IBM Support

IT31440: KAFKA CONSUMER RECEIVING MESSAGES FROM THE WRONG TOPIC

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 two message flows containing Kafka Consumer subscribing to
    two different topics under two different applications are
    deployed on same Integrations Server, messages from wrong topic
    get delivered if the name of the two flows is identical.
    

Local fix

  • Rename the flows to have unique names.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    <span style="background-color:rgb(255, 255, 255)">All users of
    IBM App Connect Enterprise V11.0 using  KAFKA nodes.</span>
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    If two, or more, applications are deployed to the same
    integration server and both applications contain a message flow
    with the same name and the message flows both contain a Kafka
    node (Consumer, Read or Producer) with the same name then the
    Kafka nodes will incorrectly share a single connector to connect
    to the Kafka server.
    
    This will mean that the second Kafka message flow node to
    initialise will use the same properties as the first Kafka
    message flow node.
    
    This may result in the second message flow sending or receiving
    messages from the same topic as the first message flow even when
    it specified a different topic
    

Problem conclusion

  • The algorithm which is used to identify when a connector may be
    shared has been updated to ensure 'non-shared' connectors, such
    as Kafka, are not shared with any other message flow node.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v11.0      11.0.0.8
    
    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

    IT31440

  • 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-01-08

  • Closed date

    2020-04-24

  • Last modified date

    2020-04-24

  • 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

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

Document Information

Modified date:
25 April 2020