PM56082: THREAD RACE RESULTS IN OUT-OF-ORDER ISALIVE CALLBACK AND JVM STOPPED WITH PANICJVM IN HAMANAGER.

Fixes are available

APAR status

Closed as program error.

Error description

Due to Thread race condition, which results in
out-of-order isAlive callback. In the end JVM stopped
with panicJVM. The following stack could be observed.

[12/01/11 17:33:54:791 JST] 0000001e SystemErr     R
at com.ibm.ws.hamanager.runtime.RuntimeProviderImpl
   .panicJVM(RuntimeProviderImpl.java:91)
[12/01/11 17:33:54:791 JST] 0000001e SystemErr     R
at com.ibm.ws.hamanager.coordinator.impl.JVMControllerImpl
   .panicJVM(JVMControllerImpl.java:56)
[12/01/11 17:33:54:791 JST] 0000001e SystemErr     R
at com.ibm.ws.hamanager.impl.HAGroupImpl
   .doIsAlive(HAGroupImpl.java:866)
[12/01/11 17:33:54:791 JST] 0000001e SystemErr     R
at com.ibm.ws.hamanager.impl.HAGroupImpl$HAGroupUserCallback
   .doCallback(HAGroupImpl.java:1364)
[12/01/11 17:33:54:791 JST] 0000001e SystemErr     R
at com.ibm.ws.hamanager.impl.Worker.run(Worker.java:64)
[12/01/11 17:33:54:791 JST] 0000001e SystemErr     R
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1550)
[12/01/11 17:33:54:791 JST] 0000001e SystemOut     O
java.lang.RuntimeException: emergencyShutdown called:

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server                                      *
****************************************************************
* PROBLEM DESCRIPTION: An Application Server stops             *
*                      unexpectedly with a "panic JVM"         *
*                      message in the SystemOut log            *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
WebSphere Application Server supports a number of clustered,
highly available singleton services, such as as a J2C adapter
or an SIBus messaging engine. The HA Manager will elect one
member of the cluster to host the active singleton service.
When the HA Manager elects a cluster member, it sends an
"activate" command to the singleton service on the elected
cluster member. After sending the activate command, the HA
Manager will then monitor the health of the singleton service
by periodically sending an "isAlive" check. If the singletonn
service responds that it is not alive, the HA Manager will
panic the JVM so the singleton service can fail over to
another cluster member.
Due to a race condition, it is possible for the isAlive check
to be processed by the singleton before the activate command
has reached it, causing an erroneous panic of the application
server.

Problem conclusion

Changed the way the HA Manager isAlive is dispatched to
guarantee that the activate command will always reach the
singleton service before the isAlive.

The fix for this APAR is currently targeted for inclusion in
fix packs 6.1.0.45, 7.0.0.23 and 8.0.0.4.  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
PM56082
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-01-16
Closed date
2012-03-15
Last modified date
2012-03-15

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
R800 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":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 October 2021

Tips

PM56082: THREAD RACE RESULTS IN OUT-OF-ORDER ISALIVE CALLBACK AND JVM STOPPED WITH PANICJVM IN HAMANAGER.

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

R800 PSY

Document Information

Share your feedback

Need support?