PQ60468: INVALIDBEANOSTATEEXCEPTION WHEN CREATING ENTERPRISE APP | |||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description Customer is getting InvalidBeanOStateException when trying to create enterpriseapp via xmlconfig. The reason for this exception is that somewhere in WAS code a method in a beanA is calling a method in beanB. The method in beanB is taking a unchecked system exception. According to the spec both beanA and beanB should be discarded. However, only beanB is being discarded and beanA is kept back in the pool. Defect 123156Local fix Problem summary **************************************************************** * USERS AFFECTED: WebSphere Application Server users * * executing EJB 1.1 CMP enterprise java * * beans, and encoutering unchecked * * exception during EJB method * * execution. * **************************************************************** * PROBLEM DESCRIPTION: An unchecked exception during a bean * * method invocation can put the bean * * into an invalid state. The log file * * will show an InvalidBeanO state * * exception. * **************************************************************** * RECOMMENDATION: * **************************************************************** Assume have two bean types, e.g. EJB-A and EJB-B. If EJB-A.methoda(...)'s implementaiton calls EJB-B.methodb(...), and EJB-B.methodb(...) encounters an unchecked, e.g. a system exception, EJB-B will be properly discarded per the EJB 1.1 spec, but EJB-A will not, and should be. EJB-A is put into a state which is not appropriate. This problem only exhibits this behavior if EJB-B.methodb() encounters an unchecked exception. If the problem causing the exception is repaired, this eFix/Apar need not be applied. If the exception may happen and customer chooses to allow it, the eFix should be applied.Problem conclusion Determine if an EJB-A and EJB-B scenario exists where EJB-A's method calls a method on EJB-B, and method in EJB-B encounters an unchecked (system exception). If so, this problem will occur on 4.02 and 4.03 WebSphere Application Server versions.Temporary fix Provided a fix which cleans up the InvalidBeanO state, when bean receives an unchecked exception. Has passed customer's initial test, but is not through production Q/A test at this time.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 #: PQ60468
IBM Group: Software Group
Modified date: Jun 20, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.