IT34083: Messages stuck in the cluster transmit queue intermittently due to cluster channel in use (AMQ9514E)

APAR status

• Closed as program error.

Error description

• Some messages are stuck in the cluster
  transmit queue intermittently and can not be sent to the
  destination, because the cluster channel is in use. Start and
  stop channel commands like the below do not help to bring up
  the channel again:
  .
  start channel (TO.QMgrName)
  stop channel (TO.QMgrName) mode (force)
  start channel (TO.QMgrName)
  stop channel (TO.QMgrName) mode (terminate)
  .
  The channel remains in "stopping" status and reports the channel
  in use error AMQ9514E. Only a restart of the queue manager help
  in such a situation. Besides, removing the auto defined cluster
  sender channel and re-establishing it by using RESET / REFRESH
  cluster commands, also did not help to solve the problem.
  

Local fix

• Restart the queue manager
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  MQ 9.1 users dealing with SDR-RCVR and Cluster sender-receiver
  channels.
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  An unlikely timing window existed in code specific to MQ 9.1
  whereby multiple channels stopping and starting concurrently
  could cause an invalid state entry to be written to the internal
  channel status data. This invalid state entry would prevent the
  channel named in the state entry from starting, reporting that
  it was already in use.
  

Problem conclusion

• The MQ queue manager code maintaing internal channel status has
  been modified to overcome the issue.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v9.0 LTS   9.0.0.13
  v9.1 LTS   9.1.0.11
  v9.x CD    9.1.5
  
  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

  IBM MQ BASE MP

• Fixed component ID

  5724H7271

Applicable component levels