PK02307: EJB'S WHICH GET MARKED AS "INVALID" ARE NOT REMOVED FROM THE CACHE AND THEREFORE CANNOT RECOVER.

 Fixes are available

5.1.1.17: WebSphere Application Server V5.1.1 Cumulative Fix 17 for AIX
5.1.1.17: WebSphere Application Server V5.1.1 Cumulative Fix 17 for HP-UX
5.1.1.19: WebSphere Application Server V5.1.1 Cumulative Fix 19 for Linux
5.1.1.16: WebSphere Application Server V5.1.1 Cumulative Fix 16 for AIX
5.1.1.18: WebSphere Application Server V5.1.1 Cumulative Fix 18 for AIX
5.1.1.18: WebSphere Application Server V5.1.1 Cumulative Fix 18 for HP-UX
5.1.1.18: WebSphere Application Server V5.1.1 Cumulative Fix 18 for Solaris
5.1.1.18: WebSphere Application Server V5.1.1 Cumulative Fix 18 for Windows
5.1.1.18: WebSphere Application Server V5.1.1 Cumulative Fix 18 for Linux
5.1.1.17: WebSphere Application Server V5.1.1 Cumulative Fix 17 for Linux
5.1.1.17: WebSphere Application Server V5.1.1 Cumulative Fix 17 for Solaris
5.1.1.17: WebSphere Application Server V5.1.1 Cumulative Fix 17 for Windows
6.0.2: WebSphere Application Server V6.0 Refresh Pack 2 for AIX platforms
5.0.2.17: WebSphere Application Server 5.0.2 Cumulative Fix 17 for Solaris
5.0.2.17: WebSphere Application Server 5.0.2 Cumulative Fix 17 for Windows
5.0.2.14: WebSphere Application Server 5.0.2 Cumulative Fix 14 for Solaris
5.1.1.10: WebSphere Application Server V5.1.1 Cumulative Fix 10 for Windows
5.1.1.10: WebSphere Application Server V5.1.1 Cumulative Fix 10 for AIX
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for AIX
5.0.2.14: WebSphere Application Server 5.0.2 Cumulative Fix 14 for Linux
5.1.1.19: WebSphere Application Server V5.1.1 Cumulative Fix 19 for AIX
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for Windows
5.1.1.19: WebSphere Application Server V5.1.1 Cumulative Fix 19 for Windows
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for HP-UX
5.1.1.9: WebSphere Application Server V5.1.1 Cumulative Fix 9 for Solaris
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for Solaris
5.0.2.15: WebSphere Application Server 5.0.2 Cumulative Fix 15 for Windows
5.0.2.15: WebSphere Application Server 5.0.2 Cumulative Fix 15 for Solaris
5.0.2.15: WebSphere Application Server 5.0.2 Cumulative Fix 15 for AIX
5.1.1.9: WebSphere Application Server V5.1.1 Cumulative Fix 9 for AIX
5.0.2.15: WebSphere Application Server 5.0.2 Cumulative Fix 15 for Linux
6.0.2: WebSphere Application Server V6.0 Refresh Pack 2 for HP-UX platforms
6.0.2: WebSphere Application Server V6.0 Refresh Pack 2 for OS/400 platforms
5.0.2.12: WebSphere Application Server 5.0.2 Cumulative Fix 12
5.1.1.6: WebSphere Application Server Version 5.1.1 Cumulative Fix 6
5.1.1.7: WebSphere Application Server Version 5.1.1 Cumulative Fix 7
5.0.2.14: WebSphere Application Server 5.0.2 Cumulative Fix 14 for HP-UX
5.0.2.14: WebSphere Application Server 5.0.2 Cumulative Fix 14 for AIX
5.1.1.4: WebSphere Application Server Version 5.1.1 Cumulative Fix 4
5.1.1.9: WebSphere Application Server V5.1.1 Cumulative Fix 9 for Windows
5.0.2.17: WebSphere Application Server 5.0.2 Cumulative Fix 17 for HP-UX
5.0.2.17: WebSphere Application Server 5.0.2 Cumulative Fix 17 for AIX
5.1.1.11: WebSphere Application Server V5.1.1 Cumulative Fix 11 for AIX
5.0.2.17: WebSphere Application Server 5.0.2 Cumulative Fix 17 for Linux
5.1.1.10: WebSphere Application Server V5.1.1 Cumulative Fix 10 for HP-UX
6.0.2: WebSphere Application Server V6.0 Refresh Pack 2 for Solaris platforms
5.1.1.10: WebSphere Application Server V5.1.1 Cumulative Fix 10 for Linux
5.1.1.9: WebSphere Application Server V5.1.1 Cumulative Fix 9 for HP-UX
5.1.1.9: WebSphere Application Server V5.1.1 Cumulative Fix 9 for Linux
5.0.2.16: WebSphere Application Server 5.0.2 Cumulative Fix 16 for HP-UX
5.1.1.12: WebSphere Application Server V5.1.1 Cumulative Fix 12 for Windows
5.0.2.16: WebSphere Application Server 5.0.2 Cumulative Fix 16 for Solaris
5.0.2.16: WebSphere Application Server 5.0.2 Cumulative Fix 16 for Windows
5.0.2.16: WebSphere Application Server 5.0.2 Cumulative Fix 16 for AIX
5.1.1.11: WebSphere Application Server V5.1.1 Cumulative Fix 11 for Windows
5.1.1.16: WebSphere Application Server V5.1.1 Cumulative Fix 16 for Solaris
5.0.2.18: WebSphere Application Server 5.0.2 Cumulative Fix 18 for Solaris
5.1.1.11: WebSphere Application Server V5.1.1 Cumulative Fix 11 for Linux
5.0.2.18: WebSphere Application Server 5.0.2 Cumulative Fix 18 for Windows
5.0.2.18: WebSphere Application Server 5.0.2 Cumulative Fix 18 for HP-UX
5.0.2.18: WebSphere Application Server 5.0.2 Cumulative Fix 18 for AIX
5.1.1.16: WebSphere Application Server V5.1.1 Cumulative Fix 16 for Windows
5.1.1.14: WebSphere Application Server V5.1.1 Cumulative Fix 14 for Solaris
5.0.2.14: WebSphere Application Server 5.0.2 Cumulative Fix 14 for Windows
5.1.1.12: WebSphere Application Server V5.1.1 Cumulative Fix 12 for AIX
5.1.1.12: WebSphere Application Server V5.1.1 Cumulative Fix 12 for Linux
5.1.1.12: WebSphere Application Server V5.1.1 Cumulative Fix 12 for HP-UX
5.1.1.12: WebSphere Application Server V5.1.1 Cumulative Fix 12 for Solaris
5.1.1.11: WebSphere Application Server V5.1.1 Cumulative Fix 11 for Solaris
5.1.1.13: WebSphere Application Server V5.1.1 Cumulative Fix 13 for AIX
5.1.1.13: WebSphere Application Server V5.1.1 Cumulative Fix 13 for Windows
5.0.2.13: WebSphere Application Server 5.0.2 Cumulative Fix 13
5.1.1.13: WebSphere Application Server V5.1.1 Cumulative Fix 13 for HP-UX
5.1.1.15: WebSphere Application Server V5.1.1 Cumulative Fix 15 for Solaris
5.1.1.13: WebSphere Application Server V5.1.1 Cumulative Fix 13 for Solaris
5.1.1.13: WebSphere Application Server V5.1.1 Cumulative Fix 13 for Linux
5.1.1.14: WebSphere Application Server V5.1.1 Cumulative Fix 14 for AIX
5.1.1.14: WebSphere Application Server V5.1.1 Cumulative Fix 14 for Linux
5.1.1.14: WebSphere Application Server V5.1.1 Cumulative Fix 14 for Windows
6.0.2: WebSphere Application Server V6.0 Refresh Pack 2 for Windows platforms
6.0.2: WebSphere Application Server V6.0 Refresh Pack 2 for Linux platforms
5.1.1.15: WebSphere Application Server V5.1.1 Cumulative Fix 15 for Windows
5.0.2.18: WebSphere Application Server 5.0.2 Cumulative Fix 18 for Linux
5.1.1.11: WebSphere Application Server V5.1.1 Cumulative Fix 11 for HP-UX
5.1.1.14: WebSphere Application Server V5.1.1 Cumulative Fix 14 for HP-UX
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for Linux
5.0.2.15: WebSphere Application Server 5.0.2 Cumulative Fix 15 for HP-UX
6.0.1.2: WebSphere Application Server Version 6.0.1 Fix Pack 2
5.0.2.16: WebSphere Application Server 5.0.2 Cumulative Fix 16 for Linux
5.1.1.10: WebSphere Application Server V5.1.1 Cumulative Fix 10 for Solaris
5.1.1.15: WebSphere Application Server V5.1.1 Cumulative Fix 15 for AIX
5.1.1.15: WebSphere Application Server V5.1.1 Cumulative Fix 15 for HP-UX
5.1.1.16: WebSphere Application Server V5.1.1 Cumulative Fix 16 for HP-UX
5.1.1.16: WebSphere Application Server V5.1.1 Cumulative Fix 16 for Linux
5.1.1.15: WebSphere Application Server V5.1.1 Cumulative Fix 15 for Linux
5.1.1.19: WebSphere Application Server V5.1.1 Cumulative Fix 19 for HP-UX



APAR status
Closed as program error.

Error description
Entity bean are not being discarded, and is simply returned to
.
If the DB Server restarts, there is a significant performance
degradation after the DB2 restart.
The observed performance degradation may be 25-30%.
.
The problem that is occurring is that this message is logged
■3/2/05 13:22:00:372 CST 00000062 SystemOut     O
javax.ejb.TransactionRolledbackLocalException:  ; nested
exception is: InvalidBeanOStateException(current = ACTIVATING,
expected = OptA | CACHED_SHARED | HYDRATING CACHED_EXCLUSIVE |
CREATING)
InvalidBeanOStateException(current = ACTIVATING, expected = OptA
| CACHED_SHARED | HYDRATING CACHED_EXCLUSIVE | CREATING)
        at
com.ibm.ejs.container.EntityBeanO.enlist(EntityBeanO.java(Compil
ed Code))
        at
com.ibm.ejs.container.activator.ReadOnlyEntityActivationStrategy
.atActivate(ReadOnlyEntityActivationStrategy.java(Compiled
Code))
        at
com.ibm.ejs.container.activator.Activator.activateBean(Activator
.java(Inlined Compiled Code))
        at
com.ibm.ejs.container.EJSContainer.preInvokeActivate(EJSContaine
r.java(Compiled Code))
        at
com.ibm.ejs.container.EJSContainer.preInvoke(EJSContainer.java(C
ompiled Code))
        at
org.spec.jappserver.orders.itement.ejb.EJSLocalCMPItemEnt_eb6213
fc.getId(Unknown Source)
        at
org.spec.jappserver.orders.itemBrowserSes.ejb.ItemBrowserSesEJB.
initItemsList(Unknown Source)
        at
org.spec.jappserver.orders.itemBrowserSes.ejb.ItemBrowserSesEJB.
getItems(Unknown Source)
        at
org.spec.jappserver.orders.itemBrowserSes.ejb.EJSLocalStatefulIt
emBrowserSes_7b595281.getItems(Unknown Source)
.
This problem only occurs when EJBs are being persisted to the
DB Server that is stopped and restarted.
.
These symptoms may occur as a result of this problem.
1. Both the OptA and ReadOnlyEntityActivationStrategies may
occur in atActivate methods leading to RemoteExceptions.
....
So, if a
RuntimeException (like EJBException) is thrown from ejbLoad,
then it is not
caught....and so the finally block does not execute the
appropriate
cleanup.... which leaves the bean in a bad state and pinned in
the EJB Cache.
.
2. As a result of this problem, because the database is reset,
a StaleConnectionException may be thrown by ejbLoad, during
atActivate when the strategy is readOnly and the exception is
not handled, so the bean is left in the cache, pinned and
on the ReadOnly strategy... and not handled... so the bean is
left in the
cache, pinned, and in the ACTIVATING state.
Once this occurs.... every attempt to access the bean afterwards
will result
in an InvalidBeanOStateException, because of the bad state...
and cleanup
will fail, because the bean is pinned in the cache.


The following exception is also resolved by the code fix
provided in this APAR:
com.ibm.ejs.container.BeanOActivationFailureException
 at
com.ibm.ejs.container.EntityBeanO.activate(EntityBeanO.java(Comp
iled Code))
 at
com.ibm.ejs.container.activator.OptAEntityActivationStrategy.doA
ctivation(OptAEntityActivationStrategy.java(Compiled Code))
 at
com.ibm.ejs.container.activator.OptAEntityActivationStrategy.atA
ctivate(OptAEntityActivationStrategy.java(Compiled Code))
 at
com.ibm.ejs.container.activator.Activator.activateBean(Activator
.java(Inlined Compiled Code))
 at
com.ibm.ejs.container.EJSContainer.preInvoke_internal(EJSContain
er.java(Compiled Code))
 at
com.ibm.ejs.container.EJSContainer.preInvoke(EJSContainer.java(I
nlined Compiled Code))
Local fix
Restart the application server.
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server users of        *
*                 Entity Enterprise Java Beans (EJBs)          *
*                 configured for Option A or ReadOnly          *
*                 Caching.                                     *
****************************************************************
* PROBLEM DESCRIPTION: Entity EJBs may be left in invalid      *
*                      state in EJB Cache after DataBase       *
*                      failure during load.                    *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
For Entity EJBs configured for Option A or ReadOnly caching,
the Entity beans may be left in the EJB Cache in an 'invalid'
state after a database exception occurs when loading the
Entity bean. Subsequent attempts to access the Entity bean
will result in the following exception:

InvalidBeanOStateException(current = ACTIVATING, expected =
OptA | CACHED_SHARED | HYDRATING CACHED_EXCLUSIVE | CREATING)
Problem conclusion
The EJB Container has been changed to properly handle database
(or other) failures when loading Entity EJBs with Option A
or ReadOnly caching.

This fix is available in the follwoing service packs:
5.0.2.11, 5.1.1.4, and 6.0.1.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 PK02307
Reported component name WAS BASE 5.0
Reported component ID 5630A3600
Reported release 10W
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2005-03-10
Closed date 2005-04-25
Last modified date 2006-01-03

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
EJBCNTR          

Publications Referenced

Fix information
Fixed component name WAS BASE 5.0
Fixed component ID 5630A3600

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


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 10W
Software edition:
Reference #: PK02307
IBM Group: Software Group
Modified date: Jan 3, 2006