IBM Support

PM44593: CR HANGS WHEN CLIENT SIDE CONNECTION IS ABORTED WHEN UPLOADING LARGE PAYLOAD.

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.

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • an HTTP client initiates a file transfer upload from the client
    to the application running in the servant.
    
    When protocol_http_timeout_output_recovery is not set or if it
    is set to SERVANT, then the file transfer ultimately times out
    with the following call stack, and the servant is ABENDed with
    SEC3 reason 04130007:
    
    at com.ibm.ws390.xmem.XMemSRCppUtilities.doPushService(
        Native Method)
    at com.ibm.ws390.channel.xmem.XMemReadRequestContext.read(
        XMemReadRequestContext.java:228)
    at com.ibm.ws.http.channel.impl.HttpServiceContextImpl.
        fillABuffer(HttpServiceContextImpl.java:4139)
    at com.ibm.ws.http.channel.impl.HttpServiceContextImpl.
        readSingleBlock(HttpServiceContextImpl.java:3371)
    at com.ibm.ws.http.channel.impl.HttpServiceContextImpl.
        readBodyBuffer(HttpServiceContextImpl.java:3477)
    at com.ibm.ws.http.channel.inbound.impl.
        HttpInboundServiceContextImpl.getRequestBodyBuffer(
        HttpInboundServiceContextImpl.java:1704)
    at com.ibm.ws.webcontainer.channel.WCCByteBufferInputStream.
        bufferIsGood(WCCByteBufferInputStream.java:225)
    at com.ibm.ws.webcontainer.channel.WCCByteBufferInputStream.
        read(WCCByteBufferInputStream.java:146)
    at com.ibm.ws.webcontainer.srt.http.HttpInputStream.read(
        HttpInputStream.java:314)
    at org.apache.commons.fileupload.MultipartStream$
        ItemInputStream.makeAvailable(MultipartStream.java:977)
    at org.apache.commons.fileupload.MultipartStream$
        ItemInputStream.read(MultipartStream.java:887)
    at java.io.FilterInputStream.read(FilterInputStream.java:128)
    at org.apache.commons.fileupload.util.LimitedInputStream.read(
        LimitedInputStream.java:125)
    at java.io.FilterInputStream.read(FilterInputStream.java:102)
    at org.apache.commons.fileupload.util.Streams.copy(
        Streams.java:94)
    at org.apache.commons.fileupload.util.Streams.copy(
        Streams.java:64)
    at org.apache.commons.fileupload.FileUploadBase.parseRequest(
        FileUploadBase.java:362)
    at org.apache.commons.fileupload.servlet.ServletFileUpload.
        parseRequest(ServletFileUpload.java:126)
    
    When protocol_http_timeout_output_recovery is set to SESSION,
    the request still times out, but the session is closed and the
    servant thread does get freed up, as evidenced by these
    messages:
    WSVR0605W: Thread "WebSphere:ORB.thread.pool t=009aaa60"
    (0000006d) has been active for 704821 milliseconds and may be
    hung.  There is/are 1 thread(s) in total in the server that may
    be hung.
    at com.ibm.ws390.xmem.XMemSRCppUtilities.doPushService(
        Native Method)
    
    WSVR0606W: Thread "WebSphere:ORB.thread.pool t=009aaa60"
    (0000006d) was previously reported to be hung but has
    completed.  It was active for approximately 1246758
    milliseconds.  There is/are 0 thread(s) in total in the server
    that still may be hung.
    
    In each instance, the error is preceeded by the following FFDC
    from the controller.  We observed that this NPE error did also
    occur at other times, when a hang did not occur.
    
    [5/29/11 20:57:30:146 CEST]     FFDC
    Exception:java.lang.NullPointerException
    SourceId:com.ibm.ws.tcp.channel.ZAioTCPChannel ProbeId:300
    Reporter:com.ibm.ws.tcp.channel.impl.ZAioTCPChannel@42504250
    java.lang.NullPointerException
    at com.ibm.ws.proxy.channel.http.HttpProxyServiceContextImpl.
        localProviderPreparation
        (HttpProxyServiceContextImpl.java:4118)
    at com.ibm.ws.proxy.channel.http.HttpProxyConnectionLink.
        processResponseWork(HttpProxyConnectionLink.java:1407)
    at com.ibm.ws.proxy.channel.http.HttpProxyConnectionLink.
        transferProcessingToResponsePath
        (HttpProxyConnectionLink.java:1857)
    at com.ibm.ws.proxy.channel.http.HttpInboundReadBodyCallback.
        error(HttpInboundReadBodyCallback.java:96)
    at com.ibm.ws.http.channel.inbound.impl.HttpISCBodyReadCallback.
        error(HttpISCBodyReadCallback.java:95)
    at com.ibm.ws.tcp.channel.impl.ZAioTCPReadRequestContextImpl.
        readCompleted(ZAioTCPReadRequestContextImpl.java:748)
    at com.ibm.ws.tcp.channel.impl.ZAioTCPConnLink.
        readCompleted(ZAioTCPConnLink.java:1134)
    at com.ibm.ws.tcp.channel.impl.ZAioTCPChannel.
        readCompleted(ZAioTCPChannel.java:906)
    at com.ibm.ws.tcp.channel.impl.ZAioTCPChannelCPPUtilities.
        readCompleted(ZAioTCPChannelCPPUtilities.java:170)
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V7.0 and V8.0                        *
    ****************************************************************
    * PROBLEM DESCRIPTION: Servant is ABENDed with SEC3 reason     *
    *                      04130007 when the client side payload   *
    *                      read is timed out.                      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    An Internal controller region flag is not set correctly when
    client side timed out and it causes servant being ABENDed with
    SEC3 error.
    

Problem conclusion

  • In the fix a controller region internal flag is corrected.
    
    APAR PM44593 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

    PM44593

  • 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-07-28

  • 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

More support for: WebSphere Application Server for z/OS
General

Software version: 7.0

Reference #: PM44593

Modified date: 03 February 2012