Fixes are available
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
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.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
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.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
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.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
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.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
For a cluster with only one member, the member can be started but the cluster status remains "partial start".
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server Network Deployment Version 8.0 and * * above * **************************************************************** * PROBLEM DESCRIPTION: For a cluster with only one member, * * the member can be started * * but the cluster status remains * * "partial start". * **************************************************************** * RECOMMENDATION: * **************************************************************** The problem occurs because of a timing condition where the node agent is not ready to add the dmanager as a notification listener. As a result, the started notification does not get sent to the dmgr. Trace shows the following: addRemoteListener failed during dmgr discovering nodeagent with error below: [6/20/14 12:13:31:707 CEST] 0000002f DownstreamSer 1 QueueConsumerThread[0](Q0): addServer: ConnectorException: com.ibm.websphere.management.exception.ConnectorNotAvailableExce ption at com.ibm.ws.management.discovery.ServerInfo.getAdminClient(Server Info.java:221) at com.ibm.ws.management.event.DownstreamServerManager.getRemotePro xy(DownstreamServerManager.java:296) at com.ibm.ws.management.event.DownstreamServerManager.addRemoteLis tener(DownstreamServerManager.java:234) at com.ibm.ws.management.event.DownstreamServerManager.createDSMEnt ry(DownstreamServerManager.java:350) at com.ibm.ws.management.event.DownstreamServerManager.access$100(D ownstreamServerManager.java:71) at com.ibm.ws.management.event.DownstreamServerManager$QueueConsume rThread.addServer(DownstreamServerManager.java:1228) at com.ibm.ws.management.event.DownstreamServerManager$QueueConsume rThread.run(DownstreamServerManager.java:1186) at java.lang.Thread.run(Thread.java:773) [6/20/14 12:13:31:708 CEST] 0000002f DownstreamSer < QueueConsumerThread[0](Q0): addServer Exit
Problem conclusion
Code is changed to have another retry when dmgr failed to addRemoteListener to nodeagent during discovery process. The fix for this APAR is currently targeted for inclusion in fix pack 8.0.0.10 and 8.5.5.4. 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
PI21377
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-07-04
Closed date
2014-09-10
Last modified date
2014-09-10
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
R800 PSY
UP
R850 PSY
UP
Document Information
Modified date:
28 April 2022