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     [CLOSED] Crashed Agents

Read-Only Read-Only Topic
Go
Search
Notify
Tools
[CLOSED] Crashed Agents
 Login/Join
 
ABT
Master
posted
I think I already know the answer to this, bt maybe there's something I'm missing. When an agent shows as crashed via the Agent Monitor (WebFocus dashboard), there is no chance that it is coming back, right? Sometimes a LASTERRNO > 0 will allow it to continue processing, I just wanted to make sure I wasn't going to have an angry user come back at me because it wasn't all the way dead yet.

"Bring out your dead"
"I'm not dead yet"
"Of course you are"
"No, in fact I'm feeling much better"

- ABT

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


------------------------------------
WF Environment:
------------------------------------
Server/Client, ReportCaster, Dev Studio: 7.6.11
Resource Analyzer, Resource Governor, Library, Maintain, InfoAssist
OS: Windows Server 2003
Application/Web Server: Tomcat 5.5.25
Java: JDK 1.6.0_03
Authentication: LDAP, MRREALM Driver
Output: PDF, EXL2K, HTM

------------------------------------
Databases:
------------------------------------
Oracle 10g
DB2 (AS/400)
MSSQL Server 2005
Access/FoxPro
 
Posts: 561 | Registered: February 03, 2010Report This Post
GamP
Virtuoso
posted Hide Post
You're absolutely right, when an agent has crashed it is dead and it will stay dead until the process is stopped manually or by restarting the server.
This is done to allow for the recovery of files from the crashed agents directory for further analysis. Drawback is of course that the dead agent does still occupy a slot in the available agents pool. There is a setting you can use to immediately kill crashed agents, thereby releasing the slot for a new healthy agent.


GamP
- Using AS 8.2.01 on Windows 10 - IE11.
in Focus since 1988
 
Posts: 1961 | Location: Netherlands | Registered: September 25, 2007Report This Post
GamP
Virtuoso
posted Hide Post
I looked up what this setting is:
quote:
To have the WebFOCUS Reporting Server automatically clean up crashed agents, you can add the following setting in the edaserve.cfg file:

crashed_cleanup = ON


GamP
- Using AS 8.2.01 on Windows 10 - IE11.
in Focus since 1988
 
Posts: 1961 | Location: Netherlands | Registered: September 25, 2007Report This Post
ABT
Master
posted Hide Post
thanks for the confirm, exactly what I was after.

- ABT


------------------------------------
WF Environment:
------------------------------------
Server/Client, ReportCaster, Dev Studio: 7.6.11
Resource Analyzer, Resource Governor, Library, Maintain, InfoAssist
OS: Windows Server 2003
Application/Web Server: Tomcat 5.5.25
Java: JDK 1.6.0_03
Authentication: LDAP, MRREALM Driver
Output: PDF, EXL2K, HTM

------------------------------------
Databases:
------------------------------------
Oracle 10g
DB2 (AS/400)
MSSQL Server 2005
Access/FoxPro
 
Posts: 561 | Registered: February 03, 2010Report This Post
ABT
Master
posted Hide Post
GamP, What manual did you find that in? I did a 'Documentation Search' and didn't get any hits on 'crashed_cleanup'.

- ABT


------------------------------------
WF Environment:
------------------------------------
Server/Client, ReportCaster, Dev Studio: 7.6.11
Resource Analyzer, Resource Governor, Library, Maintain, InfoAssist
OS: Windows Server 2003
Application/Web Server: Tomcat 5.5.25
Java: JDK 1.6.0_03
Authentication: LDAP, MRREALM Driver
Output: PDF, EXL2K, HTM

------------------------------------
Databases:
------------------------------------
Oracle 10g
DB2 (AS/400)
MSSQL Server 2005
Access/FoxPro
 
Posts: 561 | Registered: February 03, 2010Report This Post
ira
Platinum Member
posted Hide Post
try looking here: http://documentation.informati.../08serverconfig3.htm


aix-533,websphere 5.1.1,apache-2.0,
wf 538(d), 537 (p),
==============
7.6.11 (t) aix 5312
websphere 6.1.19
apache 2.0
 
Posts: 195 | Registered: October 27, 2006Report This Post
Doug
Expert
posted Hide Post
Thanks for the info... I searched for "kill crashed agents", here in FocalPoint, and there it was... Big Grin
 
Posts: 3132 | Location: Tennessee, Nashville area | Registered: February 23, 2005Report This Post
GamP
Virtuoso
posted Hide Post
There is also a very good help-function in the server's web console.
In 77, start the server console web page, go to Workspace / configuration, open group Configuration files and right-click Workspace, select Edit. When te file is opened, click on the book icon, just left above the file contents.
The help file contains a **lot** of information.


GamP
- Using AS 8.2.01 on Windows 10 - IE11.
in Focus since 1988
 
Posts: 1961 | Location: Netherlands | Registered: September 25, 2007Report 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     [CLOSED] Crashed Agents

Copyright © 1996-2020 Information Builders