IT48052: CLIENT CHANNEL STATUS REMAINS STARTING FOR FAILED CONNECTION WHEN MAXIMUM NUMBER OF ACTIVE CHANNELS IS EXCEEDED.

APAR status

• Closed as program error.

Error description

• If a client channel is attempted to be started, while the
  configured amount of MaxActiveChannels is already running, an
  additional entry in status STARTING will be listed in the
  DIS CHS output until the queue manager has been restarted.
  

Local fix

Problem summary

• The channel status entry was allocated before it was verified
  that MaxActiveChannels has not been reached yet. However it was
  not cleaned up after should that have been the case already.
  

Problem conclusion

• Product has been changed to verify that a slot is available
  and MaxActiveChannels has not been reached yet before allocating
  and trying to start the new channel instance.
  ----------------------------------------------------------------
  The fix is targeted for delivery in maintenance level 8.1.0.30
  of IBM MQ for HPE NonStop 8.1.
  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 FOR HPE NS O

• Fixed component ID

  5724A3904

Applicable component levels