PQ86936: NODEAGENT INTIALIZATION THREAD HANGS WHEN A SERVER THAT IS STARTED AUTOMATICALLY ABENDS.

 A fix is available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
When a server is started automatically when the nodeagent is
brought up, the nodeagent intialization thread waits for a
the server to finish initialization before moving on.  In the
case where the server abends, the nodeagent is never notified
of the abend, and continues to wait indefinitely.  Users
experiencing this error will see the nodeagent address space
running, however, it will not be able to synchronize any
servers with the deployment manager.
Local fix
Disable the automatic start of servers when the nodeagent is
started.  This can be done in the following panel on the
admin console:
  Servers > Application Servers > <serverName> >
  Process Definition > Control > Monitoring Policy
.
and setting the field 'Node restart state' to 'Stopped'.
Stopped is the default value for this field.
Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V5.0 for z/OS                                *
****************************************************************
* PROBLEM DESCRIPTION: When servers are started automatically  *
*                      on NodeAgent startup and at least one   *
*                      of the servers abends, the NodeAgent    *
*                      Initialization thread hangs.            *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When an application server is started automatically as a result
of nodeagent startup, the nodeagent intialization thread waits
for the server to finish initialization before moving on.  In
the case where the server abends, the nodeagent is never
notified of the abend, and continues to wait indefinitely.
Users experiencing this error will see the nodeagent address
space running, however, the "INITIALIZATION COMPLETE" message
for the nodeagent control region will never appear on the
system console.
Problem conclusion
The server_start_wait_for_initialization_Timeout custom
property, previously enabled only for Application Servers,
may now also be specified for the nodeagent server, allowing
the nodeagent to timeout while waiting for servers to initialize
instead of waiting indefinitely as has been the case.

The following changes will be made to the V5 Information Center.
To access these Information Centers, use the link provided on
the product library page at:

www.ibm.com/software/webservers/appserv/zos_os390/library.html

The article "Changing the values of variables referenced in
BBOM0001I messages" has been updated to indicate which of the
variable to application servers and which ones only apply to
application servers and deployment agents. A sentence has also
been added to the first paragraph to clarify that these
variables apply to all servers (deployment managers, node
agents, JMS servers, and application servers) unless otherwise
indicated.

The description of the
server_start_wait_for_initialization_Timeout variable has been
updated to indicate the correct administrative console path to
follow to add this custom property for a node.

APAR PQ86936 is associated with SERVICE LEVEL W502013 of
WebSphere Application Server V5.0 for z/OS.
Temporary fix Comments
APAR information
APAR number PQ86936
Reported component name WEBSPHERE FOR Z
Reported component ID 5655I3500
Reported release 500
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2004-03-31
Closed date 2004-07-20
Last modified date 2004-08-04

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:
PQ89471

Modules/Macros
BBOUBINF          

Publications Referenced

Fix information
Fixed component name WEBSPHERE FOR Z
Fixed component ID 5655I3500

Applicable component levels
R500 PSY UQ90831    UP04/07/27 P F407

  Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.


Document Information


Current web document: swg1PQ86936.html
Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS
Operating system(s):
Software version: 500
Software edition:
Reference #: PQ86936
IBM Group: Software Group
Modified date: Aug 4, 2004