IT13186: JDBC CONNECTION POOL CAN BECOME FULL OF STALE CONNECTIONS

APAR status

• Closed as program error.

Error description

• When a JDBC connection is specifically terminated from the
  database side it is possible that the connection is not
  properly removed from the connection pool, even after a message
  flow thread has thrown an exception due to the broken
  connection.
  
  Under this circumstance, the connection pool can eventually
  become full and the following error is observed for every flow
  invocation:
  
  BIP6269E: A request for a JDBC connection from pool 'myPool'
  has timed out after waiting for 15010 milliseconds.
  
  The expected behaviour is that the first time a broken
  connection is used an exception is thrown by the JDBC API call.
   This ensures that this connection will be removed from the
  connection pool and will therefore not be eligible for re-use.
  
  In some cases this is not happening and the same broken
  connection is given to a message flow thread repeatedly.
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users of WebSphere Message Broker V8 or IBM Integration Bus
  V9 and V10 using JDBC.
  
  
  Platforms affected:
  z/OS, MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  When a JDBC connection is specifically terminated from the
  database side it is possible that the connection is not properly
  removed from the connection pool, even after a message flow
  thread has thrown an exception due to the broken connection.
  
  Under this circumstance, eventually the connection pool can
  become full and the following error is observed for every flow
  invocation:
  
  BIP6269E: A request for a JDBC connection from pool 'myPool' has
  timed out after waiting for 15010 milliseconds.
  
  The expected behaviour is that the first time a broken
  connection is used an exception is thrown by the JDBC API call.
  This ensures that this connection will be removed from the
  connection pool and will therefore not be eligible for re-use.
  
  In some cases this is not happening and the same broken
  connection is given to a message flow thread repeatedly.
  
  
  
  
  There are a number of resource name changes between WebSphere
  Message Broker and IBM Integration Bus Version 9.0.  For details
  visit
  http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.e
  tools.mft.doc/bb23814_.htm
  

Problem conclusion

• The JDBC nodes now correctly remove stale connections from the
  connection pool.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v8.0       8.0.0.8
  v9.0       9.0.0.6
  v10.0      10.0.0.5
  
  The latest available maintenance can be obtained from:
  http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041
  
  If the maintenance level is not yet available,information on
  its planned availability can be found on:
  http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308
  ---------------------------------------------------------------
  

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

  INTEGRATION BUS

• Fixed component ID

  5724J0540

Applicable component levels

• RA00 PSY

     UP