IBM Support

IT08293: HTTPASYNCREQUESTNODE SERIALIZES HEADER PARSERS

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • When making a request to a remote web service using the
    HTTPAsyncRequest node the last child of the InputRoot tree is
    serialized as a bitstream to make up the body of the request.
    
    If the Input message tree does not have a body, for example if
    the message originated from a HTTPInput node using the GET HTTP
    method this results in the input HTTP header being serialised
    and used as the body of the HTTP request.
    
    This can lead to malformed HTTP messages and the remote server
    issuing a HTTP 400 "Bad Response" message.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM Integration Bus version 9 or above using the
    HTTPAsyncRequest Node.
    
    
    Platforms affected:
    MultiPlatform, z/OS
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When making a request to a remote web service using the
    HTTPAsyncRequest node the last child of the InputRoot tree is
    serialized as a bitstream to make up the body of the request.
    
    If the Input message tree does not have a body, for example if
    the message originated from a HTTPInput node using the GET HTTP
    method, this results in the input HTTP header being serialized
    and used as the body of the HTTP request.
    
    This can lead to malformed HTTP messages and the remote server
    issuing a HTTP 400 "Bad Response" message.
    
    
    There are a number of resource name changes between WebSphere
    Message Broker and IBM Integration Bus Version 9.0. For details
    visit
    http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.e
    tools.mft.doc/bb23814_.htm
    

Problem conclusion

  • The HTTPAsyncRequest node now only serializes the last child of
    the InputRoot message tree if that child is owned by a body
    parser.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.0       9.0.0.6
    v10.0      10.0.0.2
    
    The latest available maintenance can be obtained from:
    http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041
    
    If the maintenance level is not yet available,information on
    its planned availability can be found on:
    http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT08293

  • Reported component name

    INTEGRATION BUS

  • Reported component ID

    5724J0530

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-04-14

  • Closed date

    2015-09-11

  • Last modified date

    2016-03-16

  • 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

    INTEGRATION BUS

  • Fixed component ID

    5724J0530

Applicable component levels

  • R900 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSNQK6","label":"IBM Integration Bus"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
23 March 2020