PQ51460: OBJECT_NOT_EXIST EXCEPTIONS WHEN USING SESSIONBEANS (STATEFUL ORSTATELESS) WITH BEANMANAGED TRANSACTIONS | |||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||
APAR status Closed as program error. Error description This e-fix is necessary in situations where a client is invoking methods on a stateful or stateless SessionBean whose transaction attribute is set to BeanManaged. The symptom without this e-fix applied is that the client receives an OBJECT_NOT_EXIST exception when invoking the remote method on the SessionBean. Defect=110717Local fix Problem summary This APAR is being used to ship the cumulative fixes for the EJB container. Defects fixed are as follows: 111549 Use BeanPool for CMP 111491 PstmtMap in EJSJDBCPersister unneeded. 111490 OA needs serverKey in bytes 111483 Wrong object returned on Finders/Collection 111438 Bottleneck in EJSContainer.getCurrentTx 111283 MethodElements not processed correctly 110717 OBJECT_NOT_EXIST Exception in WLM environment 110661 Interop problem w/ 3.5 and WS390, SUID mismatch 110496 EJB callbacks sometimes called without collaborators 106838 Container too busy passivating beans to complete shutdown 106582 Excessive pathlength in InitialContext.lookup 103404.1 Activation of Entity Bean after module Stop/Start FailsProblem conclusion 4.0.2 ptf.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: 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 #: PQ51460
IBM Group: Software Group
Modified date: Sep 6, 2001
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.