APAR status
Closed as program error.
Error description
Many WebContainer threads are hung SessionsLRUOffloader and following stack is observed. ThreadMonitor W WSVR0605W: Thread "WebContainer : 48" (0000010c) has been active for 628553 milliseconds and may be hung. There is/are 47 thread(s) in total in the server that may be hung. at java.lang.Object.wait(Native Method) at java.lang.Object.wait(Object.java:167) at com.ibm.ws.xs.sessionmanager.SessionsLRUOffLoader.checkAndWaitLo ckKey(Se ssionsLRUOffLoader.java:285) at com.ibm.ws.xs.sessionmanager.SessionsLRUOffLoader.accessObject(S essionsL RUOffLoader.java:560) at com.ibm.ws.xs.sessionmanager.HttpSessionRequestWrapper.getSessio n(HttpSe ssionRequestWrapper.java:648) at com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(Page Filter.j ava:47) at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(Fi lterInst anceWrapper.java:195) at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebApp FilterCh ain.java:91) at com.ibm.ws.xs.sessionmanager.HttpSessionFilter.doFilter(HttpSess ionFilte r.java:508) at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(Fi lterInst anceWrapper.java:195) at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebApp FilterCh ain.java:91) at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebA ppFilter Manager.java:928) at com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters (WebAppF ilterManager.java:1025)
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users of WebSphere eXtreme Scale HTTP * * session * * management. * **************************************************************** * PROBLEM DESCRIPTION: A hung thread detection message is in * * the * * WebSphere Application server web * * container. * **************************************************************** * RECOMMENDATION: * **************************************************************** Messages similar to the following messages are logged in the SystemOut and trace log files: ThreadMonitor W WSVR0605W: Thread "WebContainer : 8" (0000009a) has been active for 726089 milliseconds and may be hung. There is/are 1 thread(s) in total in the server that may be hung. When the session ID from a request does not match the WebSphere eXtreme Scale session ID cookie, a permanent lock results on the WebSphere eXtreme Scale session ID key. Subsequent requests that contain this WebSphere eXtreme Scale session ID key are waiting indefinitely, resulting in the hung thread warnings.
Problem conclusion
WebSphere eXtreme Scale ensures that any keys that are locked during a request are unlocked by the end of the request.
Temporary fix
Comments
APAR Information
APAR number
PI05917
Reported component name
WS EXTREME SCAL
Reported component ID
5724X6702
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-11-11
Closed date
2013-12-02
Last modified date
2013-12-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
WS EXTREME SCAL
Fixed component ID
5724X6702
Applicable component levels
R860 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSTVLU","label":"WebSphere eXtreme Scale"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
02 December 2013