IBM Support

IC65023: Thread handle leak in amqrmppa processes observed leading to increased usage of non-paged pool on Windows.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The following errors were observed on the system:
    1.) System Event log: Server was unable to allocate from the
    system non-paged pool because the pool was empty.
    2.) Queue Manager error log: The return code from the TCP/IP
    (send) call was 10055 X('2747').
    3.) FDC: ERROR_NO_SYSTEM_RESOURCES during a WriteFile operation.
    
    These errors all relate to exhausting the non-paged pool
    resources which are used primarily by the kernel for sockets,
    handles and other system objects. An observation of the
    amqrmppa process using perfmon showed an ever increasing usage
    of non-paged pool as well as handle objects (which consume non-
    paged pool). Use of the handle utility revealed these handle
    objects to be primarily of the 'Thread' type.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Any users using client applications connecting to a WebSphere
    MQ V7 queue manager. Server applications using asynchronous
    consume API calls are also affected.
    
    Platforms affected:
    Windows
    
    ****************************************************************
    PROBLEM SUMMARY:
    As part of changes made in WebSphere MQ V7, the server
    implicitly uses asynchronous consume mechanisms to deal with
    incoming client requests for messages. This results in the
    creation of a new thread which performs the asynchronous consume
    operations. However, the handle to this thread was not being
    closed after the thread had been destroyed.
    

Problem conclusion

  • WebSphere MQ was modified to ensure that the handle to the
    asynchronous consume thread was closed once that connection was
    no longer valid.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
                       v7.0
    Platform           Fix Pack 7.0.1.2
    --------           --------------------
    Windows            U200316
    
    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

    IC65023

  • 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

    2009-12-08

  • Closed date

    2010-01-11

  • Last modified date

    2010-01-11

  • 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":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSDEZSF","label":"IBM WebSphere MQ Managed File Transfer for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0.1","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
31 March 2023