PQ88216: "Maximum startup attempts" setting for Generic Server has no affect.

APAR status
Closed as program error.

Error description
Bettegow
Defect Type = Technical

Defect Qualifiers = Missing

Defect Content Type = Tasks

Description: The "Maximum startup attempts" setting for Generic
Servers has no effect. Regardless of this setting, the admin
server appears to make exactly one restart attempt.

The admin server would also need to reset the restart Attempt
counter after the Generic Server has been running for some
period of time, otherwise the restart attempt counter is
eventually exhausted, even though restarts are actually
successful.

Furthermore, the admin server would need to restrict the
interval between restart attempts in order not to cause
prformance problems in the event that the server would
immedieately and repeatedly fail on startup.

We suspect that the "Ping interval", "Ping timeout" and
"Ping initial timeout" settings for the Generic
Server would Control that behaviour.

However, the documentation is unclear on how these settings
applies to Generic Servers, and they do not seem to have any
effect on the restart behaviour.

As a "wish-list" item, it would also be nice if it would be
possible to set the number of restart attempts to be infinite,
perhaps by setting it to 0 or -1, which would also be a
resonable
Local fix
Suggested Update: None.
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server users trying    *
*                 to retstart the server.                      *
****************************************************************
* PROBLEM DESCRIPTION: Maximum startup attempts setting for    *
*                      Server has no effect. Regardless of     *
*                      this setting, the admin server          *
*                      appears to make exactly one restart     *
*                      attempt.                                *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Maximum startup attempts setting for Server has no effect.
Regardless of this setting, the admin server appears to make
exactly one restart attempt.

There are two ways to set the maxRetry and sleepTime
1. Using admin.config:
com.ibm.ejs.sm.adminServer.nannyThread.maxRetries=<Value>
com.ibm.ejs.sm.adminServer.nannyThread.waitTime=<Value>
2.Using adminclient in the appropriate textboxes.

Note:
1. The system will look into admin.config to read values for
maxRetry and sleepTime at first otherwise it reads from
adminclient and try to restart the app server more than once.

2. The property set using admin.config applies to all app
servers rather than individual app server.
Problem conclusion
There was change in code of ActiveServerProcess.java to read
the values from adminclient or also from admin.config as
specified in 
PQ59006.
Temporary fix
We were able to recreate the problem and testing has been done
from ourside. Test-Fix has been sent to customer but customer
has not perform the test.
Comments
APAR information
APAR number PQ88216
Reported component name WEBSPHERE AE AI
Reported component ID 5630A2200
Reported release 400
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2004-04-30
Closed date 2004-06-07
Last modified date 2004-06-07

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
admingui          

Fix information

Applicable component levels
R400 PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ88216
IBM Group: Software Group
Modified date: Jun 7, 2004