IBM Support

IT26021: XMS .NET multithreaded async client consumer application fails to process poison messages in bindings mode.

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

  • If XMS .NET Multithreaded Async consumer application is used in
    bindings mode to consume poison messages, the application
    crashes with the following error:
    
    Failed to create XMS message.
    The wrong message type or properties were specified when
    creating a base message.
    Linked Exception : System.ArgumentOutOfRangeException: Valid
    values are
    between 0 and 65535, inclusive.
    Parameter name: codepage
       at IBM.XMS.Client.WMQ.Common.WmqCcsid.GetDotnetEncoding(Int32
    mqCcsid)
       at
    IBM.XMS.Client.WMQ.WmqReceiveMarshal.ConstructProviderMessageFro
    mRFH2(In
    t32 messageBodyStyle)] [False]
    

Local fix

  • The exception is seen only in Bindings Mode. If the application
    is run using Managed/Unmanaged Mode,the exception is not thrown.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users of XMS .NET multithreaded async consumer applications
    processing poison messages in bindings mode.
    
    
    Platforms affected:
    Windows
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    If XMS .NET Multi threaded Async consumer application is used in
    bindings mode to consume poison messages,XMS .NET client
    intermittently failed to parse the message encoding field  which
    leads to the application crashes.
    

Problem conclusion

  • IBM has not been able to reproduce the reported issue, and so
    additional debug capabilities have been added such that
    additional information will be available to IBM support should
    the problem reoccur.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v8.0       8.0.0.15
    v9.0 LTS   9.0.0.11
    v9.1 CD    TBC.
    v9.1 LTS   9.1.0.6
    
    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

    IT26021

  • 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

    2018-08-20

  • Closed date

    2020-06-08

  • Last modified date

    2020-06-08

  • 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"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
10 June 2020