IBM Support

IC69174: WMQ XMS .NET V2.0 CLIENT IS FAILING WITH CWSMQ0006E MQ RC=2278 MQRC_CLIENT_CONN_ERROR AND 2058 MQRC_Q_MGR_NAME_ERROR

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 IBM Message Service Client
    for .NET (XMS .NET) v2.0 to do a MQCONNX to connect to a queue
    manager, it is failing with
    IBM.XMS.XMSException: CWSMQ0006E: An exception was received
    during the call to the method ConnectionFactory.
    CreateConnection: System.IO.IOException.
    
    The MQ trace reveals that when trying to find a match for the
    queue manager name it is failing with Reason: 2058 0x0000080a
    MQRC_Q_MGR_NAME_ERROR and after the 2058 error there is also
    a reason 2278 0x000008e6  MQRC_CLIENT_CONN_ERROR.
    
    An XMS trace reveals the following exception associated with
    trying to find the correct client entry in the client channel
    table (CCDT)
    System.ArgumentOutOfRangeException
    Message: 'maxValue' must be greater than zero.
    Parameter name: maxValue
    StackTrace:
    at System.Random.Next(Int32 maxValue)
    at IBM.WMQ.MQChannelListEntry.OrderWeightedChannelEntry()
    at IBM.WMQ.MQChannelTable.CreateChannelEntryLists
    (MQChannelListEntrynameList)
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users with .Net clients of version 7.0.1.1 and above and using
    a CCDT table from queue manager prior to version 7.0.1.1.
    
    Platforms affected:
    Windows
    
    ****************************************************************
    PROBLEM SUMMARY:
    The WebSphere MQ .Net client 7.0.1.1 version and above will fail
    to read Channel Definitions properly when a CCDT table created
    from a pre-7.0.1.1 version queue manager is being used.
    

Problem conclusion

  • The problem was due to the additional properties added as part
    of 7.0.1.1 client.  These values where not getting initialized
    to default values when CCDT tables created from older version of
    queue managers were used.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
                       v7.0
    Platform           Fix Pack 7.0.1.4
    --------           --------------------
    Windows            U200323
    
    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

    IC69174

  • Reported component name

    WMQ WINDOWS V7

  • Reported component ID

    5724H7220

  • Reported release

    701

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-06-11

  • Closed date

    2010-06-29

  • Last modified date

    2010-06-29

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

    IZ76985

  • 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

  • R701 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.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
29 June 2010