IBM Support

IV34919: Z/OS WEBSPHERE SERVANT REGION (SR) PORT HANG DUE TO A MQRC=2009,MQRC_CONNECTION_BROKEN' RETURNED FROM WMQ.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • After a WebSphere MQ queue manager failure, the WebSphere
    Application Server Servant Region listener port failed to
    restart due to MQRC=2009, MQRC_CONNECTION_BROKEN' was
    returned from WMQ.
    
    The JMS traces show that the connection was not being
    obtained from the connection pool, but was being
    created as a new managed connection for which a new
    binding connection to the queue manager was
    attempted to be created.
    
    The trace showed that the MQCONNX was successful but the
    MQOPEN was failing in the native bindings code of WMQ.
    
    From a WMQ queue manager perspective the MQOPEN was failing
    with MQRC 2009 as the JMS code was using an 'old' context.
    

Local fix

  • The workaround would be to reduce the reconnection interval
    on the listener port to 30 seconds which will allow the
    listener port to reconnect in 60 seconds if this problem
    occurs.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users of the WebSphere MQ v7 Resource Adapter within the
    WebSphere Application Server on the zOS platform, that are
    making use of the internal processing change that was delivered
    under APAR PM41841 that has been turned on under the direction
    of IBM support.
    
    Platforms affected:
    All Distributed (iSeries, all Unix and Windows) +Java +Java zOS
    ****************************************************************
    PROBLEM SUMMARY:
    When making use of the internal processing change provided under
    APAR PM41841 a problem was found where the context remained
    present when a new connection was established to the zOS Queue
    Manager when that context is now invalid.
    

Problem conclusion

  • This APAR fixes the problem by making sure that the context
    object is not invalid when a new connection is made to the zOS
    queue manager after a failure in the zOS queue manager.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
                       v7.0
    Platform           Fix Pack 7.0.1.11
    --------           --------------------
    Windows            7.0.1.11
    AIX                7.0.1.11
    HP-UX (PA-RISC)    7.0.1.11
    HP-UX (Itanium)    7.0.1.11
    Solaris (SPARC)    7.0.1.11
    Solaris (x86-64)   7.0.1.11
    iSeries            7.0.1.11
    Linux (x86)        7.0.1.11
    Linux (x86-64)     7.0.1.11
    Linux (zSeries)    7.0.1.11
    Linux (Power)      7.0.1.11
    zOS                7.0.1.11
    
                       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

    IV34919

  • Reported component name

    WMQ AIX V7

  • Reported component ID

    5724H7221

  • Reported release

    701

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-01-16

  • Closed date

    2013-01-25

  • Last modified date

    2014-01-21

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    PM82225 PI10035

Fix information

  • Fixed component name

    WMQ AIX V7

  • Fixed component ID

    5724H7221

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:
21 January 2014