PI12978: DB2 INSERT IS ROLLED BACK FOR UNKNOWN REASON

Fixes are available

APAR status

Closed as program error.

Error description

Application running in WebSphere Application Server does an
INSERT into a DB2 table. The INSERT seems to run fine and the
application does a COMMIT then (AUTOCOMMIT is set to FALSE).
COMMIT() returns null which means the COMMIT worked fine.
Once the application ends a ROLLBACK is done for the previously
COMMITted INSERT for unknown reasons.
.
Servant region joblog (SYSPRINT) shows:
WLTC0032W: One or more local transaction resources were rolled
           back during the cleanup of a
           LocalTransactionContainment.
.
Extensive tracing in WebSphere and JDBC driver reveals that the
COMMIT was done on a different connection than the original
INSERT was done.
By means of a debug module L3 figurred out finally that the
underlying sqljconnection was not reassociated properly after
the dissociation due to which there were 2 connection objects.
.
Note:
With unshared connection problem does not occur.

Local fix

Use unshareable connections

KC article regarding Connection Handles and shared vs unshared:
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=p
hil&product=was-nd-mp&topic=cconpconh

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server releases v7,v8,v855 when             *
*                  SQLJConnection is used.                     *
****************************************************************
* PROBLEM DESCRIPTION: When Shareable Connections is used      *
*                      and DB2 SQLJConnection is used to do    *
*                      jdbc operation, if the connection is    *
*                      not properly closed and a dissociate    *
*                      happens the connection handle may get   *
*                      associated to the wrong underlying      *
*                      SQLJConnection.                         *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
This is because when dissociate happens it would reset the
jdbc connection however the SQLJConnection was not getting
reset hence the wrong association.

Problem conclusion

Code changes have been done to reset the SQLJConnection as
well during a dissociate.

APAR PI12978 is currently targeted for inclusion in Fix Packs
8.0.0.10 and 8.5.5.4 of WebSphere Application Server.

Sysroute APAR PI19932 will be used to deliver this fix in
WebSphere Application Server V7.0 for z/OS.

Please refer to the Recommended Updates page for delivery
information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

In addition, please refer to URL:
http://www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
for Fix Pack PTF information.

Temporary fix

Comments

APAR Information

APAR number
PI12978
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-03-04
Closed date
2014-06-12
Last modified date
2015-06-04

APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:

PI19932

Fix information

Fixed component name
WEBSPHERE FOR Z
Fixed component ID
5655I3500

Applicable component levels

R800 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"800","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 April 2022

Tips

PI12978: DB2 INSERT IS ROLLED BACK FOR UNKNOWN REASON

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R800 PSY

Document Information

Share your feedback

Need support?