What to do about MQ Message Broker Error: AMQ9999: Channel program ended abnormally.

Document ID : KB000003978
Last Modified Date : 14/02/2018
Show Technical Document Details
Issue:

This article applies to APM for IBM WebSphere MQ

APM appears to occupy all SYSTEM.DEF channels without releasing them. Eventually, all channels are consumed.

The following error is observed in the MQ logs:

  • 05/28/14 14:57:08 - Process(1187934.147) User(mqadm) Program(amqrmppa) AMQ9999: Channel program ended abnormally.


Channel program SYSTEM.DEF.SVRCONN terminated abnormally

Environment:
All supported APM Releases
Cause:

This error occurs when the required JMS pub/sub queues have not been created to collect the Message Broker metrics.

 

Resolution:

To resolve the issue, create all the prerequisite JMS queues on the JMS Broker Queue Manager using the script "MBMonitorJMSQueues.mqsc".

This script is included with the APM for IBM WebSphere MQ (PowerPack). It contains a series of MQSC commands which create the JMS queues for the JMS protocol.

The script can be executed with the command:

runmqsc <QMGR name>/MQMonitor/properties/MBMonitorJMSQueues.mqsc

You must restart the MQMonitor agent after execution.

The JMS queues can be created on the Configuration Manager's Queue Manager if it shares its Queue Manager with any of the Brokers; otherwise, It can be created on the Queue Manager of one of the Brokers. Queue Manager details should be provided in the "JMS Broker Connection" section of the MB Monitor file.

For complete details on installing and using APM with IBM WebSphere MQ, refer to the APM for IBM WebSphere MQ Guide contained in the APM documentation set.