PH37481: LEAKED CONNECTIONS IN COM.IBM.WS.BATCH.SCHEDULERSTOREFACTORY

APAR status

• Closed as program error.

Error description

• when using the batch component, The connections where created on
  line
  com.ibm.ws.batch.SchedulerSingleton.enforceJobOutputQueueLimits
  (SchedulerSingleton.java:14327)leaked.
  
  At the time of creation the Oracle Database listener was down
  for a few seconds resulting in a SQLException being thrown.
  However, the connections created during that time were never
  closed. Resulting in their connection pool filling up.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  *                  Java Batch                                  *
  ****************************************************************
  * PROBLEM DESCRIPTION: Java batch connection pool filling up   *
  *                      due to connections not being closed     *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Connection requests failed with:
  [3/14/21 8:49:11:552 EDT]     FFDC
  Exception:java.sql.SQLRecoverableException
  SourceId:com.ibm.ws.rsadapter.spi.InternalGenericDataStoreHelper
  .getPooledCon ProbeId:1298
  java.sql.SQLRecoverableException: IO Error: The Network Adapter
  could not establish the connection
  Caused by: oracle.net.ns.NetException: The Network Adapter could
  not establish the connection
  Caused by: java.io.IOException: Socket read timed out, socket
  connect lapse 10 ms. /10.66.82.6 1521 3 1 true
  Caused by: java.io.InterruptedIOException: Socket read timed
  out
  The database network adapter stopped responding to connection
  requests from the driver and wew connection requests failed with
  the above exception and were treated as stale connections. In
  flight connections stayed in the pool waiting for a response
  from the database.
  In some places, the java batch runtime which made the get
  connection requests did not properly handle the above problem
  and close the connection.
  

Problem conclusion

• A code update has been made to close connections properly in a
  get/use/close manner when an exception is encountered getting th
  connection.
  
  The fix for this APAR is targeted for inclusion in fix pack
  9.0.5.14 and 8.5.5.23. 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

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels