IBM Support

IC88664: WEBSPHERE MQ V7.0.1: WHEN A WMQ CHANNEL FAILURE OCCURS THE WEBSPHERE APPLICATION SERVER LISTENER PORT FAILS TO RECONNECT

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When a WebSphere MQ channel failure occurs that was being used
    for a WebSphere Application Server listener port, then the
    listener port fails to reconnect once the channel has been
    restarted. Messages remain on the queue and the Message Driven
    Bean configured against the listener port is not driven.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of the WebSphere Application
    Server V7, V8 and V8.5 WebSphere MQ messaging provider who are
    using an Message-Driven Beans(MDB) configured against a Listener
    Port or Activation Specification, using the CLIENT transport
    type.
    
    Platforms affected:
    All Distributed (iSeries, all Unix and Windows) +Java +Java zOS
    ****************************************************************
    PROBLEM SUMMARY:
    A WMQ channel outage caused the connection between the WMQ JMS
    client running in the WebSphere Application Server to be
    disconnected. The WebSphere MQ classes for JMS client then
    failed to inform the exception handler registered by the
    WebSphere Application Server recovery function for Listener
    Ports, due to the timing of the exception that occurred. As the
    WebSphere Application Server was not aware of the connection
    disconnect it did not attempt to recovery the connection as
    defined in the Listener Port configuration.
    
    This then caused messages to be left on the WMQ Queue even when
    the WMQ channel was re-established.
    

Problem conclusion

  • This APAR solves the issue by making sure that any exception
    handlers configured against the WMQ consumer are informed of an
    exception on the connection. This APAR effects both Listener
    Ports and WMQ Activation Specifications as both rely on the
    exception handlers registered to commence MDB recovery
    reconnection.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
                       v7.0
    Platform           Fix Pack 7.0.1.10
    --------           --------------------
    Windows            U200352
    AIX                U853055
    HP-UX (PA-RISC)    U853082
    HP-UX (Itanium)    U853087
    Solaris (SPARC)    U853083
    Solaris (x86-64)   U853089
    iSeries            7.0.1.10
    Linux (x86)        U853084
    Linux (x86-64)     U853088
    Linux (zSeries)    U853085
    Linux (Power)      U853086
    zOS                7.0.1.10
    
                       v7.1
    Platform           Fix Pack 7.1.0.3
    --------           --------------------
    Windows            7.1.0.3
    AIX                7.1.0.3
    HP-UX (Itanium)    7.1.0.3
    Solaris (SPARC)    7.1.0.3
    Solaris (x86-64)   7.1.0.3
    iSeries            7.1.0.3
    Linux (x86)        7.1.0.3
    Linux (x86-64)     7.1.0.3
    Linux (zSeries)    7.1.0.3
    Linux (Power)      7.1.0.3
    zOS                7.1.0.3
    
    Platform           v7.5
    --------           --------------------
    Multiplatforms     7.5.0.1
    
    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

    IC88664

  • Reported component name

    WMQ WINDOWS V7

  • Reported component ID

    5724H7220

  • Reported release

    701

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-11-28

  • Closed date

    2012-12-13

  • Last modified date

    2012-12-13

  • 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

  • R701 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.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
13 December 2012