IBM Support

IC68152: WMQ v7 .NET Client connection reports unhandled exception IBM.XMS.XMSException Message="CWSMQ0006E"

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Unmanaged .NET clients fail to flow user ID and password
    information to the server-side despite the client having set
    the correct fields in a MQConnectionSecurityParameters
    structure. This may result in connection failures as a result
    of authentication if the server-side requires this information
    for security exit processing. An example client which will fail
    in this way is the XMS client when setting the user id and
    password in the following manner:
    connectionfactory.SetStringProperty(XMSC.USERID, "auserid");
    connectionfactory.SetStringProperty
    (XMSC.PASSWORD, "apassword");
    
    The client connection is successful but the security exit causes
    the client to throw an exception due to invalid user ID and
    password data:
    
    IBM.XMS.XMSException was unhandled
    
    Message="CWSMQ0006E: An exception was received during the call
    to the method ConnectionFactory.CreateConnection: CompCode: 2,
    Reason: 2059
    
    Explanation: Server has asked to close channel. CompCode : 2
    Reason : 2059. During execution of the specified method an
    exception was thrown by another component. See the linked
    exception for more information."
    Source="IBM.XMS.Client.WMQ"
    ErrorCode="CWSMQ0006"
    

Local fix

  • No local fix available.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Any users of WebSphere MQ making use of the unmanaged .NET
    client via XMS and passing user ID/password data to server-side
    security exits.
    
    Platforms affected:
    Windows
    
    ****************************************************************
    PROBLEM SUMMARY:
    The problem occurred because the unmanaged native layer was not
    aware that a user ID and password had been specified by the
    managed layer. This is because there are several ways of
    specifying this information in a MQConnectionSecurityParameters
    class dependent on the circumstances. The managed client such
    as XMS was setting the field known as userid which is
    of 'String' type on an instance of a
    MQConnectionSecurityParameters object prior to passing this to
    the native layer in a MQConnectOptions structure. However, the
    native unmanaged layer checks the fields 'CSPUserIdPtr'
    and 'CSPUserIDOffset' to determine whether a user ID was set.
    This is because the MQCSP struct passed to the native layer
    does not include a field called 'userid' to represent the user
    id. Instead, it relies on the aforementioned fields being
    filled in correctly. Therefore, it is the responsibility of the
    managed .NET layer to convert the userid field in the
    MQConnectionSecurityParameters class to either 'CSPUserIdPtr'
    or 'CSPUserIDOffset' in the MQCSP struct prior to passing this
    to the native layer. The native layer will then pick up the
    user ID and password settings.
    

Problem conclusion

  • The WebSphere MQ .NET unmanaged client was modified to
    ensure that the user ID and password parameters are converted
    in the managed layer to a format understood by the native layer
    prior to transitioning to said native layer. The unmanaged
    client then successfully determines that the parameters are set
    and flows them in appropriate network flows to the server side.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
                       v7.0
    Platform           Fix Pack 7.0.1.3
    --------           --------------------
    Windows            U200320
    
    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

    IC68152

  • 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

    2010-04-26

  • Closed date

    2010-05-19

  • Last modified date

    2010-05-19

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

    IZ73672

  • 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:
19 May 2010