PQ52631: ILLEGALSTATEEXCEPTION OCCURRING AT BEAN PASSIVATION, ALTHOUGH STATE IS SET CORRECTLY BEFORE REMOVAL FROM CACHE

APAR status
Closed as program error.

Error description
more than one bean instance is in the same transaction, but one
is being used when state is set and the other is being used for
passivation.  This causes an IllegalStateException on the latter
Local fix Problem summary
This fixes a condition in the container where upon
encountering an EJB createFailure (in
this case a DuplicateKeyException) the container
removes the wrong Bean instance from the
EJBcache (so happens to be the same beanId
though). Subsequently the instance which was
removed
fails commit processing because the instance
enlisted in the transaction does not match up
with the instance in the EJBcache.
Problem conclusion Temporary fix Comments
APAR information
APAR number PQ52631
Reported component name WEBSPHERE AE NT
Reported component ID 5630A2201
Reported release 400
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2001-09-20
Closed date 2001-09-20
Last modified date 2001-09-20

APAR is sysrouted FROM one or more of the following:
PQ51806

APAR is sysrouted TO one or more of the following:

Modules/Macros
EJSCONT          

Fix information
Fixed component name WEBSPHERE AE NT
Fixed component ID 5630A2201

Applicable component levels
R400 PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ52631
IBM Group: Software Group
Modified date: Sep 20, 2001