IBM Support

IT32418: DEFAULT NAMESPACE IN SOAP BODY CAUSE BIP5014E ERROR DURING SERIALIZATION.

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

  • If you process a soap message having default namespace
    attribute in soap body, then you are likely to hit following
    error when serializing the message tree to bitstream ( ie .when
    emitting monitoring event, writing to an output queue, etc.)
    
    
    BIP5014E: Element must have a namespace specified if there is a
    default namespace in scope. Whilst writing the XMLNS message,
    element 'Body' was found to be in scope of a default namespace,
    but this element does not have a namespace defined.
    
    Here is
    an example of SOAP message, with default namespace attribute in
    soap body, that can cause the error.
    
     <s:Envelope
    xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"> <s:Body
    xmlns="http://foo.bar/test"> <test> 1 </test>
    </s:Body></s:Envelope>
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    <span style="background-color:rgb(255, 255, 255)">All users of
    IBM App Connect Enterprise v11 and IBM Integration Bus V10 with
    SOAPInput node.</span>
    
    
    Platforms affected:
    z/OS, MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    If you process a soap message that has a default namespace
    attribute in the soap body, then you are likely to hit the
    following error when serializing the message tree to bitstream
    (i.e., when emitting monitoring event, writing to an output
    queue, etc.)
    
    BIP5014E: Element must have a namespace specified if there is a
    default namespace in scope. Whilst writing the XMLNS message,
    element 'Body' was found to be in scope of a default namespace,
    but this element does not have a namespace defined.
    
    Here is an example of a SOAP message, with default namespace
    attribute in the soap body, that can cause the error.
    
    <s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
    <s:Body xmlns="http://foo.bar/test"> <test> 1 </test>
    </s:Body></s:Envelope>
    

Problem conclusion

  • The product no longer fails to serialize a SOAP message that has
    a default namespace in the soap header or Body.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v10.0      10.0.0.22
    v11.0      11.0.0.10
    
    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

    IT32418

  • Reported component name

    INTEGRATION BUS

  • Reported component ID

    5724J0540

  • Reported release

    A00

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-04-02

  • Closed date

    2020-08-25

  • Last modified date

    2020-08-25

  • 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

    5724J0540

Applicable component levels

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

Document Information

Modified date:
26 August 2020