What’s New in Java Management Service
Java Management Service (JMS) has advanced significantly.
It is now provided to all Java users on OCI at no additional cost, apart from the modest expense of monitoring, logging, and alarms. It has been implemented globally across all OCI regions. For further details on these minimal operational costs and choices, see the price information below.
New features and capabilities are added to JMS on a regular basis through new releases. The most intriguing new features in the most recent version, 4.0, are the following: the capacity to
Clients may:
Utilize JMS insights to improve workloads (desktop, server, and cloud) within the organization.By locating out-of-date Java installations, unapproved apps, and Java runtime and application inconsistencies, you can safeguard your Java SE investments. As an illustration,you find out via JMS that your application is really running on JDK 8 while you were expecting it to be running on JDK 11.JMS assists system administrators in responding to inquiries like:
- Which manufacturers are supplying the Java installations in my setting?
- Do my apps use the Java installations that they are supposed to use?
- Are programs that aren't permitted running?
- How many installations of obsolete Java do I have?
Oracle has the answers to these queries since they are the guardians of Java. Oracle is in a unique position to use its knowledge to obtain important insights about the performance, compliance, and behavior of Java applications.
How does it operate?
The Java consumption Tracker is used by Java Management Service to report Java consumption. The Java Usage Tracker records information on the vendor, program being executed, JRE version, and other aspects of how Oracle Java Runtime Environments are utilized on your computers. Furthermore, every now and again JMS does a file scan to find Java runtimes that are either not being used or do not have the capabilities of the Java Usage Tracker, thus they are not detected by the tracker.
For example, JMS will identify OpenJDK binaries through file scanning, but it won't be able to display the usage associated with them since OpenJDK binaries lack Java Usage Tracker features, which the more feature-rich Oracle JDK does. Java Usage Monitor