MQ Agent Autodiscovery Queue
Article ID: 190215
Updated On:
Products
CA Application Performance Management Agent (APM / Wily / Introscope)
CA Application Performance Management (APM / Wily / Introscope)
INTROSCOPE
DX Application Performance Management
Issue/Introduction
We had an issue where the agent was apparently able to write to the autodiscovery queue but could not read the queue. The agent proceeded to bombard the QM with connections which greatly impacted the mainframe as a whole. We believe the issue began with a network outage but the agent was never able to recover properly.
Environment
Release : 10.7.0
Component : APM Agents
Resolution
APM10.7.0HF57
Additional Information
APM10.7.0HF57_DE437614_DE447928.zip
DE437614: Introduced a hidden property to delay the reconnection attempts in case of disconnections.
MQMonitor.properties file.
mq.autodiscovery.reconnect.qm.interval=60000
The above-mentioned property will delay the reconnection by the number of milli-secs that is mentioned. So, MQMonitor will again try to connect after 60 secs.
DE437614: Introduced a hidden property to delay the reconnection attempts in case of disconnections.
MQMonitor.properties file.
mq.autodiscovery.reconnect.qm.interval=60000
The above-mentioned property will delay the reconnection by the number of milli-secs that is mentioned. So, MQMonitor will again try to connect after 60 secs.
Feedback
Yes
No
Powered by
