Fixes are available
6.1.0.1: WebSphere Application Server V6.1.0 Fix Pack 1 for HP-UX
6.1.0.1: WebSphere Application Server V6.1.0 Fix Pack 1 for AIX
6.1.0.1: WebSphere Application Server V6.1.0 Fix Pack 1 for Windows
6.1.0.1: WebSphere Application Server V6.1.0 Fix Pack 1 for Linux
6.1.0.1: WebSphere Application Server V6.1.0 Fix Pack 1 for i5/OS
6.1.0.1: WebSphere Application Server V6.1.0 Fix Pack 1 for Solaris
APAR status
Closed as program error.
Error description
The ThreadPoolMgrImpl class in the runtime.impl component is responsible for creating the thread pool statistic modules and managing the counters. The PmiThreadPoolAdapter (inner class of ThreadPoolMgrImpl) implementation of the ThreadPoolListener interface makes the following call PmiFactory.createThreadPoolPerf ( ... ) to create the thread pool modules. These modules do not seem to be created for the Work Manager (Async Bean) thread pools. They aren't showing up in the PmiRegistry trace. The Work Manager uses the WAS thread pool and has seen this stat modules show up as of 6.0.0.1.
Local fix
Fix in next release
Problem summary
**************************************************************** * USERS AFFECTED: WebSphere Application Server version 6 users * * who want to monitor Performance Monitoring * * Infrastructure (PMI) data for ThreadPools * * that are not configured beneath the * * ThreadPoolManager. * **************************************************************** * PROBLEM DESCRIPTION: ThreadPools that are not configured * * beneath the ThreadPoolManager (for * * example, Asynchbeans ThreadPools) never * * have PMI reporting enabled. * **************************************************************** * RECOMMENDATION: * **************************************************************** ThreadPoolManager iterates over all ThreadPools configured beneath it when started and enables PMI reporting for each ThreadPool if PMI has been enabled on the server. ThreadPools are not otherwise enabled for PMI reporting. Therefore, any ThreadPool that is not configured beneath the ThreadPoolManager will never have PMI reporting enabled.
Problem conclusion
ThreadPools now enable PMI reporting when they are created rather than relying on ThreadPoolManager. The fix for this APAR is currently targeted for inclusion in fixpack 6.0.2.13 and 6.1.0.1. Please refer to the recommended updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PK24993
Reported component name
WEBSPH APP SERV
Reported component ID
5724J0800
Reported release
60W
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2006-05-16
Closed date
2006-06-08
Last modified date
2006-06-08
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
RUNTIME
Fix information
Fixed component name
WEBSPH APP SERV
Fixed component ID
5724J0800
Applicable component levels
R60A PSY
UP
R60H PSY
UP
R60I PSY
UP
R60P PSY
UP
R60S PSY
UP
R60W PSY
UP
R60Z PSY
UP
R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.0","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
19 October 2021