PM01579: DEADLOCK SEEN BETWEEN HAMANAGER AND DRS CALLING HTTPSESSCLUSTEROBSERVER.

Fixes are available

APAR status

Closed as program error.

Error description

On startup, a deadlock is seen between Default threads and
HAManager threads.  Both threads are making calls to
com.ibm.ws.webcontainer.httpsession.httprouting.HttpSessClusterO
bserver.notify.

The call stacks for the threads in question will appear similar
to the following:

"Default : 10":
at
com.ibm.ws.cluster.service.ClusterServiceImpl.registerInterest

(ClusterServiceImpl.java:353)
- waiting to lock <6040b498> (a
  java.util.Collections$SynchronizedMap)
at com.ibm.ws.webcontainer.httpsession.httprouting

.HttpSessClusterObserver.notify(HttpSessClusterObserver.java:183
)
- locked <6100a978> (a
  com.ibm.ws.webcontainer.httpsession.httprouting
  .HttpSessClusterObserver)
at com.ibm.ws.runtime.component.MultibrokerDomainImpl

.registerInterestWithWLMCluster(MultibrokerDomainImpl.java:436)
at com.ibm.ws.drs.managers.DRSBootstrapManager
   .handleBootstrapResponse(DRSBootstrapManager.java:479)
at com.ibm.ws.drs.stack.DRSClientCallback.processRcvMessage

(DRSClientCallback.java:341)
at
com.ibm.ws.drs.stack.DRSStack.processRcvMessage(DRSStack.java:29
5)
at com.ibm.ws.drs.DRSDomain.messageReceived(DRSDomain.java:536)
at com.ibm.ws.drs.ha.DRSAgentClassEvents$1.run

(DRSAgentClassEvents.java:714)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1473)



"HAManager.thread.pool : 1":
at com.ibm.ws.webcontainer.httpsession.httprouting

.HttpSessClusterObserver.notify(HttpSessClusterObserver.java:148
)
- waiting to lock <6100a978> (a
  com.ibm.ws.webcontainer.httpsession.httprouting
  .HttpSessClusterObserver)
at
com.ibm.ws.cluster.service.ClusterServiceImpl.handleNotification

(ClusterServiceImpl.java:617)
- locked <6040b498> (a java.util.Collections$SynchronizedMap)
at
com.ibm.websphere.cluster.topography.DescriptionA.notifyListener
s

(DescriptionA.java:244)
at
com.ibm.ws.cluster.topography.ClusterDescriptionImpl.setMemento

(ClusterDescriptionImpl.java:967)
at com.ibm.ws.cluster.topography.DescriptionManagerA.update

(DescriptionManagerA.java:428)
at
com.ibm.ws.cluster.propagation.bulletinboard.BBDescriptionManage
r
   .updated(BBDescriptionManager.java:329)
at com.ibm.ws.hamanager.bboard.LocalBulletinBoardStateManager
   $BBoardUserCallback.doCallback

(LocalBulletinBoardStateManager.java:2784)
at com.ibm.ws.hamanager.impl.Worker.run(UserCallbacks.java:288)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1473)

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server using memory-to-memory data          *
*                  replication.                                *
****************************************************************
* PROBLEM DESCRIPTION: A deadlock occurs at application        *
*                      server start with multiple threads in   *
*                      HttpSessClusterObserver.notify.         *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
During startup the cluster observer's notify method is invoked
by Data Replication Services (DRS) and Workload Management
(WLM).  In some instances a deadlock occurs when the notify
method is invoked simultaneously by DRS and WLM.

Problem conclusion

When the DRS_DO_NOT_NOTIFY_CLUSTEROBSERVER JVM custom property
is defined and set to true DRS will not invoke the notify
method during application server startup.  This will prevent
the deadlock from occurring.

The fix for this APAR is currently targeted for inclusion in
fix pack 6.1.0.31 and 7.0.0.11.  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
PM01579
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
61H
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-11-18
Closed date
2010-02-11
Last modified date
2010-02-11

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

PM01579: DEADLOCK SEEN BETWEEN HAMANAGER AND DRS CALLING HTTPSESSCLUSTEROBSERVER.

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?