IBM Support

PI81572: PARSING ERRORS WHEN THE CONNECTION IS REUSED AND THERE IS UNREAD DATA ON THE WIRE AFTER THE RESPONSE IS READ

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If there is data left on the wire when the connection is
    reused, parsing errors such as a MalformedMessageException can
    occur after sending out the next request because the channel
    finally reads the leftover data while it's expecting to read
    the next response.
    

Local fix

  • Avoid reusing the connection.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  IBM WebSphere Application Server Version    *
    *                  8.0, 8.5.5 and 9.0 Traditional Profile      *
    *                  users of outbound connection                *
    ****************************************************************
    * PROBLEM DESCRIPTION: The HTTP Channel can encounter an       *
    *                      exception while reading for the         *
    *                      response data of an outbound request    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    While reading for the response on an outbound connection the
    HTTP Channel can encounter an exception similar to this:
    [5/3/17 9:51:07:500 CDT] 0000005e HttpOutboundS 3   Exception
    while
    parsing response:
    com.ibm.wsspi.genericbnf.exception.MalformedMessageException:
    Invalid
    CR found in token
    This occurs when the connection has been reused and the
    previous response data was not read. This left over data is
    then read on the next response, where the HTTP Channel was
    expecting the first line of a request, and instead of
    processing the expected response it throws the above exception.
    

Problem conclusion

  • The HTTP Channel was modified to read for and throw out the
    response data if not all of the data was read
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 8.0.0.15, 8.5.5.13, 9.0.0.6, 17.0.0.3.  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

    PI81572

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-05-12

  • Closed date

    2017-09-18

  • Last modified date

    2017-09-18

  • 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

  • R800 PSY

       UP

  • R850 PSY

       UP

  • R900 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
18 October 2021