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 latterLocal 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 is sysrouted FROM one or more of the following: PQ51806 APAR is sysrouted TO one or more of the following: Modules/Macros
|
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
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.