IBM Support

IV50451: WMQ V701 MDBS REGISTERED AGAINST A SHARED QUEUE STOP RECEIVING MESSAGES AND APPEAR HUNG AFTER COUPLING FACILITY FAILURE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • WMQ V701 MDBs which have been registered against a shared queue
    fail to get messages and appear hung after the coupling facility
    associated with the queue sharing group becomes unavailable.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of the WebSphere MQ Classes for JMS
    who are attempting to get messages from a Shared Queue.
    
    This includes users of:
    
    - 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.0 and V8.0 WebSphere MQ
    messaging provider.
    - The WebSphere Application Server V6.1 WebSphere MQ messaging
    provider who have configured the WebSphere variable
    MQ_INSTALL_ROOT to point to a WebSphere MQ V7.0.1, V7.1, V7.5
    installation.
    
    Platforms affected:
    All Distributed (iSeries, all Unix and Windows) +Java +Java zOS
    ****************************************************************
    PROBLEM SUMMARY:
    A shared queue is a type of local queue whose messages can be
    accessed by one or more queue managers that are in a
    queue-sharing group (QSG). Queue Managers in the QSG communicate
    with each other by means of a coupling facility (CF) that stores
    the shared queues.
    
    When a Message-Driven Bean (MDB) was registered against a shared
    queue and the coupling facility hosting the shared queue failed,
    the MDB application was not notified of the failure. It remained
    running and no error messages were written to the Java trace or
    application server logs. The MDB application was also unable to
    process any additional messages and appeared to be in a hung
    state.
    

Problem conclusion

  • The WebSphere MQ Classes for JMS have been modified to notify
    any listeners registered against a shared queue that the
    coupling facility has failed. An MQRC_CF_STRUC_FAILED error is
    returned to the application and in the case of MDBs the MDB
    application will enter a stopped state. The MQRC_CF_STRUC_FAILED
    error and associated java stack will be written to the Java
    trace and application server log.
    
    After the coupling facility has been recovered, MDB applications
    that make use of an activation specification will need to be
    restarted manually in order to restore message processing.
    
    MDB applications deployed in WebSphere Application Server that
    have been configured to use a listener port can recover
    automatically if the following conditions are met:
    1) The coupling facility has been successfully recovered.
    2) The maximum number of retry attempts (MAX.RECOVERY.RETRIES)
    configured on the message listener service have not yet been
    exceeded.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v7.1       7.1.0.5
    v7.5       7.5.0.4
    v7.0       7.0.1.12
    
    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

    IV50451

  • Reported component name

    WMQ LIN X86 V7

  • Reported component ID

    5724H7224

  • Reported release

    701

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-10-07

  • Closed date

    2013-11-29

  • Last modified date

    2013-11-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 LIN X86 V7

  • Fixed component ID

    5724H7224

Applicable component levels

  • R701 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSFKSJ","label":"WebSphere MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 April 2022