Fixes are available
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
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
Obtain the fix for this APAR.
APAR status
Closed as program error.
Error description
It is possible that WAS can ignore a notifcation that an Activity completed. If the Activity Session (AS) then times out there is a possibility that the AS can hang pending a notification. At this point depending on server configuration the thread will either hang or cause an HTTP request time out. Also, depending on the server configuration the HTTP request time out can cause an EC3 ABEND. The hung thread Java Stack: Java stack: ----------- Method Location ------ -------- java/lang/Object.wait Object.java java/lang/Object.wait Object.java:199 com/ibm/ws/ActivitySession/ASessWebInvocationCollaborator.preInv oke ASessWebInvocationCollaborator.java:211 com/ibm/ws/wswebcontainer/servlet/ServletWrapper.handleRequest ServletWrapper.java:461 com/ibm/ws/webcontainer/servlet/CacheServletWrapper.handleReques t CacheServletWrapper.java:90 com/ibm/ws/webcontainer/WebContainer.handleRequest WebContainer.java:744 com/ibm/ws/wswebcontainer/WebContainer.handleRequest WebContainer.java:1455 com/ibm/ws/webcontainer/channel/WCChannelLink.ready WCChannelLink.java:115
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V6.1.0 * **************************************************************** * PROBLEM DESCRIPTION: If an Activity Session (AS) that is * * linked to an HTTP Session times out * * when the request is with the client, * * the AS can hang when the request is * * received back on the server, pending * * a notification that the state has * * changed. This notification will * * never occur. The thread hang shows * * the following stack : * * * * com/ibm/ws/ActivitySession/ASessWebInvo * * cationCollaborator.preInvoke * * ASessWebInvocationCollaborator.java:211 * * com/ibm/ws/wswebcontainer/servlet/Servl * * etWrapper.handleRequest * * ServletWrapper.java:461 * * com/ibm/ws/webcontainer/servlet/CacheSe * * rvletWrapper.handleRequest * * CacheServletWrapper.java:90 * * com/ibm/ws/webcontainer/WebContainer.ha * * ndleRequest WebContainer.java:744 * * com/ibm/ws/wswebcontainer/WebContainer. * * handleRequest WebContainer.java:1455 * * com/ibm/ws/webcontainer/channel/WCChann * * elLink.ready WCChannelLink.java:115 * **************************************************************** * RECOMMENDATION: * **************************************************************** When an Activity Session that is linked to an HTTP Session times out, the timeout is processed immediately, and the Activity is completed as designed. However, if the timeout occurs during the period when the request is back with the client, the next linked HTTP request that arrives attempts to resume the linked Activity Session, which succeeds even though the Activity is now completed. During subsequent processing of incoming requests, the Activity Session state is now incorrect, and the processing thread hangs in the collaborator preinvoke.
Problem conclusion
Correct the timeout processing of an Activity Session linked to an HTTP Session, in the circumstances when the timeout occurs when the request is back with the client. APAR PM24502 is currently targeted for inclusion in Service Level (Fix Pack) 6.1.0.37 of WebSphere Application Server V6.1 Please refer to URL: //www.ibm.com/support/docview.wss?rs=404&uid=swg27006970 for Fix Pack availability.
Temporary fix
Comments
APAR Information
APAR number
PM24502
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
610
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-10-14
Closed date
2010-12-20
Last modified date
2011-05-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
WEBSPHERE FOR Z
Fixed component ID
5655I3500
Applicable component levels
R610 PSY UK65883
UP11/04/06 P F104
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
Document Information
Modified date:
25 October 2021