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     New feature: Automatic Self Recovery

Read-Only Read-Only Topic
Go
Search
Notify
Tools
New feature: Automatic Self Recovery
 Login/Join
 
<pranas>
posted
Hello,

Has some one tried the new WebFOCUS 5.2.3 feature automatic_recovery option in edaserver.cfg?
What is exact syntax?
Does it really works?

Thanks gurus!

Pranas
 
Report This Post
<Grzegorz>
posted
The automatic recovery syntax looks as follows:
automatic_recovery = y
or
automatic_recovery = n
It is set to 'y'es by default (if there is no automatic_recovery in the edaserve.cfg).

Automatic recovery checks if the configured listeners and special services (it means processes named edapgwy) are running, and if any of the edapgwy process is down it is run again.

From my experiments (on Windows only) it looks that the feature really works.

To experiment with the automated recovery:

  • From the WebFOCUS web console, choose Listeners
  • You will see the configured Listeners along with their system Pid
  • Find the process with the appropriate Pid using Task Manager, and stop it.
  • Wait for a while, the process should be back with the same or another Pid.

It does not recover the FDS Service - its process is named hlisnk, and the automatic recovery only recovers edapgwy processes.


List of processes running when Webfocus Server is running

Regards
Grzegorz
 
Report This Post
<pranas>
posted
The combination:
automatic_recovery = y
crashed_cleanup = on

Provides stable environment. Nice new feature :-)
 
Report 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     New feature: Automatic Self Recovery

Copyright © 1996-2020 Information Builders