IBM Support

IT28907: JMS 2.0 DeliveryDelay performance issue

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 put with a DeliveryDelay, using the IBM MQ JMS
    2.0 client, the queue manager's delivery delay processor task
    performs more slowly than expected if messages are not made
    available to it until after their configured delay interval has
    been reached.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This affects users of the JMS 2.0 DeliveryDelay feature
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    A logic error in the queue manager task which performs the
    processing of messages with a delivery delay meant that messages
    were not correctly processed in batches when they became
    eligible.
    
    In the worst case scenario, it was possible for the task to
    enter a state whereby each messages was put and committed
    individually when its delay interval expired instead of the puts
    being batched as expected, resulting in a visible backlog of
    messages on the delivery delay queue.
    

Problem conclusion

  • The delivery delay processor task that runs as part of the MQ
    queue manager when delivery delay is being used has been
    corrected to apply the intended batching logic.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v8.0       8.0.0.15
    v9.0 LTS   9.0.0.10
    v9.1 CD    TBC.
    v9.1 LTS   9.1.0.5
    
    The latest available maintenance can be obtained from
    'WebSphere MQ Recommended Fixes'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037
    
    If the maintenance level is not yet available information on
    its planned availability can be found in 'WebSphere MQ
    Planned Maintenance Release Dates'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT28907

  • Reported component name

    IBM MQ BASE MP

  • Reported component ID

    5724H7251

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-04-24

  • Closed date

    2020-02-28

  • Last modified date

    2020-02-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

    IBM MQ BASE MP

  • Fixed component ID

    5724H7251

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0.0.0","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
28 February 2020