IBM Support

IT27232: When using a connection name list there is a memory leak in the channel code

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • When providing a channel definition to a native MQ client (C,
    C++, RPG, COBOL, Unmanaged .NET) via API, MQSERVER environment
    variable or pre-connect exit and the channel has a connection
    name with comma separated values, each connection attempt leaks
    heap storage. The storage is not freed until the process
    terminates.
    
    The problem does not affect applications using a client
    connection definition table (CCDT), Java or fully managed .NET
    clients or channel definitions that do not use comma separated
    values.
    

Local fix

  • Use only one entry in the connection name field.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    User with native clients (C, C++, unmanaged .NET, RPG, COBOL)
    with channel definitions that use comma separated connection
    names and source this information via API (MQCONNX, connect,
    etc), MQSERVER environment variable or a pre-connect exit are
    potentially affected.
    
    Users using CCDT files to provide channel configuration are not
    affected.
    
    The application would need to attempt to a queue manager
    multiple times, this includes application logic (loops), client
    auto-reconnect or multiple threads.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    Internal data structures used to represent channels for comma
    separated hosts are added to a list of resources to free when
    using a single channel definition source such as API, MQSERVER
    or pre-connect exit. A logic omission meant that the code to
    free the structures once they were no longer in use was never
    executed.
    

Problem conclusion

  • Resource cleanup checks are now performed when clients attempt
    to connect to a queue manager, regardless of the source of the
    connection data.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v8.0       8.0.0.12
    v9.0 LTS   9.0.0.6
    v9.1 CD    9.1.2
    v9.1 LTS   9.1.0.2
    
    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

    IT27232

  • Reported component name

    IBM MQ BASE M/P

  • Reported component ID

    5724H7261

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-12-06

  • Closed date

    2019-01-23

  • Last modified date

    2019-01-23

  • 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

    IBM MQ BASE M/P

  • Fixed component ID

    5724H7261

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.0","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
23 January 2019