PQ70159: TRANSACTION ATTRIBUTE (TX_REQUIRED) IS INCORRECTLY CHANGED WHEN APPLICATION IS RUN IN WEBSPHERE Z/OS WHEN ARRAY IS IN SIGNATURE | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description Customer application has methods defined within a container transaction. The Trans-Attribute for the container-transaction is 'Required'. Looking at the application in AAT, you can see that the Transaction Attribute for each method is set to 'Required'. Also in the 'ejb-jar.xml' file within the 'application.ear'file you see tag <trans-attribute>Required</trans-attribute> within the <container-transaction> tag. If the method 'signature' contains an 'array', the Transaction Attribute of the method which contains an array may be set to an incorrect value, when the application server starts. . The problem the users sees is that the 'Transaction Context' is 'switched' when this method is called, during application code execution. . Additional Symptom: timeout SQLCODE=-913 SQLSTATE=57033 (00C9008E) in the application Server region, due to the one thread being started with a different transaction context, even though all of the session beans have the Transaction Attribure set to 'Required'.Local fix Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V4.0.1 for z/OS and OS/390 * **************************************************************** * PROBLEM DESCRIPTION: Customers deploying an application * * which contains an array in EJB method * * signature may be assigned wrong * * transaction attribute during runtime * * but will be registered properly in SM * * DB2's method level deployment info. * **************************************************************** * RECOMMENDATION: * **************************************************************** Customer application has methods defined within a container transaction. The Trans-Attribute for the container-transaction is 'Required'. Looking at the application in AAT, you can see that the Transaction Attribute for each method is set to 'Required'. Also in the 'ejb-jar.xml' file within the 'application.ear'file you see tag <trans-attribute>Required</trans-attribute> within the <container-transaction> tag. If the method 'signature' contains an 'array', the Transaction Attribute of the method which contains an array may be set to an incorrect value, when the application server starts.Problem conclusion Support has been modified to assign the correct transaction attribute during runtime for all methods, including methods that contain array type in their signature. APAR PQ70159 is associated with SERVICE LEVEL W401502 of WebSphere Application Server V4.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: UQ75293 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 #: PQ70159
IBM Group: Software Group
Modified date: Apr 3, 2003
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.