JBoss ON agent has high CPU usage due to continuously running detail discovery scans after previously discovered resource's plug-in is disabled
Issue
- Agent CPU utilization continuously over 150%
- Spikes where CPU usage goes to 300%
- ResourceDiscoveryComponent.invoker.daemon thread consuming large part of CPU
- Agent continuously running discovery scans and inventory sync
Environment
- Red Hat JBoss Operations Network (ON) 3.2
- Agent plug-in has been disabled for a resource that had previously been discovered
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
