APAR status
Closed as program error.
Error description
.
Application server hangs due to deadlock in disthub code:
.
Looking at the thread dumps, there is a deadlock:
.
.
2LKDEADLOCKTHR Thread
"com.ibm.disthub.impl.jms.SessionDispatcher@6e87b022"
(0x7979B528)
3LKDEADLOCKWTR is waiting for:
4LKDEADLOCKMON sys_mon_t:0x7A69B3F8 infl_mon_t: 0x00000000:
4LKDEADLOCKOBJ
com.ibm.disthub.impl.jms.SessionDispatcher@3BB90280/3BB90288:
3LKDEADLOCKOWN which is owned by:
2LKDEADLOCKTHR Thread "P=381229:O=0:CT" (0x302399A8)
3LKDEADLOCKWTR which is waiting for:
4LKDEADLOCKMON sys_mon_t:0x78E35F28 infl_mon_t: 0x00000000:
4LKDEADLOCKOBJ
com.ibm.disthub.impl.jms.MessageQueue@3BB83FC0/3BB83FC8:
3LKDEADLOCKOWN which is owned by:
2LKDEADLOCKTHR Thread
"com.ibm.disthub.impl.jms.SessionDispatcher@6e87b022"
(0x7979B528)
NULL
NULL
2LKDEADLOCKTHR Thread "P=381229:O=0:CT" (0x302399A8)
3LKDEADLOCKWTR is waiting for:
4LKDEADLOCKMON sys_mon_t:0x78E35F28 infl_mon_t: 0x00000000:
4LKDEADLOCKOBJ
com.ibm.disthub.impl.jms.MessageQueue@3BB83FC0/3BB83FC8:
3LKDEADLOCKOWN which is owned by:
2LKDEADLOCKTHR Thread
"com.ibm.disthub.impl.jms.SessionDispatcher@6e87b022"
(0x7979B528)
3LKDEADLOCKWTR which is waiting for:
4LKDEADLOCKMON sys_mon_t:0x7A69B3F8 infl_mon_t: 0x00000000:
4LKDEADLOCKOBJ
com.ibm.disthub.impl.jms.SessionDispatcher@3BB90280/3BB90288:
3LKDEADLOCKOWN which is owned by:
2LKDEADLOCKTHR Thread "P=381229:O=0:CT" (0x302399A8)
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server *
* using HTTP Session memory-to-memory *
* replication or using Dynamic Cache with push *
* or push-pull sharing policy. *
****************************************************************
* PROBLEM DESCRIPTION: Application server hang due to deadlock *
* in disthub. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Application server appears hung. Replication is configured for
dynamic caching or session memory to memory persistence. A
thread dump indicates there is a deadlock in disthub. Most
occurances have been between SessionDispatcher and
MessageQueue threads, but are not limitied to those threads.
Problem conclusion
This fix is currently targeted for 5.0.2.13 and 5.1.1.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 |
PK04465 |
Reported component name |
WAS ENTERPRISE |
Reported component ID |
5630A3700 |
Reported release |
00A |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2005-04-19 |
Closed date |
2005-07-28 |
Last modified date |
2005-07-28 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
Publications Referenced
|
Fix information |
Fixed component name |
WAS NETWRK DEPL |
Fixed component ID |
5630A3601 |
Applicable component levels |
R003 PSY |
UP |
R00A PSY |
UP |
R00I PSY |
UP |
R00H PSY |
UP |
R00P PSY |
UP |
R00S PSY |
UP |
R00W PSY |
UP |
R103 PSY |
UP |
R10A PSY |
UP |
R10I PSY |
UP |
R10H PSY |
UP |
R10P PSY |
UP |
R10S PSY |
UP |
R10W PSY |
UP |
|