IBM Support

IC61013: WEBSPHERE MQ VERSION 7 CLASSES FOR JMS APPLICATIONS FAIL TO HANDLE POISON MESSAGES WHEN USING CLUSTER QUEUES

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When using WebSphere MQ Version 7 classes for Java Message
    Service (JMS) applications, a poison message will be moved to
    the dead letter queue instead of the specified backout queue
    when the backout threshold is reached.
    
    This only happens when receiving messages from cluster queues.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects WebSphere MQ Version 7 classes for Java
    Message Service (JMS) applications that get messages from
    cluster queues which have a backout threshold and backout queue
    defined.
    
    Platforms affected:
    All Distributed (iSeries, all Unix and Windows) +Java
    ****************************************************************
    PROBLEM SUMMARY:
    The WebSphere MQ Version 7 classes for JMS inquire the queue
    in use to determine the backout queue (BOQ) and backout
    threshold (BOTHRESH). However, when cluster queues are being
    used, these properties are only returned if the queue was
    opened for input as well opened for inquiry.
    
    As the classes for JMS did not open the queue for input as well
    as browse when dealing with cluster queues, these properties
    were not returned, which meant that any poison messages were
    moved to the dead letter queue.
    

Problem conclusion

  • The WebSphere MQ Version 7 classes for JMS have been updated to
    open cluster queues for input as well as inquire. This allows
    the BOQ and BOTHRESH values to be retrieved from the cluster
    queue.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
                       v7.0
    Platform           Fix Pack 7.0.1.0
    --------           --------------------
    Windows            U200306
    AIX                U823774
    HP-UX (PA-RISC)    U823665
    HP-UX (Itanium)    U823667
    Solaris (SPARC)    U823772
    Solaris (x86-64)   U824344
    iSeries            tbc_p700_0_1_0
    Linux (x86)        U823664
    Linux (x86-64)     U823773
    Linux (zSeries)    U823668
    Linux (Power)      U823666
    
    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

    IC61013

  • Reported component name

    WMQ WINDOWS V7

  • Reported component ID

    5724H7220

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-05-06

  • Closed date

    2009-06-29

  • Last modified date

    2009-06-29

  • 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

    WMQ WINDOWS V7

  • Fixed component ID

    5724H7220

Applicable component levels

  • R700 PSY

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCPQ63","label":"APAR \/ Maintenance"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
29 June 2009