IBM Support

IC63182: A WEBSPHERE MQ XMS FOR .NET CLIENT GETS ILLEGALSTATEEXCEPTION WHEN TRYING TO RECEIVE A XML MESSAGE.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When trying to use a WebSphere MQ XMS for .NET client to
    to receive an XML message an illegal state exception occurs
    and generates the following error:
    IBM.XMS.IllegalStateException: CWSMQ0006E: An exception was
    received during the call to the method {1}: {0}. During
    execution of the specified method an exception was thrown by
    another component. See linked exception for more information.
    at IBM.XMS.WMQ.WmqMessageConsumer.GetAMessage(Int64 timeOut)
    at IBM.XMS.WMQ.WmqMessageConsumer.ReceiveAsync(Int64 timeout)
    at IBM.XMS.WMQ.WmqAsynchronous.Run()
    Linked Exception : CompCode: 2, Reason: 2018
    MQ reason code 2018 = 0x000007e2 =  MQRC_HCONN_ERROR.
    In the MQ XMS .NET client trace log, an out-of-bounds error is
    reported as seen below:
    source=IBM.XMS.WMQ.WmqMessageConsumer org=IBM prod=WebSphere
    component=Message Service Client for .NET thread=?1 : 0?
    System.ArgumentException: Offset and length were out of bounds
    for the array or count is greater than the number of elements
    from index to the end of the source collection.
    at System.Buffer.BlockCopy(Array src, Int32 srcOffset,
    Array dst, Int32 dstOffset, Int32 count)
    at IBM.WMQ.MQFAP.zstMQGET(Int32 hConn, Int32 hObj,
    MQMessageDescriptor& mqmd, MQGetMessageOptions& mqgmo, Int32
    bufferLength, Byte?? buffer, Int32& dataLength, MQLPIGetOpts
    lpiGetOpts,Int32& compCode, Int32& reason)
    at IBM.WMQ.MQFAP.MQGET(Int32 hConn, Int32 hObj,
    MQMessageDescriptor& mqmd, MQGetMessageOptions& mqgmo, Int32
    bufferLength, Byte?? buffer,Int32& dataLength, Int32& compCode,
    Int32& reason)
    at IBM.WMQ.MQManagedClientConnector.MQGET(Int32 hConn,
    Int32 hObj, MQMessageDescriptor& md, MQGetMessageOptions& gmo,
    Int32 bufferLength, Byte?? buffer, Int32& dataLength, Int32&
    compCode, Int32& reason)
    at IBM.WMQ.MQDestination.Get(MQMessage message,
    MQGetMessageOptions gmo, Int32 maxMsgSize)
    at IBM.WMQ.MQDestination.Get(MQMessage message,
    MQGetMessageOptions gmo)
    at IBM.XMS.WMQ.WmqMessageConsumer.GetAMessage(Int64 timeOut)
    ----
    
    
    ADDITIONAL KEYWORDS: CWSMQ0006E HCONN Illegal State Exception
    dot net dotnet IA9H Message Service Client XMS.NET
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Customers using MQ .NET managed client applications to retrieve
    huge messages.
    
    
    Platforms affected:
    Windows
    
    ****************************************************************
    PROBLEM SUMMARY:
    The .NET client application fails while getting large messages.
    This is caused by a buffer over flow problem. The failure
    happens when the client tries to retrieve data beyond the
    actual size of the buffer.
    

Problem conclusion

  • The buffer offset is calculated incorrectly which leads to
    data being read beyond the actual buffer length. The APAR fix
    corrects the error in the offset calculation.
    
    ---------------------------------------------------------------
    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

    IC63182

  • Reported component name

    WMQ WINDOWS V7

  • Reported component ID

    5724H7220

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-09-15

  • Closed date

    2009-11-18

  • Last modified date

    2009-11-18

  • 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

  • R700 PSY

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCPQ63","label":"APAR \/ Maintenance"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
18 November 2009