APAR status
Closed as program error.
Error description
When calling a method on a bean in the same bucket as is being
removed, a java level deadlock can occur which looks like the
following:
1LKDEADLOCK Deadlock detected !!!
NULL ---------------------
NULL
2LKDEADLOCKTHR Thread "ORB.thread.pool : 0" (0x443806A0)
3LKDEADLOCKWTR is waiting for:
4LKDEADLOCKMON sys_mon_t:0x460AA858 infl_mon_t: 0x00000000:
4LKDEADLOCKOBJ
com.ibm.ejs.util.cache.Bucket@582575D0/582575D8:
3LKDEADLOCKOWN which is owned by:
2LKDEADLOCKTHR Thread "Alarm : 2" (0x3A64B7A0)
3LKDEADLOCKWTR which is waiting for:
4LKDEADLOCKMON sys_mon_t:0x460A5498 infl_mon_t: 0x4609FA80:
4LKDEADLOCKOBJ java.lang.Object@5825C1F8/5825C200:
3LKDEADLOCKOWN which is owned by:
2LKDEADLOCKTHR Thread "ORB.thread.pool : 0" (0x443806A0)
Local fix Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server Developers *
* and Administrators for applications that *
* use Stateful Session EJBs. *
****************************************************************
* PROBLEM DESCRIPTION: Deadlock may occur between two threads *
* named "ORB.thread.pool" and "Alarm", *
* waiting for a lock on an object of *
* type *
* com.ibm.ejs.util.cache.Bucket *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When using Stateful Session EJBs and the Application Server
is under heavy load, the EJB Container may passivate some
of the Stateful Session EJBs to a file, to free up
resources. At this time, if the Stateful Session EJB
accesses other EJB instances (i.e. during ejbPassivate)
it is possible that a deadlock may occur.
Problem conclusion
Basically, the deadlock occurs because the thread performing
the passivation may acquire EJB cache resource locks in a
different order than other EJB access.
The lock ordering will be changed to be consistent will all
other EJB access, and the deadlock will no longer occur.
The problem will be fixed in the following releases:
5.1.1.5 and 6.0.2
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 |
PK04804 |
Reported component name |
WAS BASE 5.0 |
Reported component ID |
5630A3600 |
Reported release |
10A |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2005-04-25 |
Closed date |
2005-07-12 |
Last modified date |
2005-07-12 |
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 BASE 5.0 |
Fixed component ID |
5630A3600 |
Applicable component levels |
R003 PSN |
UP |
R00A PSY |
UP |
R00H PSY |
UP |
R00I PSY |
UP |
R00P PSY |
UP |
R00S PSY |
UP |
R00W PSY |
UP |
R103 PSN |
UP |
R10A PSY |
UP |
R10H PSY |
UP |
R10I PSY |
UP |
R10P PSY |
UP |
R10S PSY |
UP |
R10W PSY |
UP |
|