IBM Support

IT32487: FAILURE TO EMIT TRANSACTION START MONITORING EVENT WHEN INPUT MESSAGE CAUSE PARSING ERROR.

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 the input message to the flow is invalid and can cause a
    parsing error, its seen that transaction start events are not
    getting emitted. This is seen particularly when the correlation
    tab of monitoring event is configured with an xpath that refers
    to the message tree.
    
    For eg: If an invalid soap message, that doesn't conform to
    WSDL, is used to invoke a SOAP message flow that has transaction
    start event configured and if the event configuration has a
    global correlator xpath, then a transaction monitoring event
    will not be seen; the user will only find the parsing errors
    like BIP2230E, BIP3614E and BIP5009E being responded back to the
    client.
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All  users of IBM Integration Bus V10 and App Connect Enterprise
    V11 using monitoring events
    
    
    Platforms affected:
    z/OS, MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    <span style="background-color:rgb(255, 255, 255)">When the input
    message to the flow is invalid and causes a </span><span
    style="background-color:rgb(255, 255, 255)">parsing error,  the
    transaction start events are not  getting emitted. This is seen
    particularly when the correlation </span><span
    style="background-color:rgb(255, 255, 255)">tab of monitoring
    event is configured with an xpath that refers </span><span
    style="background-color:rgb(255, 255, 255)">to the message tree.
          </span>
    

Problem conclusion

  • The product is now modified so that it will emit the transaction
    start events even when  parser exceptions occur.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v10.0      10.0.0.23
    v11.0      11.0.0.12
    
    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

    IT32487

  • 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-21

  • Closed date

    2021-01-28

  • Last modified date

    2021-01-28

  • 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

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

Document Information

Modified date:
29 January 2021