DB2 FOR LUW / DB2FORLUW / 910 - DB2

When the JDBC/JCC driver switches between XA (2 phase commit) 
local/global transactions in some cases it may not reuse an 
existing TransportObject.  Instead it creates a new connection 
which results in a connection leakage and you may notice that 
increasing JDBC property maxTransportObject may delay the amount 
of time before the application hangs. 
 
Another possible symptom is XAER_OUTSIDE (Resource Manager doing 
work outside global transaction) or hang when trying to start a 
new XA transaction. 
 
This error applies only when the JDBC/JCC driver is connected to 
DB2 for z/OS using the XA connection.

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See ERROR DESCRIPTION.                                       * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade the JDBC/JCC driver to the one included with v9.1    * 
* Fixpack 10.                                                  * 
****************************************************************

Set JDBC/JCC property: 
 
queryCloseImplicit=DB2BaseDataSource.QUERY_CLOSE_IMPLICIT_NO (2) 
 
Please note this workaround only resolves the XAER_OUTSIDE 
issue.  It does not resolve the hang or connection leakage 
problem.

Upgrade the client application to use the JDBC/JCC driver 
included with v9.1 Fixpack 10.

N/A

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

09.04.2010
16.06.2011
16.06.2011

9.1.,
9.1.FP10