PK89881: NODE AGENT INCORRECTLY RESTARTS APPSERVER DURING A CLUSTER STOP

Fixes are available

APAR status

Closed as program error.

Error description

During a cluster stop the nodeagent incorrectly restarts
appservers.

The following can be seen in the logs,

[6/22/09 12:33:47:816 EDT] 0000008c PidWaiter     A
ADML0064I: Restarting an unreachable server server1

is caused by the PidWaiter assuming that the presence of a pid
file in the log root means that the server process did not
receive a stop request.
That logic is incorrect because the stop was requested:

6/22/09 12:31:01:690 EDT] 0000007d AdminHelper   A
ADMN1020I: An attempt is made to stop the server1 server.
 -
Additional Symptoms:
When stopping an application server using the stopserver command
it is restarted by the nodeagent. The nodeagent systemout.log
shows:
PidWaiter     A
 ADML0064I: Restarting an unreachable server "server1".
AdminHelper   A
 ADMN1000I: An attempt is made to launch server1 on node node1.
  (User ID = my.ldap.com:389/user1P)
 -

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server version 6.1 and version 7.0          *
****************************************************************
* PROBLEM DESCRIPTION: The NodeAgent PidWaiter process         *
*                      incorrectly restarts an application     *
*                      server during cluster restart.          *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
During a cluster stop, the NodeAgent PidWaiter process may
incorrectly restart application servers. The following may be
seen in the log:
[6/22/09 12:33:47:816 EDT] 0000008c PidWaiter A ADML0064I:
Restarting an unreachable server server1
This is caused by the PidWaiter assuming that the presence of
a pid file in the log root means that the server process did
not receive a stop request. That logic is incorrect because
the stop was requested:
6/22/09 12:31:01:690 EDT] 0000007d AdminHelper A ADMN1020I: An
attempt is made to stop the server1 server.

Problem conclusion

Code is modified such that the NodeAgent will not relaunch an
application server when the pid file exists and the stopping
notification was received. The fix for this APAR is currently
targeted for inclusion in Service Level (Fix Pack) of
WebSphere Application Server version 6.1 (6.1.0.29) and
version 7.0 (7.0.0.7).  Please refer to the Recommended
Updates page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PK89881
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
61A
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-06-25
Closed date
2009-07-21
Last modified date
2009-08-18

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

Fix information

Fixed component name
WEBS APP SERV N
Fixed component ID
5724H8800

Applicable component levels

R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
R700 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 December 2021

Tips

PK89881: NODE AGENT INCORRECTLY RESTARTS APPSERVER DURING A CLUSTER STOP

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?