PQ75440: TRANSACTION CONTEXT CANNOT BE ESTABLISHED ON A 'CREATE' METHOD. | |||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description When a create method is defined on a bean (as oppose to create method on a bean home which does not need transaction context), transaction context is not established.Local fix Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * version 4.0.1 for z/OS and OS/390 * **************************************************************** * PROBLEM DESCRIPTION: A Stateless bean buisiness method * * 'create' does not have the proper * * transaction context established for it. * * This results in its related work being * * performed in the wrong transaction * * which ultimately leads to incorrect * * results in the backing database. * **************************************************************** * RECOMMENDATION: * **************************************************************** When invoking 'create' or 'remove' method on for a stateless session bean, it is not required to establish tran context and collaborator support. Therefore it was possible via an optimization to bypass the setting of tran and collaborator context in the event of a home create or remove call for a stateless session. The optimization path in this scenario was not distinguishing between a call to 'create' defined on the home vs. defined on the bean. Therefore if an app included a bean whose remote interface included a method called 'create' (legal according to the spec), the tran context would not be established and the bean method would encounter errors.Problem conclusion When processing a bean for installation the container now sets an indicator flag in the EJBMethodInfo object when the method 'create' or 'remove' is processed for the home interface. This flag is used later in the preInvoke path to determine if the method call being dispatched is a *home* create or a *home* remove (as opposed to the same named methods on the bean interface) and will bypass the tran and collaborator context setup accordingly. If these two method names are set on the bean interface, the install processing will set the new flag to false and later in preInvoke, the tran and collaborator contexts will be established correctly. APAR PQ75440 is associated with SERVICE LEVEL W401509 of WebSphere Application Server version 4.0.1 for z/OS and OS/390.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 for z/OS
Operating system(s):
Software version: 401
Software edition:
Reference #: PQ75440
IBM Group: Software Group
Modified date: Aug 6, 2003
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.