Cause

LCM has a default URL that it uses to download Oracle Java 8. When Oracle publishes a Java update, the URL changes the previous URL immediately stops working. Furthermore, the new URL cannot be predicted in advance. This means that there is a period during which the LCM default URL is incorrect and Java downloads fail by default.

This can be addressed 3 ways, any one of which is sufficient:

1. Updating the Java Version in Config Profiles
2. Using a Custom Java URL in Config Profiles
3. Updating Definitions

Updating the Java Version in Config Profiles

The LCM documentation for Managing Java Installs shows how to download a specific version of Java by updating the java-setup page of your configuration profile(s). You can set major-version, update-version, build-version, and build-hash according to the current url published by oracle.

An example URL found at that page might be http://download.oracle.com/otn-pub/java/jdk/8u191-b12/2787e4a523244c269598db4e85c51e0c/server-jre-8u191-linux-x64.tar.gz In this case, the relevant values are:

• major-version: 1.8.0, this never changes for a java 8 release.
• update-version: 191, from 8u191.
• build-version: 12, from 8u191-b12.
• build-hash: 2787e4a523244c269598db4e85c51e0c from /8u191-b12/2787e4a523244c269598db4e85c51e0c/.

Given correct values for each of the above fields, LCM will automatically construct the Oracle Java download URL.

Using a Custom Java URL in Config Profiles

If you are concerned about future outages caused by Oracle Java updates, you can host Oracle Java yourself on an internally accessible web server. See the LCM offline install kbase for details.

Updating Definitions

When Oracle releases a Java update, the engineering team that develops OpsCenter and LCM try to release updated defaults for the java-setup page as quickly as possible. This often happens within 24 hours of the Oracle Java update.

OpsCenter instances that have outbound HTTPS access to opscenter.datastax.com will automatically download these updated definitions and once this happens jobs will be successful even if you take no action.

OpsCenter instances with limited outbound connectivity, or that have had definitions updates disabled, can have definitions manually updates as described in Updating and configuring definitions files properties.

Special Considerations for Older Versions of OpsCenter

Older versions of OpsCenter may encounter a second error message related to upgrading Java: No such file or directory: 'local_policy.jar'. Upgrade OpsCenter to 6.0.11, 6.1.4, or a more recent version to resolve this issue, or work around it by unchecking the manage-jce box in the java-setup page of the relevant config-profile(s).

In Oracle Java 8u151 and later, Oracle moved the location of the export-strength JCE policy files. Due to this change, OpsCenter/LCM versions 6.0.0-6.0.10 and 6.1.0-6.1.3 are unable to perform JCE installs on Java 8u151 and later.