DB2 CONNECT / DB2CONNCT / B50 - DB2

During XA Transaction, when XAER_RMFAIL is received from server,
such connections are not isolated, closed and removed from
connection pool.

for XAConnections, server might return XAER_RMFAIL for certain
transaction processing that are piggy backed. xa.start() and
xa.end() can be seen piggy backed with next xa operation
(prepare/commit/rollback) and server might return XAER_RMFAIL
for the xa.start() or xa.end() is the chained execution
response. If this occurs, then such connection need to be closed
by application.
In order to facilitate application to close such connection, JCC
driver will raise ConnectionEvent according to
ConnectionEventListener interface specification.
Application need to implement such Connection event listener
interface to receive XAER_RMFAIL event.

****************************************************************
* USERS AFFECTED:                                              *
* ALL Db2 Connect users                                        *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to JCC driver on Db2 version V11.5.7.0               *
****************************************************************

set xaNetworkOptimization=false

****************************************************************
* USERS AFFECTED:                                              *
* ALL Db2 Connect users                                        *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to JCC driver on Db2 version V11.5.7.0               *
****************************************************************

Fixed in Db2 V11.5.7.0 and later

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

15.07.2021
03.09.2021
03.09.2021