IBM Support

IV27153: LARGE MEMORY ALLOCATION WHEN ACCEPTING TRUNCATED MESSAGES WITHOUT SPECIFYING A MAXIMUM MESSAGE SIZE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When an application specifies that it will accept truncated
    messages but does not specify a maximum size to be accepted, it
    is possible to see large (100MB) memory allocation when it is
    not required.
    
    This can contribute to memory starvation, and associated errors
    from the queue manager.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users specifying MQGMO_ACCEPT_TRUNCATED_MSG without also
    specifying a maximum message length.
    
    Platforms affected:
    All Distributed (iSeries, all Unix and Windows)
    ****************************************************************
    PROBLEM SUMMARY:
    Where a maximum message size is not specified, but the option
    MQGMO_ACCEPT_TRUNCATED_MSG is specified, WebSphere MQ will
    allocate a memory buffer of a large size resulting in no message
    truncation taking place.
    
    The allocation of large amounts of memory can contribute to
    unnecessary memory consumption in the queue manager.
    

Problem conclusion

  • Under the circumstance where MQGMO_ACCEPT_TRUNCATED_MSG is
    specified but no maximum message size is given, the process will
    deliver the message without truncation in an appropriately sized
    buffer for the message concerned.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following:
    
                       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
    
                       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
    
    Version            v7.5
    --------           --------------------
    Fix available in:  7.5.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

    IV27153

  • 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

    2012-08-28

  • Closed date

    2013-02-20

  • Last modified date

    2013-07-08

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

    PM60991

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

Fix information

  • Fixed component name

    WMQ AIX V7

  • Fixed component ID

    5724H7221

Applicable component levels

  • R701 PSY

       UP

[{"Line of Business":{"code":"LOB36","label":"IBM Automation"},"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSFKSJ","label":"WebSphere MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0.1"}]

Document Information

Modified date:
01 October 2021