Fixes are available
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
APAR status
Closed as program error.
Error description
customer has problems to query the WebContainer MBean since he has updated to WAS v8.5.5.2 . WAS v8.5.5.2 on AIX (recreated the same locally on Windows) . AdminControl.queryNames('name=WebContainer,type=ThreadPool,proce ss=serve r1,*') returns two MBeans, one valid and the other one with mbeanIdentifier=null . This is causing trouble in the customer's WAS monitoring, as VMWare Hyperic (and probably other JMX related tools as well) expect only one MBean to be returned.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server ThreadPool MBeans. * **************************************************************** * PROBLEM DESCRIPTION: The Application Server exports a * * vestigial ThreadPool MBean for every * * thread pool in the server * * configuration. * **************************************************************** * RECOMMENDATION: * **************************************************************** The Application Server unexpectedly registers two ThreadPool instances for every ThreadPool declared the server configuration: a usable instance containing a valid mbeanIdentifier field, and a vestigial instance containing a null mbeanIdentifier. For example, when using the wsadmin application to query the WebContainer ThreadPool MBean: wsadmin>$AdminControl queryNames *,type=ThreadPool,name=WebContainer The application returns two MBean instances: 1. WebSphere:name=WebContainer,process=server1,platform=dynamicprox y,node=DABOT- 1Node13,version=8.5.5.5,type=ThreadPool,mbeanIdenti fier=cells/DABOT-1Node15Cell/nodes/DABOT- 1Node13/servers/server1 /server.xml#ThreadPool_1183122130079,cell=DABOT- 1Node15Cell,spec =1.0 2. WebSphere:name=WebContainer,process=server1,platform=dynamicprox y,node=DABOT- 1Node13,version=8.5.5.5,type=ThreadPool,mbeanIdenti fier=null,cell=DABOT-1Node15Cell,spec=1.0 This problem may impact applications that expect such queries to return a single MBean instance.
Problem conclusion
WebSphere Application Server was modified to export exactly one ThreadPool instance for each thread pool declared in the server configuration. The fix for this APAR is currently targeted for inclusion in fix pack 8.5.5.6. 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
PI34299
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-02-05
Closed date
2015-02-19
Last modified date
2015-02-19
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
R850 PSY
UP
Document Information
Modified date:
28 April 2022