IBM Support

SE55330: WMQ V7.0.1 JMS CLIENT APPLICATION GENERATES ERROR: MQRC_SYNCPOINT_NOT_AVAILABLE IF BROWSING A POISON MESSAGE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A JMS Client application that uses a JMS QueueBrowser to browse
    messages whilst taking part in a global XA Transaction throws an
    MQRC_SYNCPOINT_NOT_AVAILABLE error if a Poison
    message is browsed.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of the following environments, who are
    making use of a
    QueueBrowser whilst taking part in a XA transaction:
    
    - The WebSphere MQ V7.0.1, V7.1, V7.5 classes for JMS.
    
    - The WebSphere MQ V7.0.1, V7.1, V7.5 Resource Adapter.
    
    - The WebSphere Application Server V7 and V8 WebSphere MQ
    messaging provider.
    
    Platforms affected:
    All Distributed (iSeries, all Unix and Windows) +Java +Java zOS
    ****************************************************************
    PROBLEM SUMMARY:
    When a JMS QueueBrowser is being used to browse messages and a
    poison message is found, the WebSphere MQ Classes for JMS
    attempt
    to requeue the message to the backout queue. The MQGET call
    issued as part of the requeue is performed under syncpoint.
    
    This is not a valid operation if the WebSphere MQ Classes for
    JMS
    are participating in a XA transaction that has not yet been
    started by the transaction manager (inactive), and so this
    operation resulted in the
    MQRC_SYNCPOINT_NOT_AVAILABLE message being returned.
    

Problem conclusion

  • The QueueBrowser implementation has been modified such that
    poison messages are only requeued to the
    backout queue if the XA transaction that the WebSphere MQ
    Classes for JMS are participating in is active; that is, if
    transactional work has already been carried out on the session
    in use before the browse is performed.
    
    If the XA transaction is inactive, any poison messages will not
    be seen in the QueueBrowser returned Enumeration, and the
    messages will remain on the queue.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following:
    
                       v7.0
    Platform           Fix Pack 7.0.1.12
    --------           --------------------
    Windows            7.0.1.12
    AIX                7.0.1.12
    HP-UX (PA-RISC)    7.0.1.12
    HP-UX (Itanium)    7.0.1.12
    Solaris (SPARC)    7.0.1.12
    Solaris (x86-64)   7.0.1.12
    iSeries            7.0.1.12
    Linux (x86)        7.0.1.12
    Linux (x86-64)     7.0.1.12
    Linux (zSeries)    7.0.1.12
    Linux (Power)      7.0.1.12
    zOS                7.0.1.12
    
                       v7.1
    Platform           Fix Pack 7.1.0.4
    --------           --------------------
    Windows            7.1.0.4
    AIX                7.1.0.4
    HP-UX (Itanium)    7.1.0.4
    Solaris (SPARC)    7.1.0.4
    Solaris (x86-64)   7.1.0.4
    iSeries            7.1.0.4
    Linux (x86)        7.1.0.4
    Linux (x86-64)     7.1.0.4
    Linux (zSeries)    7.1.0.4
    Linux (Power)      7.1.0.4
    zOS                7.1.0.4
    
    Version            v7.5
    --------           --------------------
    Fix available in:  7.5.0.3
    
    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

    SE55330

  • Reported component name

    WMQ ISERIES V7

  • Reported component ID

    5724H7226

  • Reported release

    701

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2013-03-28

  • Closed date

    2013-06-26

  • Last modified date

    2013-06-26

  • 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 ISERIES V7

  • Fixed component ID

    5724H7226

Applicable component levels

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

Document Information

Modified date:
27 April 2020