Fixes are available
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
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
Copy of: 8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
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
WebSphere Applicaiton Server 8.5.5. Intelligent Managerment. If the Intelligent Management Application Placement Controller (APC) is running on a node, along with multiple members of dynamic clusters, the node will not go into Maintenance Mode (MM). The admin console will show that MM is being applied for more than 10 minutes, and eventually will fail to put the node into MM. This error will be put in the SystemOut.log file: NodeGroupXDUt E NGRP0009E: Error invoking setMaintenanceMode on node YOUR_NODE_NAME, newValue: true leaveProcessesRunning: true Exception: ""
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server 8.5.5 * **************************************************************** * PROBLEM DESCRIPTION: WAS 8.5.5. Node with APC and multiple * * dynamic cluster members does not move * * into maintenance mode. * **************************************************************** * RECOMMENDATION: * **************************************************************** When setting Node in maintenance mode, the list of servers which need to be placed in maintenance was incorrect. This caused the Node not to go into maintenance mode as all the servers could not go in to maintenance mode.
Problem conclusion
The code is fixed to properly create servers list that needs to be moved to maintenance mode. The fix for this APAR is currently targeted for inclusion in the fix pack 8.5.5.5 Please refer to the Recomended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PI29980
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2014-11-19
Closed date
2015-02-13
Last modified date
2015-02-13
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 APP S
Fixed component ID
5724J0800
Applicable component levels
R850 PSY
UP
Document Information
Modified date:
28 April 2022