Channel status is shown as STOPPED even after the channel is restarted
Below are the behaviours of IBM Websphere MQ and Applications Manager :
- If a channel is started, the status of the channel is not changed to RUNNING. It will be in INACTIVE state until a connection is made to the channel and a get / put is performed. Refer IBM wiki
- By default, APM doesn't show inactive channels. To show inactive channels, go to Edit Monitor -> Select System Filter Objects -> Add INCLUDE_INACTIVE_CHANNELS: true in System Objects to Monitor textbox
If a channel is restarted in IBM MQ, but Applications Manager reports its status as STOPPED, the below could be the reason for that :
- The channel is restarted.
- The state of the channel is moved to INACTIVE ( not RUNNING ). You can verify the status from MQExplorer / using command : dis chstatus(channelName)
- INCLUDE_INACTIVE_CHANNELS:true filter is not added to the MQ monitor in Applications Manager.
- In this case, during the data collection, the inactive channels are not returned by the MQ, and hence it is shown as down.
- The status will not change from STOPPED.
To fix this issue, set INCLUDE_INACTIVE_CHANNELS:true, after which the channels with inactive status also will be shown in the Applications Manager UI.
If the issue still exists, reach out to our support with the screenshot of the error obtained to appmanager-support@manageengine.com along with the latest Support Information File (SIF) from Applications Manager with print all logs enabled for analysis.
New to ADSelfService Plus?
Related Articles
The health of the IBM Websphere MQ monitor is not affected by default, if the listener status is stopped.
The health of the listener will not be affected unless the threshold is configured for the status attribute under Listener monitoring. You have to configure a threshold for status manually so that the health status of the listener is affected. To ...The channel state is changed to inactive in IBM MQ, but the alert is not triggered by Applications Manager
Alert won't get triggered by default unless threshold is configured for 'Status' attribute under Channel monitoring. To trigger an alert, configure a threshold such that the severity is 'Critical' if status changes to "STOPPED".Process in AppManager UI is shown as down while the process is up and running in the machine
Every time a server restarts, the PID of the processes get updated. So the processes added in the monitor will be shown as down. It is recommended that you have static contents alone in the process Commands and Args. It is also recommended that you ...Configure "/server-status" page for Oracle HTTP server
In order to monitor an Oracle HTTP server in Applications Manager, the '/server-status' page must be configured on the target Oracle HTTP server that needs to be monitored. This can be accomplished by following these steps: Step 1 - Enable the ...Configure "/server-status" page for IBM HTTP server
In order to monitor an IBM HTTP server in Applications Manager, the '/server-status' page must be configured on the target IBM HTTP server that needs to be monitored. This can be accomplished by following these steps: Step 1 - Enable the ...