-
Title
JMXDiscovery not discovering local Java processes owned by another user -
Description
Running JMXDiscovery does not detect the Java processes running on the host. The popup message indicated after clicking Property Lookup:
System properties cannot be shown because either the discovery agent is inactive, or there are no running JVM processes. Make sure the discovery agent and processes you want to inspect are all running, then click ' Rediscover'.
-
Cause
The Foglight Agent Manager (FglAM) is owned by user 'foglight' while the Java processes are owned by another user. The JMXDiscovery API is designed to only monitor the Java processes owned by the user that runs the FglAM. -
Resolution
RESOLUTION 1:
If permitted, change the ownership of the FglAM files and directories to be the same user who owns the Java process. Restart the FglAM to take effect and rerun the JMXDiscovery.
RESOLUTION 2:
Add the JMXAgent via the JMX Service URL. Ensure the required jmxremote parameters are passed to the java startup scripts and your Java server is configured for JMX monitoring. See "Generic JDK5+ Platform MBean Server" section in the JMX agent user guide.