IT45181: XMS .NET applications connecting to a queue sharing group throw MQRC 6109 while closing the consumer

APAR status

• Closed as program error.

Error description

• XMS .NET application with sharingconversation set to 1 and
  connecting to a Z os Queue sharing group which has more than 1
  member is failing with MQRC_NO_CONNECTION_REFERENCE and throws
  the following exception to the application while closing the
  consumer
  
  IBM.XMS.IllegalStateException   HResult=0x80131500
  Message=Failed to close queue Q. XMS attempted to close a IBM MQ
  destination, but encountered an error. The destination might
  already be closed, or another thread may be performing an MQGET
  while close() is called. Use the linked exception to determine
  the cause of this error. You may be able to perform the close()
  later.   Source=amqmxmsstd   StackTrace:    at
  IBM.XMS.Client.WMQ.WmqMessageConsumer.CheckNmqiCallSuccess(Strin
  g messageid, String insert, String insertKey, Int32
  completionCode, Int32 reason, NmqiEnvironment environment,
  String probeid, WmqCommonConnection commonConnection, Hconn
  hconn)    at IBM.XMS.Client.WMQ.WmqConsumerShadow.Close()    at
  IBM.XMS.Client.WMQ.WmqMessageConsumer.Close()    at
  IBM.XMS.Client.Impl.XmsMessageConsumerImpl.Close()    at
  IBM.XMS.Client.Impl.XmsMessageConsumerImpl.Dispose()
  

Local fix

• Set SharingConversation >1 as a workaround
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  XMS .NET applications with sharing conversation set to 1 &
  connecting to a Z os Queue Sharing group which has more than 1
  member.
  
  
  Platforms affected:
  Windows, Linux on x86-64
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  XMS .NET applications always establish two connections to a
  Queue Manager. First connection is created when
  CreateConnection() is called and the second connection is
  created when CreateSession is called. This is the default
  behavior. When an XMS .NET application is connecting to a Z os
   Queue Sharing group which has more than 1 member, the
  connections are established to two different Queue Managers in
   the group as two different sockets are created when
  SharingConversation is set to 1. When closing the XMS objects,
   if a wrong connection id(the connection id which doesn't belong
  to that Queue manager) is sent to the Queue manager then the
  Queue Manager would return MQRC_NO_CONNECTION_REFERENCE.
  

Problem conclusion

• XMS .NET was using the wrong connectionId while closing the
  consumer, which now has been resolved.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v9.2 LTS   9.2.0.25
  v9.3 LTS   9.3.0.20
  v9.4 LTS   9.4.0.0
  
  The latest available maintenance can be obtained from
  'IBM MQ Recommended Fixes'
  https://www.ibm.com/support/pages/recommended-fixes-ibm-mq
  
  If the maintenance level is not yet available information on
  its planned availability can be found in 'IBM MQ
  Planned Maintenance Release Dates'
  https://ibm.biz/mqplannedmaintenance
  
  ---------------------------------------------------------------
  

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