IBM Support

IT36612: SOAPASYNCRESPONSE NODE SHOULD CREATE HTTPINPUTHEADER WHEN NOT USING 'HTTP ASYNCHRONOUS REQUEST-RESPONSE' PROPERTY

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

  • In ACE V11, when SOAPAsyncRequest and SOAPAsyncResponse nodes
    are used in the default mode, which is to use WS-Addressing to
    call the paired SOAPAsyncResponse node, an HTTPInputHeader is
    expected from SOAPAsyncResponde node. However, the
    SOAPAsyncResponse node propagates out a HTTPResponseHeader.
    This can cause a failure when the node is connected to a
    Collector node and may result in BIP3159S and BIP6105E errors.
    
    
    In its default mode, the backend makes a webservice call to
    the SOAPASyncResponse node's endpoint. Accordingly a
    HTTPInputHeader is expected. However, if using 'HTTP
    asynchronous request-response' property, the HTTP Request
    socket is used to receive the response and hence
    HTTPResponseHeader is expected.
    
    The HTTPInputHeader needs
    'X-Original-HTTP-Command' property. Similarly, the
    HTTPResponseHeader needs 'X-Original-HTTP-Status-Line'. If
    those fields are missing it can cause failures when the tree is
    reconstructed from a serialized bitstream, which is the reason
    it throws errors when used with the Collector node.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All Users of IBM App Connect Enterprise V11.0 with
    SoapAsynRequest and SoapAsyncResponse nodes.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    In App Connect Enterprise V11, when SOAPAsyncRequest and
    SOAPAsyncResponse nodes are used in the default mode, which is
    to use WS-Addressing to call the paired SOAPAsyncResponse node,
    an HTTPInputHeader is expected from SOAPAsyncResponde node.
    However, the SOAPAsyncResponse node propagates out an
    HTTPResponseHeader. This can cause a failure when the node is
    connected to a Collector node and may result in BIP3159S and
    BIP6105E errors.
    
    In its default mode, the backend makes a webservice call to the
    SOAPAsyncResponse node's endpoint. Accordingly, an
    HTTPInputHeader is expected. However, if using 'HTTP
    asynchronous request-response' property, the HTTP Request socket
    is used to receive the response and hence HTTPResponseHeader is
    expected. But in both cases, HTTPResponseHeader is seen
    propagated out from SOAPAsyncResponse node.
    
    The HTTPInputHeader needs 'X-Original-HTTP-Command' property.
    Similarly, the HTTPResponseHeader needs
    'X-Original-HTTP-Status-Line'. If those fields are missing it
    can cause failures when the tree is reconstructed from a
    serialized bitstream, which is the reason it throws errors when
    used with the Collector node.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    IT36612

  • Reported component name

    APP CONNECT ENT

  • Reported component ID

    5724J0550

  • Reported release

    B00

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-04-19

  • Closed date

    2021-06-04

  • Last modified date

    2021-09-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

    APP CONNECT ENT

  • Fixed component ID

    5724J0550

Applicable component levels

[{"Line of Business":{"code":"LOB36","label":"IBM Automation"},"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSDR5J","label":"IBM App Connect Enterprise"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"B00"}]

Document Information

Modified date:
17 September 2021