IBM Support

IZ66692: Fully Managed .NET client fails with Probe ID CO052000 and error message AMQ9207 in the logs.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • An exception with Probe ID CO052000 is produced in the fully
    managed .NET client during an MQ API call when receiving data
    from the remote end. The FFST contains invalid data when
    attempting to read a TSH segment from the socket. The TSH was
    missing from the data on the socket.
    An error message AMQ9207 is also found in the logs.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Any users of WebSphere MQ using the fully-managed .NET client.
    
    Platforms affected:
    Windows
    
    ****************************************************************
    PROBLEM SUMMARY:
    The problem was caused by a programming error when reading data
    from the socket. The documentation for the socket.Receive call
    states 'the Receive method will read as much data as is
    available, up to the number of bytes specified by the size
    parameter'. Therefore, it may read less bytes than the size
    parameter. The fully managed .NET client was issuing 1 Receive
    call on the socket and assuming that an entire MQ message
    segment was present. However, due to high network latency and
    large message sizes, an incomplete TSH segment was present on
    the socket at the time the first call was issued. As a result,
    a subsequent Receive call retrieved the second half of the
    incomplete TSH once it had arrived on the socket.
    

Problem conclusion

  • WebSphere MQ was modified to ensure that the socket processing
    layer would repeatedly issue Receive calls on the socket until
    one entire MQ message segment was present. The buffer returned
    would then contain the entire MQ message segment as opposed to
    only the first part of it. Subsequent socket calls would then
    correctly retrieve the next logical MQ message segment instead
    of the second half of a previous MQ message segment.
    
    ---------------------------------------------------------------
    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

    IZ66692

  • 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

    2009-12-11

  • Closed date

    2010-02-18

  • Last modified date

    2010-02-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

    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:
18 February 2010