A production application node started experiencing high heap usage and then AD stopped monitoring the JVM altogether. During this state, I could still use JConsole to view the JMX data on that node. Additionally, another monitoring tool maintained the connection. The application node itself was still functioning (granted, performance was not great).
1) Why did AD drop this connection and stop gathering data for this node?
2) How do I get AD to reconnect and resume gathering data on this node?
Neal
Hi,
We see this is part of support request# 36551, we request you to track support help ticket for further assistance on this query.
We see by default the node property heap-storage-monitor-shutdown-
Regards,
Arun