PH55245: ALLOW JTA TRANSACTION TIMEOUT TO SKIP JDBC 4.1+ DATASOURCE ABORT MECHANISM AND BEHAVE AS PER OLDER JDBC DATASOURCE

APAR status

• Closed as program error.

Error description

• ALLOW JTA TRANSACTION TIMEOUT TO SKIP JDBC 4.1+ DATASOURCE
  ABORT MECHANISM AND BEHAVE AS PER OLDER JDBC DATASOURCE
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: ALLOW JTA TRANSACTION TIMEOUT TO SKIP   *
  *                      JDBC 4.1+ DATASOURCE ABORT MECHANISM    *
  *                      AND BEHAVE AS PER OLDER JDBC            *
  *                      DATASOURCE                              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  If an XAResource for a JDBC Connection from a JDBC 4.1, or
  higher, Datasource is enlisted with a JTA transaction, the
  transaction timeout process invokes abort on the Connection.
  This is a change in behaviour from transaction timeout
  processing for Connections from earlier versions of JDBC
  datasources and while usage of the abort mechanism is generally
  preferable, it can excercise different Exception
  handling paths in applications that may not have been
  anticipated when, for example, updating a datasource or
  migrating from an earlier version of WebSphere Application
  Server.
  

Problem conclusion

• To revert the behaviour of JTA transaction timeout processing
  to that used in WebSphere Application Server 8.5.5, or when
  using a JDBC Datasource that supports versions of the JDBC
  Specification earlier than 4.1, a JVM System Property can now
  be configured:
  
  com.ibm.ws.JDBC.abortDisabled=true
  
  By default, ie without configuration of this property,
  behaviour remains unchanged.
  
  The fix for this APAR is targeted for inclusion in fix pack
  9.0.5.17. For more information, see 'Recommended Updates for
  WebSphere Application Server':
  https://www.ibm.com/support/pages/node/715553
  

Temporary fix

Comments

APAR Information

• 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

  WEBSPHERE APP S

• Fixed component ID

  5724J0800

Applicable component levels