PQ84963: BEANOACTIVATIONFAILUREEXCEPTION OCCURS AFTER MIGRATE FROM 4.0.3 TO 4.0.7 MAINTENANCE LEVELS. | |||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description Customer application gets a TransactionRolledbackException CORBA TRANSACTION_ROLLBACK caused by a com.ibm.container.BeanOActivationFailureException in their application after applying fixpak7 over fixpak3. A duplicate key exception was detected during (after) PostCreate processing and the BeanO was marked destroyed but not removed from cache. Next time a findByPrimaryKey() finds the destroyed bean and the failure occurs.Local fix Problem summary **************************************************************** * USERS AFFECTED: WebSphere Application Server users who * * encountered an error during EJB creation * * and subsequently activate the same bean * * type may be affected. * **************************************************************** * PROBLEM DESCRIPTION: If an error occurs during EJB after * * post create processing, e.g. duplicate * * key, follow-on request to the same * * bean type may result in a * * BeanOActivationFailureException. * * This exception is manifested to * * the application in the form of a * * TransactionRolledbackException. * **************************************************************** * RECOMMENDATION: * **************************************************************** When an error occurs during EJB after post create processing, an already created BeanO is marked destroyed but is not removed from the cache. This left the BeanO instance in an inconsistent state. Any subsequent request that causes the activation of the bean will find the bean "already activated", hence the BeanOActivationFailureException is thrown by the EJB container.Problem conclusion This incorrect behavior is rectified by removing the destroyed beanO entry from the cache when an unexpected error is detected. Any follow-on method call will activate a new instance of the beanO for servicing the request.Temporary fix Temporary fix patch was sent to customer for testing to cover the case where the create process failed with a duplicated key and the beanO is not removed accordingly.Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
SRLS
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ84963
IBM Group: Software Group
Modified date: Mar 29, 2004
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.