search cancel

APMIA MQ monitoring -- no data refresh after the MQ QMGR restart

book

Article ID: 225856

calendar_today

Updated On:

Products

CA Application Performance Management SaaS

Issue/Introduction

If QMGR is restarted then APMIA data is not updated, it just reports in the console with false data. 

Example: We had one incident where APM didn't alert for current queue depth of the queues and in APMIA showed that queue on zero .

So I restarted the Agent. After that APMIA picked up the current data from MQ side.

 

 

 

Environment

Release : SAAS

Component :

Cause

Based on the default bindtype in Queue manager. please refer this link to know where to check 

https://www.ibm.com/docs/en/ibm-mq/9.0?topic=information-queue-manager-default-bind-type#q019030___qmdefbindt

Customer environment:

DefaultBindType= SHARED

 

If it is set to shared, then some of the resources will be shared by both client (in this case our agent) and qm process.

That's the reason it is locking the process until agent is also restarted. So this is expected behavior when using MQ bindings mode for client connection.

Resolution

Working as design. 

When using bindings mode agent needs to be restarted if there is any issue restarting qm.