IBM Support

IV21819: XMS APPLICATION RETURNS SYSTEM.OUTOFMEMORYEXCEPTION WHILE CREATE CONSUMERS DURING INCREASED LOAD

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Error Description
    Message service client (XMS) for .NET v2.0.0.x running with
    WebSphere MQ v7.0.1.x client fails with
    System.OutOfMemoryException while significantly increasing
    the number of Consumers. Exception is hit with around 2000
    consumers from single application process.
    
    Application set-up is as follows:
    Create XMS Connection
    Create XMS Session
    Create XMS Destination(Queue/Topic)
    Create large number of XMS Consumers (Sync or Async,
    Durbale/Non-Durable)
    
    
    The error message shown in the XMS logs, while creating a non
    durable subscriber :
    
    Warning [0f6decad-63aa-4a20-9a95-5c439fb496f6#UnsSession.
    CreateNonDurableSubscriptions#: System.OutOfMemoryException
    exception
    ocurred while subscribing to
    System.Collections.ObjectModel.ReadOnlyCollection`1[System.Strin
    g]
    topicsException Recd Msg:Exception of type 'System.
    OutOfMemoryException' was thrown.
    at
    IBM.XMS.Client.WMQ.WmqConsumerShadow..ctor(XmsPropertyContext
    xmsProps,
    WmqConsumerOwner helper, WmqDestination destination, String
    selector,
    Boolean nolocal, String subscriptionName, Byte[] subID)
    at IBM.XMS.Client.WMQ.WmqAsyncConsumerShadow..ctor
    (XmsPropertyContext xmsProps, WmqConsumerOwner helper,
    WmqDestination
    destination, String selector, Boolean nolocal, String
    subscriptionName)
    at IBM.XMS.Client.WMQ.WmqMessageConsumer.set_MessageListener
    (ProviderMessageListener value)
    at
    IBM.XMS.Client.Impl.XmsMessageConsumerImpl.set_MessageListener
    (MessageListener value)
    
    Debug diagnostics capturing the objects consuming memory in the
    w3wp.exe process shows
    mscorwks.dll (a known Windows memory manager) is
    responsible for most of the outstanding allocations. These
    allocations show to have originated from the following
    module(s)
    and function(s):
    0x20097A4
    0x63FBD94
    System.Collections.Generic.Dictionary`2[[System.__Canon,
    mscorlib],
    [System.Int32, mscorlib]].FindEntry(System.__Canon)
    mscorjit!emitter::emitEndCodeGen+16c
    IBM.XMS.Admin.Objects.WmqXmsFactory.CreateTopic(System.String
    

Local fix

  • Local Fix￘
    none
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Applications that would need large number of consumers to be
    created. Process memory will increase by 32kb with each consumer
    created.
    
    Platforms affected:
    Windows
    
    ****************************************************************
    PROBLEM SUMMARY:
    XMS Applications, when create a large number of Message
    consumers, these message consumers will create a 32kb byte array
    internally. With large volumes of Message Consumers, the process
    memory observed to be growing high at the rate of 32kb and
    eventually fails with OutOfMemoryException once the permitted
    memory for the single process has reached on Windows OS.
    

Problem conclusion

  • XMS Message Consumer has been fixed to not create 32kb byte
    arrays as default but create the buffer as and when required for
    messages.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
                       v7.0
    Platform           Fix Pack 7.0.1.9
    --------           --------------------
    Windows            7.0.1.09
    
                       v7.1
    Platform           Fix Pack 7.1.0.2
    --------           --------------------
    Windows            7.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

    IV21819

  • Reported component name

    MSG SRVCS CL .N

  • Reported component ID

    5724M2100

  • Reported release

    200

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-05-25

  • Closed date

    2012-06-29

  • Last modified date

    2013-02-13

  • 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

    MSG SRVCS CL .N

  • Fixed component ID

    5724M2100

Applicable component levels

  • R200 PSY

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCRTPP","label":"SupportPac"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"2.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
13 February 2013