PQ63130: WHEN AN EJB IS BUILD WITH A REMOVE METHOD, WHEN DEPLOYED, THE TRANSACTION CONTEX CHANGES TO TX NOT SUPPORTED | |||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description Customer has an ejb packaged with all methods set for tx_required. When the customer has a method called remove, the transaction context is changed to tx_not_supported which is evident in the meta data.Local fix Problem summary **************************************************************** * USERS AFFECTED: WebSphere Application Server users with * * overloaded remove, getHandle, isIdentical * * and getPrimaryKey methods on their beans. * **************************************************************** * PROBLEM DESCRIPTION: While overloading the remove method on * * an ejb, the checking defaults the * * transaction attributes for that method * * in an incorrect fashion. * **************************************************************** * RECOMMENDATION: * **************************************************************** Method attributes checking in Container code improperly reset transaction attributes for overloaded methods of EJBObject.Problem conclusion Container added code to check method name and signature in order for the transaction attributes for the method to be correctly reflected.Temporary fix Fixed handling of transaction attributes for overload methods of EJBObject. This fix is now permanent.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 #: PQ63130
IBM Group: Software Group
Modified date: Aug 6, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.