APAR status
Closed as program error.
Error description
When the ContainerWork thread pool is consumed, threads that attempt to put work on that thread pool will wait until the ContainerWork thread pool has an available thread. See the following example of messages that indicate thread hangs: [8/8/13 17:56:12:893 EDT] 00000065 XSThreadPool W CWOBJ7853W: Detected a hung thread named "XIOPrimaryPool : 201" TID:17fa TIMED_WAITING. Executing since 8/8/2013 17:55:44:294 -0400. Stack Trace: java.lang.Object.wait(Native Method) java.lang.Object.wait(Object.java:196) com.ibm.ws.util.BoundedBuffer.waitPut_(BoundedBuffer.java:214) com.ibm.ws.util.BoundedBuffer.put(BoundedBuffer.java:324) com.ibm.ws.util.ThreadPool.execute(ThreadPool.java:1305) com.ibm.ws.util.ThreadPool.execute(ThreadPool.java:1082) com.ibm.ws.objectgrid.thread.ThreadPoolMgrImpl$SecurityContextTh readPool.execute(ThreadPoolMgrImpl.java:181) com.ibm.ws.objectgrid.thread.ThreadPoolMgrImpl$SecurityContextTh readPool.execute(ThreadPoolMgrImpl.java:176) com.ibm.ws.objectgrid.server.container.ContainerActor.doWorkRece ive(ContainerActor.java:298) com.ibm.ws.objectgrid.server.container.ContainerActor.receive(Co ntainerActor.java:174) com.ibm.ws.xsspi.xio.actor.XIOReferable.dispatch(XIOReferable.ja va:114) com.ibm.ws.xsspi.xio.actor.XIORegistry.sendToTarget(XIORegistry. java:964) com.ibm.ws.xs.xio.transport.channel.XIORegistryRunnable.run(XIOR egistryRunnable.java:84) java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExec utor.java:1156) java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExe cutor.java:626) com.ibm.ws.objectgrid.thread.XSThreadPool$Worker.run(XSThreadPoo l.java:309)
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of eXtreme Scale. * **************************************************************** * PROBLEM DESCRIPTION: When placement events take longer, * * the transport thread pool can get * * backed up due to thread pool * * implementation. * **************************************************************** * RECOMMENDATION: * **************************************************************** The ContainerWork thread pool implementation was updated to queue waiting work instead of blocking work until a thread is available to process it.
Problem conclusion
An interim fix is available for this APAR.
Temporary fix
Comments
APAR Information
APAR number
PM95819
Reported component name
WS EXTREME SCAL
Reported component ID
5724X6702
Reported release
860
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-08-26
Closed date
2013-08-29
Last modified date
2013-08-29
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":"860","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
29 August 2013