IBM Support

IT37594: PUBLICATION OF MESSAGES TO KAFKA WHEN ACKS=0 IS TOO SLOW

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 messages are published to Kafka with the 'Acks' property on
    the Kafka producer node set to the value of zero the throughput
    of the producer node is slower than anticipated. When the
    Acks property is set to zero it is expected that the Kafka
    Producer node is providing the lowest quality of service however
    the producer node is waiting for the send operation to complete
    before allowing the message flow to continue. This fix allows
    the send operation to complete asynchronously and allow message
    flow operation to continue.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM App Connect Enterprise 11.0, 12.0, and IBM
    Integration Bus V10.0 using Kafka Publication nodes with an Acks
    value of 0 (zero).
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    The throughput of the Kafka Producer node in a message flow with
    an Acks value of 0 (zero) is slower than what can be achieved
    using a standalone application written in Java.
    

Problem conclusion

  • Sending messages to Kafka using the Kafka Producer node with an
    Acks value of 0 (zero) is intended to be provide the maximum
    message throughput in exchange for sending messages at the
    lowest quality of service. However when the Kafka Producer node
    is configured in this way it was still performing a lookup in
    order to populate the local environment with the partition
    number and checksum values for each message sent. This
    additional lookup was responsible for the disparity in
    performance.
    As a result of this APAR, the partition number and checksum
    fields will not be written to the WrittenDestination in the
    Local Environment following a Kafka Producer node which is
    configured with an Acks value of 0 (zero).
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v10.0      10.0.0.25
    v11.0      11.0.0.15
    v12.0      12.0.2.0
    
    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

    IT37594

  • 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

    2021-07-13

  • Closed date

    2021-10-08

  • Last modified date

    2021-10-08

  • 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":"LOB45","label":"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:
13 October 2021