IBM Support

IJ04255: MQ XMS .NET client fails to connect to a queue manager using thecertificate label set in the application

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

  • An XMS .NET client fails to connect to a queue manager if
    certificate label is set in the application.  Following error is
    thrown
    CWSMQ0006E:  An exception was received during the call to the
    method  ConnectionFactory.CreateConnection: CompCode: 2,
    Reason: 2393.
    During execution of the specified method an exception was
    thrown by another component.
    
    The following can be seen in the queue manager error log:
    
    The channel is lacking a certificate to use for the SSL
    handshake. The channel
    name is 'TEST' (if '????' it is unknown at this stage in the
    SSL processing).
    The remote host is 'ABC(xxx.xx.xx.xx)'.
    The channel did not start.
    

Local fix

  • Set the following properties in mqclient.ini file:
    
    SSL:
      CertificateLabel={client certificate labelname]
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    XMS.NET APPLICATIONS USING XMSC.WMQ_SSL_CLIENT_CERT_LABEL
    PROPERTY TO SET THE CERTIFICATE LABEL
    
    
    Platforms affected:
    Windows
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    If certificate label is set using XMSC.WMQ_SSL_CLIENT_CERT_LABEL
    property in the XMS.NET application, XMS.NET doesn't pick the
    value set in the application,rather uses the default value i.e
    "ibmwebspheremquserid",which is wrong.If certificate label is
    set in the application, XMS.NET should use the same while
    establishing a connection to the queue manager.
    

Problem conclusion

  • If certificate label property is set in the application, XMS.NET
    should use the same for establishing a connection to the queue
    manager.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v8.0       8.0.0.9
    v9.0 LTS   9.0.0.4
    
    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

    IJ04255

  • Reported component name

    IBM MQ XMS V 8.

  • Reported component ID

    5724H7257

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-02-19

  • Closed date

    2018-03-29

  • Last modified date

    2018-04-10

  • 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 XMS V 8.

  • Fixed component ID

    5724H7257

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
10 April 2018