IT37223: IBM MQ Managed .NET Client fails unable to connect to queue manager using OpenShift routes

APAR status

• Closed as program error.

Error description

• OpenShift routes rely on TLS Server Name Indication (SNI)
  information to route connections to the correct service. If an
  attempt was made to connect an IBM MQ Managed .NET client to a
  queue manager using an OpenShift route, the connection failed
  with MQRC 2538
  (MQRC_HOST_NOT_AVAILABLE) when connecting to OpenShift:
  
  Connecting to queue manager..
  MQException received. Details: 2538 - MQRC_HOST_NOT_AVAILABLE
     at IBM.WMQ.MQQueueManager.Connect(String queueManagerName)
     at IBM.WMQ.MQQueueManager..ctor(String queueManagerName,
  Hashtable properties)
     at SimplePut.SimplePut.CreateQMgrConnection() in
  C:\SimplePut.cs:line 203
     at SimplePut.SimplePut.PutMessages() in C:\SimplePut.cs:line
  220
  End of SimplePut Application
  

Local fix

• The unmanaged MQ .NET client can be used. This requires
  installing the MQ client.
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users using a managed .NET MQ client connecting to a queue
  manager running in OpenShift Cluster with OutboundSNI is set to
  HOSTNAME
  
  
  Platforms affected:
  Windows, Linux on x86-64
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  A logic error in the managed MQ .NET classes meant that the SNI
  SERVERNAME was set to '*' while initiating SSL authentication
  although OutboundSNI property is set to HOSTNAME.
  
  As '*' is not the actual hostname, this caused the failure in
  establishing connection to queue manager, due to incorrect SNI
  information being provided to OpenShift.
  

Problem conclusion

• IBM MQ managed .NET client code has been corrected to set
  SERVERNAME to the respective hostname if OutboundSNI property is
  set to HOSTNAME.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v9.2 LTS   9.2.0.4
  v9.x CD    9.2.3
  
  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 is sysrouted FROM one or more of the following:

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

Fix information

• Fixed component name

  MQ BASE V9.2

• Fixed component ID

  5724H7281

Applicable component levels