PI19932: DB2 INSERT IS ROLLED BACK FOR UNKNOWN REASON

Obtain the fix for this APAR.

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 V7.0 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    *
  *                      When Shareable Connections is used      *
  *                      and DB2 SQLJConnection is used to do    *
  *                      jdbc operation, if the connection is    *
  *                      not properly closed and a dissociate    *
  ****************************************************************
  * 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 PI19932 is currently targeted for inclusion in Fix Pack
  7.0.0.35 of WebSphere Application Server.
  
  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 is sysrouted FROM one or more of the following:

  PI12978

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

Modules/Macros

•    BBGUBINF BBOUBINF
  

Fix information

• Fixed component name

  WEBSPHERE FOR Z

• Fixed component ID

  5655I3500

Applicable component levels

• R700 PSY UI21695

     UP14/10/10 P F410

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.