IBM Support

IT34710: CERTAIN NODES IN THE FLOW FAILS TO EMIT EVENTS EVEN WHEN THE MONITORING PROFILE IS VALID

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 migrated from V10 to V11, certain nodes in the flow using
    monitoring profile, fails to emit events even when the
    monitoring profile is valid.
    
    For example, A message flow
    containing MQReply node successfully emits events in V10 with a
    monitoring profile containing eventSourceAddress
    "MQReply.terminal.out"; but the same flow does not produce
    monitoring event once migrated to ACE V11.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of App Connect Enterprise V11 using monitoring events.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When migrated from prior versions to App Connect Enterprise V11,
    certain nodes in the flow using monitoring profile, fails to
    emit events even when the monitoring profile is valid.
    
    For example, A message flow containing MQReply node successfully
    emits events in V10 with a monitoring profile containing
    eventSourceAddress "MQReply.terminal.out"; but the same flow
    does not produce monitoring event once migrated to V11.
    
    Redeploying the flow in V11 is a way to get around this problem.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    IT34710

  • 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

    2020-10-28

  • Closed date

    2020-12-15

  • Last modified date

    2020-12-15

  • 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 & Data Platform"},"Product":{"code":"SSDR5J","label":"IBM App Connect Enterprise"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"B00"}]

Document Information

Modified date:
16 December 2020