Fixes are available
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
Command generated using administrative console command line assistance failed to run in the wsadmin adminclient. "Performance Monitoring Infrastructure > server1 > Runtime > Custom >Thread pools > Default" - then enabled a couple of PMI indicators which were disabled. The following statement will be generated in the command assistance log file for this operation: AdminControl.invoke('WebSphere:name=PerfPrivateMBean,process=ser ver1,platform=dynamicproxy,node=Node1,version=8.5.5, type=PerfPrivate,mbeanIdentifier=PerfPrivateMBean,cell=PSCell1, spec=1.0', 'updatePMIConfig', '[[threadPoolModule Default] threadPoolModule [3 4 9 5 10] [] true]', '[[Ljava.lang.String; java.lang.String [Ljava.lang. Integer; [Ljava.lang.Integer; java.lang.Boolean]') Try this as part of a Jython script - this will fail with error WASX7017E: Exception received while running file "c:\test. py"; exception information: java.lang.StringIndexOutOfBoundsException: java.lang.StringIndexOutOfBoundsException Other components like object pools will also result in the same StringIndexOutOfBoundsException.
Local fix
AdminControl.invoke('WebSphere:name=PerfPrivateMBean,process=ser ver1,platform=dynamicproxy,node=Node1,version=8.5.5.1, type=PerfPrivate,mbeanIdentifier=PerfPrivateMBean,cell=PSCell1, spec=1.0', "updatePMIConfig",'[[threadPoolModule Default] threadPoolModule [3 4 9 5 10] [] true]')
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server using the administrative console to * * obtain command assistance for invoke * * commands. * **************************************************************** * PROBLEM DESCRIPTION: The console should not include * * the signature when creating command * * assistance for * * AdminControl.invoke(). * **************************************************************** * RECOMMENDATION: * **************************************************************** The command assistance provided by the administrative console for invoke commands includes the signature as the last parameter. AdminControl.invoke fails when the signature is provided.
Problem conclusion
The console no longer includes the signature as a parameter for AdminControl.invoke(). The fix for this APAR is currently targeted for inclusion in fix pack 8.5.5.7. 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
PI39360
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-04-20
Closed date
2015-06-17
Last modified date
2015-06-17
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