PH60663: INCORRECT CONNECTION IN-USE TIME IN CONNLEAKLOGIC TRACE

APAR status

• Closed as program error.

Error description

• When ConnLeakLogic=all trace is enabled, if the datasource
  connection pool is exhausted and application receives
  J2CA0045E/ConnectionWaitTimeoutException, the trace will dump
  the connections in the connection pool which are suspected to be
  leaked with details and request stack trace. For instance, the
  trace shows the following connection has been in use for
  5294604ms
  
  [2024/4/1   09:28:42:986 CST] 00003980 ConnLeakLogic 3   Dumping
  initial request stack traces
  
  [2024/4/1   09:28:43:017 CST] 00003980 ConnLeakLogic 3
  MCWrapper id 3a77e9b0  Managed connection
  WSRdbManagedConnectionImpl@e06ac835
  State:STATE_TRAN_WRAPPER_INUSE Thread Id: 00000624 Thread Name:
  WebContainer : 5 Connections being held 1 Used with transaction
  com.ibm.ws.LocalTransaction.LocalTranCoordImpl@f9ab7ae9;RUNNING;
  
  in-use for 5294604ms
  
  But in the FFDC log generated when J2CA0045E is thrown, which
  also contains the connection pool dump, the same connection with
  ID WSRdbManagedConnectionImpl@e06ac835 is in use for 19s:
   MCWrapper id 3a77e9b0  Managed connection
  WSRdbManagedConnectionImpl@e06ac835
  State:STATE_TRAN_WRAPPER_INUSE Thread Id: 00000624 Thread Name:
  WebContainer : 5 Connections being held 1 Used with transaction
  com.ibm.ws.LocalTransaction.LocalTranCoordImpl@f9ab7ae9;RUNNING;
  
      Start time inuse Mon Apr 01 09:28:23 CST 2024 Time inuse 19
  (seconds)
      Last allocation time Mon Apr 01 09:28:33 CST 2024
  
  This discrepancy causes confusion.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  *                  using Data Source PMI                       *
  ****************************************************************
  * PROBLEM DESCRIPTION: Incorrect connection in-use time in     *
  *                      Connection leak trace                   *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When ConnLeakLogic=all trace is enabled, if the datasource
  connection pool is exhausted and application receives
  J2CA0045E/ConnectionWaitTimeoutException, the trace will dump
  the connections in the connection pool which are suspected to
  be
  leaked with details and request stack trace. For instance, the
  trace shows the following connection has been in use for
  5294604ms
  [2024/4/1   09:28:42:986 CST] 00003980 ConnLeakLogic 3
  Dumping
  initial request stack traces
  [2024/4/1   09:28:43:017 CST] 00003980 ConnLeakLogic 3
  MCWrapper id 3a77e9b0  Managed connection
  WSRdbManagedConnectionImpl@e06ac835
  State:STATE_TRAN_WRAPPER_INUSE Thread Id: 00000624 Thread Name:
  WebContainer : 5 Connections being held 1 Used with transaction
  com.ibm.ws.LocalTransaction.LocalTranCoordImpl@f9ab7ae9;RUNNING;
  in-use for 5294604ms
  But in the FFDC log generated when J2CA0045E is thrown, which
  also contains the connection pool dump, the same connection
  with
  ID WSRdbManagedConnectionImpl@e06ac835 is in use for 19s:
  MCWrapper id 3a77e9b0  Managed connection
  WSRdbManagedConnectionImpl@e06ac835
  State:STATE_TRAN_WRAPPER_INUSE Thread Id: 00000624 Thread Name:
  WebContainer : 5 Connections being held 1 Used with transaction
  com.ibm.ws.LocalTransaction.LocalTranCoordImpl@f9ab7ae9;RUNNING;
  Start time inuse Mon Apr 01 09:28:23 CST 2024 Time inuse 19
  (seconds)
  Last allocation time Mon Apr 01 09:28:33 CST 2024
  This discrepancy causes confusion.
  

Problem conclusion

• We fixed the discrepancy between "in-use" time in ffdc and trace
  logs.
  
  The fix for this APAR is targeted for inclusion in fix pack
  8.5.5.26 and 9.0.5.21. 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