Fixes are available
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
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
The check to see if a distributed activity context is involved in a loop back request does not allow for multiple active requests. This results in the property group from being added to an index greater than the array size. This can result in the following error... [12/28/10 13:42:11:151 JST] 000000bf ORBRas 1 com.ibm.rmi.pi.InterceptorManager iterateServerInterceptors:557 ORB.thread.pool : 0 The following exception was logged java.lang.IndexOutOfBoundsException: Index: 1, Size: 0 at java.util.ArrayList.add(ArrayList.java:394) at com.ibm.ws.activity.remote.DistributedActivityContext.checkForLo opback(DistributedActivityContext.java:698) at com.ibm.ws.activity.remote.DistributedActivityContext.reimport(D istributedActivityContext.java:725) at com.ibm.ws.activity.remote.ServerSideProcessor.processRequest(Se rverSideProcessor.java:179) at com.ibm.ws.activity.remote.cos.ActivityServiceServerInterceptor. receive_request(ActivityServiceServerInterceptor.java:274) at com.ibm.rmi.pi.InterceptorManager.invokeInterceptor(InterceptorM anager.java:631) at com.ibm.rmi.pi.InterceptorManager.iterateServerInterceptors(Inte rceptorManager.java:531) at com.ibm.rmi.pi.InterceptorManager.iterateReceiveRequest(Intercep torManager.java:777) at com.ibm.CORBA.iiop.ServerDelegate.dispatchInvokeHandler(ServerDe legate.java:616) at com.ibm.CORBA.iiop.ServerDelegate.dispatch(ServerDelegate.java:4 80) at com.ibm.rmi.iiop.ORB.process(ORB.java:512) at com.ibm.CORBA.iiop.ORB.process(ORB.java:1571) at com.ibm.rmi.iiop.Connection.respondTo(Connection.java:2717) at com.ibm.rmi.iiop.Connection.doWork(Connection.java:2582) at com.ibm.rmi.iiop.WorkUnitImpl.doWork(WorkUnitImpl.java:62) at com.ibm.ejs.oa.pool.PooledThread.run(ThreadPool.java:118) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1473)
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V6.1 and V7.0 * **************************************************************** * PROBLEM DESCRIPTION: The check to see if a distributed * * activity context is involved in a * * loop back request does not allow * * for multiple active requests. This * * results in the property group from * * being added to an index greater than * * the array size. This can result in an * * IndexOutOfBoundsException: * **************************************************************** * RECOMMENDATION: * **************************************************************** The check to see if a distributed activity context is involved in a loop back request does not allow for multiple active requests. This results in the property group from being added to an index greater than the array size. There are two scenarios that we are aware of whereby multiple active requests could be handled at the same time. 1. If Server A makes a request to Server B, then as part of the activity on Server B a request is made to Server A. Now on Server A there will be two active requests that could be processed at the same time. 2. If there is an error condition on Server A and the Activity request information is not cleaned up on the current thread properly. Then subsequently this thread is used to run a second Activity request, there could be two active requests being processed at the same time.
Problem conclusion
The property group has been modified so that it can handle multiple active requests being processed at the same time. The fix for this APAR is currently targeted for inclusion in fix packs 6.1.0.39 and 7.0.0.17. 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
PM30271
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
61I
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-01-12
Closed date
2011-02-10
Last modified date
2011-02-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
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
R700 PSY
UP
Document Information
Modified date:
27 October 2021