Fixes are available
8.5.0.1: WebSphere Application Server V8.5 Fix Pack 1
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
APAR status
Closed as program error.
Error description
When processing messages under load, the following FFDC may occur and the message-driven bean fails: [15/09/11 22:09:14:033 BST] FFDC Exception:java.lang.IndexOutOfBoundsException SourceId:com.ibm.ejs.container.MessageEndpointHandler.afterDeliv ery ProbeId:1280 Reporter:com.ibm.ejs.container.MessageEndpointHandler@6b4fbc java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 at java.util.ArrayList.get(ArrayList.java:347) at com.ibm.ejs.j2c.HandleList.parkHandle(HandleList.java:340) at com.ibm.ejs.container.BeanO.parkHandleList(BeanO.java:1957) at com.ibm.ejs.container.EJBThreadData.popCallbackBeanO(EJBThreadDa ta.java:256) at com.ibm.ejs.container.EJSContainer.postInvoke(EJSContainer.java: 4826) at com.ibm.ejs.container.MessageEndpointHandler.afterDelivery(Messa geEndpointHandler.java:1533) at com.ibm.ejs.container.MessageEndpointHandler.invokeMessageEndpoi ntMethod(MessageEndpointHandler.java:870) at com.ibm.ejs.container.MessageEndpointHandler.invoke(MessageEndpo intHandler.java:831) at $Proxy25.afterDelivery(Unknown Source) at com.ibm.mq.connector.inbound.AbstractWorkImpl.run(AbstractWorkIm pl.java:284) at com.ibm.ejs.j2c.work.WorkProxy.run(WorkProxy.java:608) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1650)
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server that use message-driven beans. * **************************************************************** * PROBLEM DESCRIPTION: IndexOutOfBoundsException when * * processing messages under load * **************************************************************** * RECOMMENDATION: * **************************************************************** For message-driven and stateless beans, the EJB container may perform j2c resource management after returning a bean instance to a pool. If another thread obtains the bean instance from the pool prior to the completion of the j2c resource management, then a conflict may occur resulting in various errors, though the most likely error would be as follows: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 at java.util.ArrayList.get(ArrayList.java:347) at com.ibm.ejs.j2c.HandleList.parkHandle(HandleList.java:340) at com.ibm.ejs.container.BeanO.parkHandleList(BeanO.java:1957) at com.ibm.ejs.container.EJBThreadData.popCallbackBeanO(EJBThread Data.java:256) at com.ibm.ejs.container.EJSContainer.postInvoke(EJSContainer.jav a:4826) at com.ibm.ejs.container.MessageEndpointHandler.afterDelivery(Mes sageEndpointHandler.java:1533) This error condition would most likely occur when the server is under heavy load.
Problem conclusion
The EJB container has been changed to perform any j2c resource management prior to returning a bean instance to the pool and making it availble to other threads. The fix for this APAR is currently targeted for inclusion in fix pack 8.0.0.5 and 8.5.0.1. 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
PM68782
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
2012-07-12
Closed date
2012-07-24
Last modified date
2012-07-24
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:
29 October 2021