APAR status
Closed as program error.
Error description
Appserver Hang in the DRS component. The following 2 Thread
stacks indicate they are waiting on
a)waiting to lock(a com.ibm.ws.drs.JMSSessPoolWrapper)
b)waiting to lock(com.ibm.disthub.impl.jms.TopicConnectionImpl)
1)
"Servlet.Engine.Transports : 670" daemon prio=10 tid=0x02055f80
nid=12943 lwp_id=3138530 waiting for monitor entry
[0x0f0c7000..0x0f0c5500]
at com.ibm.ws.drs.DRSJMS.jmsPubUpd(DRSJMS.java:188)
- waiting to lock <0x2639a910> (a
com.ibm.ws.drs.JMSSessPoolWrapper)
at com.ibm.ws.drs.DRSCacheApp.jmsPubUpd(DRSCacheApp.java:3234)
at com.ibm.ws.drs.DRSAPI.createEntry(DRSAPI.java:657)
com.ibm.ws.drs.DRSCacheApp.createEntry(DRSCacheApp.java:2769)
com.ibm.ws.webcontainer.httpsession.DRSHttpSessCache.createEntry
(DRSHttpSessCache.java:1118)
2)
"Servlet.Engine.Transports :
632:ipaddr=198.26.119.86;path=/conseco/selfservice/images/common
/icon_lock_trans_tanbck.gif" daemon prio=10 tid=0x02055e48
nid=12903 lwp_id=3138441 waiting for monitor entry
[0x0f6d4000..0x0f6d1500]
com.ibm.disthub.impl.client.ConnectorImpl.send(ConnectorImpl.jav
- waiting to lock <0x2638fce0> (a
com.ibm.disthub.impl.jms.TopicConnectionImpl)
com.ibm.disthub.impl.client.ConnectorImpl.send(ConnectorImpl.jav
com.ibm.disthub.impl.jms.TopicPublisherImpl.publishInternal(Topi
cPublisherImpl.java:508)
com.ibm.disthub.impl.jms.TopicPublisherImpl.publish(TopicPublish
erImpl.java:450)
Local fix
No work around available
Problem summary
****************************************************************
* USERS AFFECTED: All users of Websphere Application server *
* using HTTP session memory to memory *
* replication and cache replication. *
****************************************************************
* PROBLEM DESCRIPTION: Deadlock in the stop mechanism prevents *
* Application server stop completion. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
If a consumer of the replication service such as HTTP session
memory to memory replication or cache replication attempts a
connection reset at around the same time that an application
server stop is attempted, then the two threads deadlock with
each other preventing the completion of the application server
stop process.
Problem conclusion
A fix for this problem is being made available via an iFix.
This fix will also be available as part of 5.0.2.7 and 5.1.0.6.
Temporary fix Comments
APAR information |
APAR number |
PQ90152 |
Reported component name |
WAS BASE 5.0 |
Reported component ID |
5630A3600 |
Reported release |
00H |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2004-06-14 |
Closed date |
2004-06-23 |
Last modified date |
2004-06-23 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
Publications Referenced
Applicable component levels |
R003 PSY |
UP |
R00A PSY |
UP |
R00H PSY |
UP |
R00I PSY |
UP |
R00P PSY |
UP |
R00S PSY |
UP |
R00W PSY |
UP |
R103 PSY |
UP |
R10A PSY |
UP |
R10H PSY |
UP |
R10I PSY |
UP |
R10P PSY |
UP |
R10S PSY |
UP |
R10W PSY |
UP |
|