Fixes are available
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
8.0.0.2: WebSphere Application Server V8.0 Fix Pack 2
8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
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
A http client sends in a large request. An error happens in the application processing the reqeust and the response status is set to 500. This happens before all the chunked data is received by the SR. But, when the 500 status is sent, the rest of the data is not sent to the SR, and it gets stuck in doPushService. trace back of hung tread is: com.ibm.ws390.xmem.XMemSRCppUtilities.doPushService(Native Method) com.ibm.ws390.channel.xmem.XMemReadRequestContext. read(XMemReadRequestContext.java:228) com.ibm.ws.http.channel.impl.HttpServiceContextImpl.fillABuffer (HttpServiceContextImpl.java:4140) com.ibm.ws.http.channel.impl.HttpServiceContextImpl. readSingleBlock(HttpServiceContextImpl.java:3372) com.ibm.ws.http.channel.impl.HttpServiceContextImpl. readBodyBuffer(HttpServiceContextImpl.java:3478) com.ibm.ws.http.channel.inbound.impl. HttpInboundServiceContextImpl. getRequestBodyBuffer(HttpInboundServiceContextImpl.java:1704) com.ibm.ws.webcontainer.channel.WCCByteBufferInputStream. bufferIsGood(WCCByteBufferInputStream.java:373) com.ibm.ws.webcontainer.channel.WCCByteBufferInputStream. read(WCCByteBufferInputStream.java:266) com.ibm.ws.webcontainer.srt.http.HttpInputStream. fill(HttpInputStream.java:576) com.ibm.ws.webcontainer.srt.http.HttpInputStream. skip(HttpInputStream.java:482) com.ibm.ws.webcontainer.srt.http.HttpInputStream. finish(HttpInputStream.java:178) com.ibm.ws.webcontainer.srt.http.HttpInputStream. close(HttpInputStream.java:532) com.ibm.ws.webcontainer.srt.SRTServletRequest. finish(SRTServletRequest.java:2103) com.ibm.ws.webcontainer.srt.SRTConnectionContext. finishConnection(SRTConnectionContext.java:80) com.ibm.ws.webcontainer.WebContainer. handleRequest(WebContainer.java:1034) com.ibm.ws.webcontainer.WSWebContainer. handleRequest(WSWebContainer.java:1583) com.ibm.ws.webcontainer.channel.WCChannelLink. ready(WCChannelLink.java:186) com.ibm.ws.http.channel.inbound.impl.HttpInboundLink. handleDiscrimination(HttpInboundLink.java:445) com.ibm.ws.http.channel.inbound.impl.HttpInboundLink. handleNewRequest(HttpInboundLink.java:504) com.ibm.ws.http.channel.inbound.impl.HttpInboundLink. processRequest(HttpInboundLink.java:301) com.ibm.ws.http.channel.inbound.impl.HttpInboundLink. ready(HttpInboundLink.java:275) com.ibm.ws390.channel.xmem.XMemConnLink. ready(XMemConnLink.java:844) com.ibm.ws390.channel.xmem.XMemInboundChannel. handleRequest(XMemInboundChannel.java:340) com.ibm.ws390.xmem.XMemSRBridgeImpl. httpinvoke(XMemSRBridgeImpl.java:104) com.ibm.ws390.xmem.XMemSRCppUtilities. httpinvoke(XMemSRCppUtilities.java:74) com.ibm.ws390.orb.ServerRegionBridge.httpinvoke (ServerRegionBridge.java:215) com.ibm.ws390.orb.ORBEJSBridge.httpinvoke(ORBEJSBridge.java:281) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl. invoke(NativeMethodAccessorImpl.java:60) sun.reflect.DelegatingMethodAccessorImpl. invoke(DelegatingMethodAccessorImpl.java:37) java.lang.reflect.Method.invoke(Method.java:611) com.ibm.ws390.orb.parameters.HTTPInvoke. HTTPInvokeParmSetter(HTTPInvoke.java:101) com.ibm.ws390.orb.CommonBridge. nativeRunApplicationThread(NativeMethod) com.ibm.ws390.orb.CommonBridge. runApplicationThread(CommonBridge.java:464) com.ibm.ws.util.ThreadPool$ZOSWorker.run(ThreadPool.java:1804) com.ibm.ws390.orb.CommonBridge
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V7.0 and V8.0 * **************************************************************** * PROBLEM DESCRIPTION: Servant receives ABENDEC3 when http * * error is returned and client side * * payload is not fully uploaded. * **************************************************************** * RECOMMENDATION: * **************************************************************** Controller region skips forwarding client payload when it receive http error response. This cause servant region waiting payload and triggers ABENDEC3 error in the end.
Problem conclusion
In the fix, controller region continues forwarding payload even if servant region already set http error code. APAR PM46331 is currently targeted for inclusion in Service Level 7.0.0.21 and 8.0.0.2 of WebSphere Application Server. 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
PM46331
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-08-24
Closed date
2011-09-12
Last modified date
2012-02-03
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
R700 PSY UK74996
UP12/01/18 P 1201
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:
27 October 2021