IBM Support

IC61714: ASYNCDELIVERY THREAD HANGS/WAITS WHEN CONNECTION BROKEN EXCEPTION IS REPORTED ON THE EXCEPTION LISTENER

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When an application using the WebSphere MQ V7 classes for Java
    Message Service (JMS) gets messages from a queue using
    MessageListeners, application threads appear to hang and fail
    to be closed off if the connection to the queue manager is
    broken. When the connection broken exception occurs, the
    MessageListener threads go in a infinite loop and do not get
    terminated.
    
    A trace of the failure shows that the AsyncDelivery threads go
    into an infinite loop, similar to the one shown below:
    
    c.i.m.c.w.v.jms.internal.SessionAsyncHelper - X run()
    [java.util.NoSuchElementException] at:
    java.util.Vector.firstElement(Unknown Source)
    com.ibm.msg.client.wmq.v6.jms.internal.SessionAsyncHelper.run
    (Unknown Source)
    java.lang.Thread.run(Unknown Source)
    Object ClassLoader = null
    CurrentThread ClassLoader =
    org.eclipse.core.runtime.internal.adaptor.ContextFinder@5a635a63
    c.i.m.c.w.v.jms.internal.MQSession - d isStarted() getter [true]
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects applications using the WebSphere MQ V7
    classes for JMS that use MessageListeners to get messages from
    a queue manager.
    
    Platforms affected:
    All Distributed (iSeries, all Unix and Windows) +Java
    ****************************************************************
    PROBLEM SUMMARY:
    When applications are getting messages from JMS Destinations
    using MessageListeners, if there is a connection error between
    the application and the queue manager, the ExceptionListener
    for the JMS connection gets notified of the exception. When
    this happens, it is important that all of the AsyncDelivery
    threads used by the MessageListener for this connection must
    also be terminated.
    
    However, when the ExceptionListener was triggered, the
    MessageListener threads went in a infinite loop and did not get
    terminated.
    

Problem conclusion

  • When a connection broken event occurs, the connection failure
    is passed to the ExceptionListener. Once the exception is
    delivered to the onException method, all the AsyncDelivery
    threads registered with the connection are now terminated
    correctly.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
                       v7.0
    Platform           Fix Pack 7.0.1.1
    --------           --------------------
    Windows            U200310
    AIX                U827232
    HP-UX (PA-RISC)    U826485
    HP-UX (Itanium)    U826884
    Solaris (SPARC)    U827125
    Solaris (x86-64)   U827374
    iSeries            tbc_p700_0_1_1
    Linux (x86)        U826321
    Linux (x86-64)     U827231
    Linux (zSeries)    U827105
    Linux (Power)      U826779
    
    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

    IC61714

  • 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-06-25

  • Closed date

    2009-08-26

  • Last modified date

    2009-08-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 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:
26 August 2009