Fixes are available
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
APAR status
Closed as program error.
Error description
On WebSphere Application Server V7.0 while stopping a cluster, the nodeagent is not propagating the appserver's stopped notification due to NodeAgentStatusCache refresh of whole node. Problem noticed by customer can be application server status is slow to display in the administrative console and/or intermittent issues with stopping and starting a cluster. From javacore: 3XMTHREADINFO3 Java callstack: 4XESTACKTRACE at java/lang/Thread.sleep(Native Method) 4XESTACKTRACE at java/lang/Thread.sleep(Thread.java:851(Compiled Code)) 4XESTACKTRACE at com/ibm/ws/management/status/NodeAgentStatusCache$StatusCacheTim edThread.run(NodeAgentStatusCache.java:785(Compiled Code)) Follow nodeagent's trace log with management tracing: [1/8/12 2:03:48:682 CST] 0003827b NodeAgentStat 3 addToCache Stack Trace java.lang.Exception: addtoCache: at java.lang.Throwable.<init>(Throwable.java:67) at com.ibm.ws.management.status.NodeAgentStatusCache.addToCache(Nod eAgentStatusCache.java:623) at com.ibm.ws.management.nodeagent.NodeAgent.addAdoptedChild(NodeAg ent.java:2456) at com.ibm.ws.management.nodeagent.NodeAgent.monitorProcess(NodeAge nt.java:2339) at com.ibm.ws.management.nodeagent.NodeAgent.handleNotification(Nod eAgent.java:2114) at com.ibm.ws.management.event.ListenerInfo$1.run(ListenerInfo.java :137) at com.ibm.ws.security.auth.ContextManagerImpl.runAs(ContextManager Impl.java:4672) at com.ibm.ws.security.auth.ContextManagerImpl.runAsSystem(ContextM anagerImpl.java:4760) at com.ibm.ws.management.event.ListenerInfo.handleNotification(List enerInfo.java:153) at com.ibm.ws.management.event.NotificationDispatcher$DispatchANoti ficationToAListener.run(NotificationDispatcher.java:372) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1604)
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * Network Deployment edition, V7.0 and V8.0. * **************************************************************** * PROBLEM DESCRIPTION: Nodeagent status and performance * * issue when stopping a group of * * application servers like a cluster. * **************************************************************** * RECOMMENDATION: * **************************************************************** While stopping a cluster, the application server status is slow to display in the administrative console. Also, intermittent issues with stopping/starting cluster members due to their status being inaccurate. The nodeagent status cache is gathering status from all the servers on the node which delays some notifications to the DeploymentManager server.
Problem conclusion
Nodeagent status cache code was modified to update the cache more efficiently which allows the notifications to get to the DeploymentManager more quickly. The fix for this APAR is currently targeted for inclusion in fix packs 7.0.0.23 and 8.0.0.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
PM55922
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-01-12
Closed date
2012-03-02
Last modified date
2012-03-02
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
R700 PSY
UP
Document Information
Modified date:
28 October 2021