IBM Support

IT22577: Memory leak with client MQCONNX when specifying multiple connection names

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

  • Memory leak is observed with a multi threaded client
    application,  when the client connection information is supplied
    in MQCONNX with multiple connection names.
    
    ****************************
    MQCD     ClientConn = {MQCD_CLIENT_CONN_DEFAULT};
    MQCNO   cno = {MQCNO_DEFAULT};   /* Connect Options
                  */
    
    strncpy(ClientConn.ConnectionName,
                 "localhost(1111),localhost(2222)", --------- When
    multiple connection names are specified, memory leak is observed
                 MQ_CONN_NAME_LENGTH);
    
    strncpy(ClientConn.ChannelName,
                 "CLIENT.CHANNEL_QM",
                 MQ_CHANNEL_NAME_LENGTH);
    
    /* Point the MQCNO to the client connection definition */
    cno.ClientConnPtr = &ClientConn;
    cno.Version = MQCNO_VERSION_2;
    
    MQCONNX("QM",                 /* queue manager
                     */
    	&cno,                                 /* connect options
                   */
    	&hQm,                               /* connection handle
                 */
    	&CompCode,                    /* completion code
                   */
    	&Reason);                         /* reason code
                       */
    
    ****************************
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users connecting to queue manager with MQCONNX call and using
    the contents of the ClientConnOffset or ClientConnPtr fields of
    the MQCNO structure
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    A coding error in the MQ client code meant that internal data
    structures representing the channel definition were not
    correctly freed when multiple connection names were suppled,
    leaking the memory associated with these structures.
    

Problem conclusion

  • The MQ client code has been corrected to prevent this memory
    leak.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v8.0       8.0.0.11
    v9.0 LTS   9.0.0.5
    
    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

    IT22577

  • Reported component name

    IBM MQ BASE MP

  • Reported component ID

    5724H7251

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-09-28

  • Closed date

    2018-06-15

  • Last modified date

    2018-06-15

  • 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 MP

  • Fixed component ID

    5724H7251

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":"8.0.0.0","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
15 June 2018