PQ87308: DB2 connections getting modified to "autocommit=false" even when it created with "autocommit=true" | |||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description Customer reported seeing the following: ./bborjtr.cpp+820 ... BBOO0220E WLTC0033E: Resource jdbc/COMP_V10 rolled back in cleanup of unresolved LocalTransactionContainment.com. ibm.ws.LocalTransaction.LocalTransaction com.ibm.ws.LocalTransaction.LocalTransaction They have also seen the following after a few hours: ExtendedMessage: Closing handle for ManagedConnection@5e24f302 from pool jdbc/COMP_V92 from mcWrapper MCWrapper id 5d0ab302 Manag ed connection com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl@5e24f302 Customer has set "autocommit=true", so in the connection pool, each newly obtained DB2 connection is created with "autocommit=true". Each new connection is set up to "do the commit" after every update. However, at least one of the connections seems to be getting modified to "autocommit=false" at some point. The affected connection is returned to the pool without setting "autocommit" back to true. Later this pooled connection is returned to active use, but updates performed by a bean method within a local tran do not get committed automatically. At the end of the local tran (since no commits have yet been performed within the local transaction) then the "unresolvedaction" for the bean method is performed by the container: either rollback or commit. If you do not explicitly set the action to 'commit' then the updates will NOT be committed as you need.Local fix The workaround is to explicitly set the 'unresolvedaction=commit', that is to set the UnResolver Action to 'commit' during deployment. Then the updates WILL be committed as you need.Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V5.0 for z/OS * **************************************************************** * PROBLEM DESCRIPTION: WLTC0033E error messages can occur due * * to JDBC Connections enlisting in Local * * Transaction Containments despite the * * fact that the default value for auto * * commit is true and auto commit was * * never explicitly set to false. * **************************************************************** * RECOMMENDATION: * **************************************************************** In certain instances, WebSphere detects that the auto commit value on a JDBC Connection is false, when in fact it is true. This causes the JDBC Connection to be enlisted in Local Transaction Containments while still committing after every execution of an SQL statement. An exception similar to the following may appear in the joblog of your application servant region in situations where the application is expecting to use JDBC Connections with an auto commit value of true: ./bborjtr.cpp+820 ... BBOO0220E WLTC0033E: Resource jdbc/COMP_V10 rolled back in cleanup of unresolved LocalTransactionContainment.com.ibm.ws.LocalTransaction .LocalTransaction com.ibm.ws.LocalTransaction.LocalTransaction It is important to note that no work is actually rolled back in this situation because each SQL statement was committed upon execution.Problem conclusion WebSphere Application Server V5.0 for z/OS code now properly tracks the auto commit state and therefore does not enlist JDBC Connections in a Local Transaction Containment when the auto commit value on the JDBC Connection is true. APAR PQ87308 is associated with SERVICE LEVEL W502010 of WebSphere Application Server V5.0 for z/OS.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: PQ89822 Modules/Macros
Publications Referenced
|
Document Information |
Current web document: swg1PQ87308.html
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server for z/OS
Operating system(s):
Software version: 500
Software edition:
Reference #: PQ87308
IBM Group: Software Group
Modified date: Nov 9, 2004
(C) Copyright IBM Corporation 2000, 2009. All Rights Reserved.