This issue appears when a management agent scans its host for the presence of Java runtimes. If the management agent encounters a symbolic link when scanning a file system it may skip the link and subsequent directories.

This issue is resolved in version 210918.1427 of the management agent software. Ensure that this version (or later) is installed on all of your hosts. You can download the latest version of the software by using the contextual menu of a fleet in the Fleet Dashboard or from a fleet's Fleet Properties Tab. See also Installing a Management Agent.

The fleet Metrics charts can display end times inconsistent with the date-time editors.

There is no workaround for this issue.

It is possible to select an invalid date range in the fleet Metrics.

There is no workaround for this issue. The user should increase the interval to greater than one minute, or reduce the time period.

The "Parent Directory is not included" warning indicates that the path you added to the list of excluded paths is one that is not currently included. (The additional path has no effect on the selection of file system paths that the fleet's management agents scan on their hosts to discover Java Runtime installations.)

The "Parent Directory is not included" warning can be invalid if the include and exclude paths contain overlapping wildcard patterns. (For more information on the use of wildcard patterns, see Include/Exclude Path Patterns.)

The workaround for this issue is as follows: replace wildcard patterns with an explicit path.

You're not able to navigate to more than a depth of three levels in the breadcrumb trail of the Java Management Service user interface.

You can navigate up to a maximum of three levels from the selected fleet in a breadcrumb trail. If you attempt to navigate beyond three levels, Java Management Service will reset the breadcrumb trail.

This issue appears when listing Java runtimes without providing a compartment ID. You'll see an error message similar to compartmentId is not available.

To workaround this issue, you should always include a compartment ID when listing Java runtimes.

There is a delayed reporting of an inactive agent in a deleted managed instance. If you delete a compute with an agent installed in JMS, and when a user navigates to this deleted compute, the status shows "ACTIVE". The status will only change to "INACTIVE" after 60 days.

This issue appears when summarizing and/or listing Java runtimes without providing managed instance ID. The host ID value is included in results only if summarizing and/or listing provides managed instance ID as one of the query parameters. This is an intended design, and there is no workaround for this issue.

The following known issues are associated with the Onboarding wizard:

1. The Onboarding wizard creates default OCI resources (user group, dynamic group, compartment and policies) similar to those described in Setting Up Oracle Cloud Infrastructure for Java Management Service). If you require customized resources, then please adapt the instructions in that section.
2. The Onboarding wizard may mistakenly identify your tenancy as incorrectly configured if you have created customized OCI resources manually.
3. The policies created by the Onboarding wizard will be invalid If you delete the OCI user group or dynamic group resources created by the Onboarding wizard and then recreate them manually. To work around this, you must also delete the policies and recreate them manually.
4. The Onboarding wizard will duplicate OCI resources if the compartment it created is deleted, and subsequently, the wizard is run for a second time.
5. The fleet compartment doesn't show up after running the JMS prerequisite setup. To see the changes, you'll need to refresh the page or log off and then log in again.

The installation path, application, and managed instance information across these releases will be presented in the same Java Runtimes details page.

Your Work request can fail during the plugin initialization process. The plugin process needs to be in the RUNNING state for a Work request to succeed.

Crypto event analysis detects applications not only running on Oracle JDK and already reported by JMS, but also applications running on OpenJDK distributions. Those applications running on OpenJDK distributions detected during Crypto event analysis will not be browsable from the Crypto event analysis report in an Analysis Report. See Analysis Reports Details

The start time in Crypto event analysis report may incorrectly show a value greater than the completion time.

The Associate resources table in work request module will display two entries for each managed instances involved in a Java libraries scan work request. This is because the scan involves Java server libraries scan and a static jar libraries scan.

If a managed instance has any release of JDK 19 release already installed, then a subsequent LCM install operation of a JDK 19 release will fail. For instance, if a managed instance has JDK 19 already installed, a subsequent LCM install operation of JDK 19.0.1 on the managed instance will fail

For JBoss, the target type clustered is applicable only to applications deployed on servers that belong to a server group and within a Managed Domain. Applications deployed in Standalone mode will be indicated as non-clustered.

If you want to run a crypto analysis or use JDK Flight Recorder on an application that's running Oracle JDK 8, then you need to use the parameter -XX:+UnlockCommercialFeatures parameter when you invoke the application.

JMS plugin registration fails if you using older version of Oracle Cloud Agent (OCA). Upgrade OCA to v1.25 or later to resolve the issue.

Scan for Java libraries will not detect the libraries used by the application deployed on JBoss Java server.

Management Agents will have the Silent availability status even after uninstallation from a managed instance. Management Agent Cloud Service may take up to 30 days to cleanup and remove such Silent agents. In this period, JMS may still create work requests for these instances.

When you enable advanced features using the UI, JMS creates the log object and object storage bucket with specific names. However, if you enable advanced features through an API, you must provide names for both log object and object storage bucket.

On Windows managed instances, Advanced Features other than Lifecycle Management will only work on Java applications, application servers, and other programs that are being run with administrator privileges.