PI96004: WHEN USING A JDBC 4.0 DRIVER IN WAS V9.0, CONNECTION, A TIMED OUT TRANSACTION CANNOT PROPERLY CLOSE CONNECTIONS

9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
WebSphere Application Server traditional 9.0.5.6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
9.0.5.9: WebSphere Application Server traditional Version 9.0.5.9
9.0.5.10: WebSphere Application Server traditional Version 9.0.5.10
9.0.5.11: WebSphere Application Server traditional Version 9.0.5.11

APAR status

• Closed as program error.

Error description

• When a transaction is timed out and by the time the transaction
  ends, the transaction manager will try to rollback and release
  the connection, but if you are using JDBC 4.0 compliant driver,
  the rollback will happen but the connections will stay in the
  pool showing used by application. This will cause long open
  connections and might lead to connection pool exhaustion.
  

Local fix

• Use JDBC 4.1 compliant JDBC driver
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server using a JDBC 4.0 or older JDBC       *
  *                  driver                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: When using a JDBC 4.0 or lower          *
  *                      compliant driver, the connections are   *
  *                      not properly closed when a              *
  *                      transaction timeout occurs.             *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  This only affects JDBC compliance level 4.0 and older JDBC
  drivers. When using an affected driver the connections are not
  properly closed when a transaction timeout occurs. This will
  cause the connections to be held open and could lead to the
  connection pool becoming full if there a lot of transaction
  timeouts. FFDCs for the following exception will also be
  created:
  java.lang.AbstractMethodError:
  java/sql/Connection.abort(Ljava/util/concurrent/Executor;)
  

Problem conclusion

• The code was updated so that connections are properly closed
  for JDBC compliant 4.0 and older drivers.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 9.0.0.8.  Please refer to the Recommended Updates
  page for delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

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

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R900 PSY

     UP