IBM Support

IT12956: EXCEPTION ON RESPONSE TO ONE WAY MEP IN SOAP REQUEST NODE.

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 using a one way Message Exchange Pattern (MEP) a SOAP
    provider should not send a response to a request.
    
    However in acknowledgement that there are a large number of
    non-compliant SOAP providers in use the WS-I 1.1 specification
    states that an empty SOAP envelope in a response to a one way
    MEP request should be ignored.
    
    Instead IIB throws the following exception:
    
    BIP3708: A SOAP request received a response message body when
    one was not expected because a one-way Messsage Exchange
    Pattern (MEP) was being used.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM Integration Bus v10 and IBM App Connect
    Enterprise v11 who use the SOAPRequest node and interact with
    SOAP Services that may return non-empty replies to one-way MEP
    operations.	
    
    
    Platforms affected:
    MultiPlatform, z/OS
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When using a one way Message Exchange Pattern (MEP) a SOAP
    provider should not send a response to a request. However, in
    acknowledgement that there are a large number of non-compliant
    SOAP providers in use, the WS-I 1.1 specification states that an
    empty SOAP envelope in a response to a one way MEP request
    should be ignored. The product does not correctly follow the
    WS-I 1.1 specification when dealing with such requests and a
    BIP3708 exception will be thrown:
    
    BIP3708: A SOAP request received a response message body when
    one was not expected because a one-way Messsage Exchange Pattern
    (MEP) was being used.
    

Problem conclusion

  • If a reply is received by a SOAPRequest node for a one way MEP
    operation the product will now, by default, check for the
    presence of the soap:Body element and will allow the reply to be
    accepted if this element is empty. If the soap:Body element is
    empty, absent, or the reply is not a valid XML message, then the
    received reply is discarded and processing continues as if no
    reply was received. If the element is found and is non-empty
    then the BIP3708 exception is thrown.
    
    This APAR can be reverted by setting the environment variable
    MQSI_SOAP_STRICT_ONE_WAY_MEP.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v10.0      10.0.0.15
    v11.0      11.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

    IT12956

  • Reported component name

    WEB MESSAGE BRO

  • Reported component ID

    5724J0520

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-01-13

  • Closed date

    2019-02-08

  • Last modified date

    2019-10-17

  • 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

    WEB MESSAGE BRO

  • Fixed component ID

    5724J0520

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSKM8N","label":"WebSphere Message Broker"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
17 October 2019