PH29087: TPV IN WAS ADMIN CONSOLE SHOWS INCORRECT ACTIVECOUNT VALUE AFTERSERVANT REGION IS RESTARTED.

APAR status

• Closed as program error.

Error description

• TPV that is part of admin console has an option to display
  ActiveCount under Thread Pools. This number should be the number
  of threads actively processing a request at the time of the
  check. Once the request completes, the count goes down. Count of
  0 means there are no active request being processed at this
  point of time.
  If a WAS servant region terminates unexpectedly with some
  requests still processing and a new servant is restarted
  automatically, the ActiveCount in TPV is still reporting
  requests that were terminated. The terminated servant counter
  value is aggregated to the value returned to the MBean and
  ultimately TPV.
  However, the newly started servant process is actually reporting
  correct value which is visible in the trace, ex:
  
  Trace: 2020/07/27 15:38:18.413 02 t=7C7608 c=UNK key=P8 tag=
  (13007004)
    SourceId: com.ibm.ws.pmi.server.modules.ThreadPoolModule
    ExtendedMessage: ThreadPool :ORB.thread.pool #threadReturn#
  ActiveCount :0
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  *                  V9.0 z/OS and V8.5.5 z/OS Edition           *
  ****************************************************************
  * PROBLEM DESCRIPTION: ThreadPool ActiveCount counter is       *
  *                      sometimes showing incorrect value.      *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When a servant process is terminated with non-zero ThreadPool
  ActiveCount value, the ActiveCount value at the time of
  termination
  will be aggregated to the ActiveCount after starting a new
  servant
  process. This will lead to incorrect reporting of the ThreadPool
  ActiveCount value.
  

Problem conclusion

• The ThreadPool ActiveCount PMI counter should be categorized
  as zOS not aggregatable, so that past servant process's value
  won't be aggregated to the counter.
  
  The fix for this APAR is targeted for inclusion in fix pack
  9.0.5.7 and fix pack 8.5.519. 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

  WEBSPHERE FOR Z

• Fixed component ID

  5655I3500

Applicable component levels