Focal Point Banner


As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.

Join the TIBCO Community
TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.

  • From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
  • Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
  • Request access to the private WebFOCUS User Group (login required) to network with fellow members.

Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.


Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     [Solved] WebFocus Agent Disconnect

Read-Only Read-Only Topic
Go
Search
Notify
Tools
[Solved] WebFocus Agent Disconnect
 Login/Join
 
RichardA
Gold member
posted
I have been getting a "cannot connect to EDASERVE" error on one of my maintain and cannot figure out why. Let me explain.

I was running one of my maintains and exited. When I tried to rerun the maintain from a web page I got the "cannot connect to EDASERVE" error message. I don't think it's an ODIN.cfg issue because nothing other than this maintain has exhibited this behavior.

I completely exited out of all instances of IE and logged back in and still had the issue. When I manually deleted the IBI Webfocus cookie for that server I could get back into the maintain and it worked.

I thought that maintain and webfocus stored its persistance in session varibles not cookies. This seems not to be the case for this issue. I am at a loss for how WebFocus agent persistance really works other than my own experimentation.

Has anyone else ever had this issue?

How does WebFocus agent persistance really work?

Why can't I see user names of agents in the web console?

Is this a WebFocus Client (WFServlet) issue?

Lots of questions, no answers.

This message has been edited. Last edited by: RichardA,


Sandbox Version: 8.1.04
Sandbox Platform: Windows 2008 R2
Testing Version: 7.7.02M
Testing Platform: Windows Server 2008 R2
WF Production Version: 7.7.02M
Production Platform: Windows Server 2008
 
Posts: 57 | Location: Philadelphia, PA | Registered: June 19, 2007Report This Post
Wep5622
Virtuoso
posted Hide Post
I've seen similar issues with selfservice reports when using IE. It only happens in IE, I haven't ever seen this issue with Firefox.

What happens with sessions is that the browser stores a cookie with your session ID, so that the server knows which session to look up for your connection. Apparently IE sometimes "messes up"[1] the cookie or the session ID stored in it, causing confusion on WebFOCUS' end.

I think in such cases WF should just initiate a new session and ignore what IE is claiming. I know that IE is a piece of junk, but WF isn't exactly fault tolerant here either and it does claim to support IE - it even requires it for some actions!

Ad 1) "Messes up" from the point of view of WF. It's probably entirely valid, but different from what WF expected and close enough to the truth that WF still attempts to pick up that session.


WebFOCUS 8.1.03, Windows 7-64/2008-64, IBM DB2/400, Oracle 11g & RDB, MS SQL-Server 2005, SAP, PostgreSQL 11, Output: HTML, PDF, Excel 2010
: Member of User Group Benelux :
 
Posts: 1669 | Location: Enschede, Netherlands | Registered: August 12, 2010Report This Post
Maintain Wizard
Master
posted Hide Post
I have a solution! The problem is that if the application is not exited correctly (and I use that word sparingly) part of the connection remains. If you try to go back in, we try to reconnect to an agent or session that is no longer there. That causes the problem.

The solution is to edit the ENtemplate.xml file. Please send an e-mail to Mark_Derwin@ibi.com and I will send you the file / information on how to do this.

Mark
 
Posts: 663 | Location: New York | Registered: May 08, 2003Report This Post
  Powered by Social Strata  

Read-Only Read-Only Topic

Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     [Solved] WebFocus Agent Disconnect

Copyright © 1996-2020 Information Builders