PK80941: ALL CLUSTER MEMBERS DO NOT START WHEN THE CLUSTER IS STARTED

Fixes are available

APAR status

Closed as program error.

Error description

Attempting to start a cluster from the Administrative Console.
The member on one node starts but the member on the other node
does not start.  The nodeagent doesn't attempt to start it.
-
There are no errors issued. The normal messages are seen.
The DMGR shows:
ADMN1012I: An attempt is made to start the c1 cluster
The working nodeagent shows:
ADMN1000I: An attempt is made to launch c1_mem1 on node node1.
The failing node does not show this message.

Local fix

start the cluster member manually from the Admin Console
 -
Search Keywords: startup ZE startserver

Problem summary

****************************************************************
* USERS AFFECTED:  All users of WebSphere Application Server   *
*                  versions 6.0.2, 6.1.0, 7.0.0                *
****************************************************************
* PROBLEM DESCRIPTION: Restarting a cluster after just         *
*                      stopping it, some members do not        *
*                      restart.                                *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
After stopping the cluster, the nodeagent does not forward the
stopped notification right away for some cluster members. It
appears that those cluster members are still active but all
the members are actually stopped.  Trying to restart those
cluster members right away will cause them to not be restarted
by the nodeagent as it believes the member is still active.
Eventually, the nodeagent sends the stopped notification and
the member is recognized to be stopped.

Problem conclusion

The code has been changed to not delay sending of the stopped
notifications.
APAR PK80941 is currently targeted for inclusion in
FixPack 6.0.2.35, 6.1.0.25, 7.0.0.5 of
WebSphere Application Server V6.0.2, V6.1, and V7.0.

Please refer to Recommended Updates page for
delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PK80941
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
60A
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-02-18
Closed date
2009-02-25
Last modified date
2009-02-25

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

R60A PSY
UP
R60H PSY
UP
R60I PSY
UP
R60P PSY
UP
R60S PSY
UP
R60W PSY
UP
R60Z PSY
UP
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.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 December 2021

Tips

PK80941: ALL CLUSTER MEMBERS DO NOT START WHEN THE CLUSTER IS STARTED

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

R60A PSY

R60H PSY

R60I PSY

R60P PSY

R60S PSY

R60W PSY

R60Z PSY

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?