IBM Support

PM35193: PEV RECOVERY CAUSES THREAD AND MQ CONNECTION LEAK

Fixes are available

7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
Obtain the fix for this APAR.

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • A connection leak is observed during recovery which may
    eventually result in MQ reason code 2025
    (MQRC_MAX_CONNS_LIMIT_REACHED).
    
    SYMPTOMS:
    A dump can show:
    * Many of these types of threads can be seen running:
    com/ibm/ws/sib/remote/mq/impl/TransactionalWorker.getNextWorkIte
    m
    * these threads are created to allow all work to execute under
    one
    transactional connection to a QManager on the same thread
    * the adjunct java heap has a lot (>6K) objects of type:
    com/ibm/ws/sib/remote/mq/exceptions/RMQCursorException
    --
    with detailed message as:
    --
    CWSJP0023E: A Websphere MQ error was encountered when using the
    Websphere MQ queue Q1
    on the Websphere MQ queue manager Name :QMGR, Host :hostname,
    Port
    :0000,
    Channel :CHANNEL, Bus :BUS, BM Name
    :###,
    BM Uuid :###, Virtual QM Name :BUS,
    Auth alias :###, Transport :OutboundBasicWMQClient: null
    --
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of MQ servers for IBM WebSphere   *
    *                  Application Server V7.0 connecting to an    *
    *                  MQ queue manager in BINDINGS mode.          *
    ****************************************************************
    * PROBLEM DESCRIPTION: MQRC_MAX_CONNS_LIMIT_REACHED is         *
    *                      observed during transaction recovery    *
    *                      processing for an MQ servers resource.  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    During recovery processing of transactional resources
    associated with MQ servers, connections may not properly be
    cleaned up once recovery processing has completed.
    

Problem conclusion

  • The code has been altered to ensure that the connection opened
    for transaction recovery is always properly closed when
    transaction recovery has completed for that resource.
    
    APAR PM35193 is currently targeted for inclusion in Service
    Level (Fix Pack) 7.0.0.19 of WebSphere Application Server V7.0.
    
    Please refer to URL:
    //www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
    for Fix Pack availability.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM35193

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-03-18

  • Closed date

    2011-05-24

  • Last modified date

    2011-10-04

  • 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

    WEBSPHERE FOR Z

  • Fixed component ID

    5655I3500

Applicable component levels

  • R700 PSY UK71280

       UP11/09/10 P F109

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.



Document information

More support for: WebSphere Application Server for z/OS
General

Software version: 7.0

Reference #: PM35193

Modified date: 04 October 2011