Java Runtime usage isn't captured in the fleet

This may be the caused by one of the following:
  • See this A Java runtime may initially be absent from the table.
  • Check which directories on your host will be scanned to discover installations of Java Runtimes. See the steps to customize the directories that are scanned by the agent in Configuring a Management Agent for Java Management Service.
  • You're using an older Java release.
    Java Management Service relies on the Java Usage Tracker to report Java usage. Java Usage Tracker tracks how Oracle Java Runtime Environments are being used in your systems and captures the JRE version, vendor, the application being run, and other details. Additionally, JMS periodically performs a file scan to detect Java runtimes that aren't captured by the Java Usage Tracker, such as runtimes not being used or not having the Java Usage Tracker capabilities. OpenJDK binaries will be detected by JMS through file scanning but won't have usage associated with it since it doesn't have Java Usage Tracker capabilities. Java Usage Tracker is available for all releases of Java 7, and later, and also for the following older Java releases:
    • 6u25 and later updates

    • 5.0u33 and later updates

    • 1.4.2_35 and later updates

    For versions earlier than 1.8.0_60, the usage tracker properties files needs to be in the JRE installation folder. For 1.8.0_60 and later versions, the usage tracker properties file can be in a central location. As part of the agent installation, JMS currently only generates the usage tracker properties file in the central location. Although versions earlier than 1.8.0_60 have usage tracker, JMS won't capture the associated usage information, since it doesn't write usage to the central location. Usage information for these versions will be missing (even though they have usage tracker capabilities) because these runtimes need usage tracker in the JRE installations folder and not in the central location. If you want usage records, ask your System Administrator to manually place the usage tracker properties file in the JRE installations folder for these versions.
  • Check that you have correctly configured Java Usage Tracker on your host. For more information, see how to configure the Java Usage Tracker in Configuring a Management Agent for Java Management Service.