PH51644: MISS THREADID AND NOT REPORTED AS SUSPECTED LEAK

APAR status

• Closed as program error.

Error description

• In some cases, I can find that in pool content dump, some
  connections lost useful information:
  1. Some connections in local transaction has no thread id
  information,
  Shared Connection information (shared partitions 200)
  
  com.ibm.ws.LocalTransaction.LocalTranCoordImpl@1bc67550;RUNNING;
  MCWrapper id ae313dc1  Managed connection
  WSRdbManagedConnectionImpl@a4abc219
  State:STATE_TRAN_WRAPPER_INUSE Connections being held 1 Used
  with transaction
  com.ibm.ws.LocalTransaction.LocalTranCoordImpl@1bc67550;RUNNING;
  
  2. Some connections not in any transaction has no thread id
  inforamtion, when the connections was long hold, also not
  reported as suspected leak connection under Connection Leak
  Logic Information with stack trace of the thread when it request
  to allocate the connection:
  UnShared Connection information
      MCWrapper id d5abaf6e  Managed connection
  WSRdbManagedConnectionImpl@920ee66c  State:STATE_ACTIVE_INUSE
  Connections being held 1 Start time inuse Fri May 14 02:47:11
  EDT 2021 Time inuse 16026 (seconds)  Last allocation time Wed
  Dec 31 19:00:00 EST 1969
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server  In some cases, I can find that in   *
  *                  pool content dump, some connections lost    *
  *                  useful information                          *
  ****************************************************************
  * PROBLEM DESCRIPTION: In some cases, I can find that in pool  *
  *                      content dump, some connections lost     *
  *                      thread information.                     *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  In some cases, I can find that in pool content dump, some
  connections lost useful information:
  1. Some connections in local transaction has no thread id
  information,
  Shared Connection information (shared partitions 200)
  com.ibm.ws.LocalTransaction.LocalTranCoordImpl@1bc67550;RUNNING;
  MCWrapper id ae313dc1  Managed connection
  WSRdbManagedConnectionImpl@a4abc219
  State:STATE_TRAN_WRAPPER_INUSE Connections being held 1 Used
  with transaction
  com.ibm.ws.LocalTransaction.LocalTranCoordImpl@1bc67550;RUNNING;
  2. 2. Some connections not in any transaction has no thread id
  inforamtion, when the connections was long hold, also not
  reported as suspected leak connection under Connection Leak
  Logic Information with stack trace of the thread when it request
  to allocate the connection:
  UnShared Connection information
  MCWrapper id d5abaf6e  Managed connection
  WSRdbManagedConnectionImpl@920ee66c  State:STATE_ACTIVE_INUSE
  Connections being held 1 Start time inuse Fri May 14 02:47:11
  EDT 2021 Time inuse 16026 (seconds)  Last allocation time Wed
  Dec 31 19:00:00 EST 1969
  3. When reserve exit, the connection's information doesn't
  contain threadname yet, need to check later trace to find the
  thread name.
  

Problem conclusion

• With this APAR, I added attributes: nativeThreadid, when the
  thread is not JEE thread ID, set native thread id to threadid.
  
  With the native threadid, you can map it to native threadid in
  javacore.
  
  At same time, if stacktrace is null, set it with new Throwable()
  to avoid in suspected leak part, the connection can't be listed.
  
  In trace of ConnectionManager before allocateConnection exit,
  print the connection's information which already have threadid
  to make trace analysis easier.
  
  The fix for this APAR is targeted for inclusion in fix pack
  9.0.5.15. 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