IBM Support

PK32441: EOFEXCEPTION SENDING DATA IN GZIP FORMAT VIA A JAVA STREAM TO A SERVLET

Fixes are available

6.1.0.7: WebSphere Application Server V6.1 Fix Pack 7 for Solaris
6.1.0.7: WebSphere Application Server V6.1 Fix Pack 7 for HP-UX
6.1.0.7: WebSphere Application Server V6.1 Fix Pack 7 for Linux
6.1.0.5: WebSphere Application Server V6.1.0 Fix Pack 5 for Linux
6.1.0.7: WebSphere Application Server V6.1 Fix Pack 7 for Windows
6.1.0.7 WebSphere Application Server V6.1 Fix Pack 7 for AIX
6.1.0.5: WebSphere Application Server V6.1.0 Fix Pack 5 for AIX
6.1.0.5: WebSphere Application Server V6.1.0 Fix Pack 5 for i5/OS
6.1.0.7: WebSphere Application Server V6.1 Fix Pack 7 for i5/OS
6.1.0.5: WebSphere Application Server V6.1.0 Fix Pack 5 for HP-UX
6.1.0.5: WebSphere Application Server V6.1.0 Fix Pack 5 for Windows
Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR10 Cumulative Fix for WebSphere Application Server
6.1.0.31: Java SDK 1.5 SR11 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
6.1.0.29: Java SDK 1.5 SR11 Cumulative Fix for WebSphere Application Server
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
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: WebSphere Application Server V6.1 Fix Pack 47
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
6.1.0.5: WebSphere Application Server V6.1.0 Fix Pack 5 for Solaris
6.1.0.9: WebSphere Application Server V6.1 Fix Pack 9 for Solaris

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Issue sending data in GZIP format via a Java Stream to a
    servlet deployed in WebSphere. In WebSphere Application Server
    v6.0.2 instance a read of the input stream triggers an
    EOFException. This functionality works in WebSphere Application
    Server v5.1, but does not work in 6.0 or 6.1.
    
    SystemOut.log shows the following error:
    ---------------------------------------
    [9/28/06 9:35:13:847 PDT] 00000019 WCCByteBuffer E Failed to get
    next body buffer
    
    Note: EOFException may or may not be logged.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: WebSphere Application Server version 6       *
    *                 users of the HTTP channel using both         *
    *                 compression and chunked encoding.            *
    ****************************************************************
    * PROBLEM DESCRIPTION: The HTTP channel is receiving a body    *
    *                      decompression error on the second chunk *
    *                      read off the network.                   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The proper HTTP handling of both body compression and chunked
    encoding is that Content-Encoding (compression) is applied to
    the entire body and then Transfer-Encoding is applied as it is
    sent. This means the server side that receives that body must
    read the entire chunked body first, then decompress. The HTTP
    channel was attempting to decompress each individual chunk,
    thus it received the decompression error on the second chunk.
    

Problem conclusion

  • The HTTP channel has been updated to apply the encodings in the
    proper order when reading in such a body, as well as now
    applying the encodings correctly with outgoing messages.
    
    The fix for this APAR is currently targeted for inclusion
    in fixpacks 6.0.2.17 and 6.1.0.5.
    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

    PK32441

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    60W

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2006-10-04

  • Closed date

    2006-10-18

  • Last modified date

    2006-10-18

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Modules/Macros

  • HTTPCHAN
    

Fix information

  • Fixed component name

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

  • R60A PSY

       UP

  • R60H PSY

       UP

  • R60I PSY

       UP

  • R60P PSY

       UP

  • R60S PSY

       UP

  • R60W PSY

       UP

  • R60Z PSY

       UP

  • R61A PSY

       UP

  • R61H PSY

       UP

  • R61I PSY

       UP

  • R61P PSY

       UP

  • R61S PSY

       UP

  • R61W PSY

       UP

  • R61Z PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 December 2021