Details
-
Bug
-
Resolution: Fixed
-
Medium
-
7.0.1, 7.1.2, 7.2.2, 7.3.5, 7.4.5, 7.5.2, 7.6.2, 7.7.4, 7.8.3, 7.9.0, 7.13.3
-
38
-
Severity 3 - Minor
-
52
-
Description
Issue Summary
When starting a Confluence node with Java 11 on a Data Center deployment, the following warning appears in the application log:
2020-11-12 18:31:58,355 WARN [Catalina-utility-2] [com.hazelcast.instance.HazelcastInstanceFactory] log Hazelcast is starting in a Java modular environment (Java 9 and newer) but without proper access to required Java packages. Use additional Java arguments to provide Hazelcast access to Java internal API. The internal API access is used to get the best performance results. Arguments to be used: --add-modules java.se --add-exports java.base/jdk.internal.ref=ALL-UNNAMED --add-opens java.base/java.lang=ALL-UNNAMED --add-opens java.base/java.nio=ALL-UNNAMED --add-opens java.base/sun.nio.ch=ALL-UNNAMED --add-opens java.management/sun.management=ALL-UNNAMED --add-opens jdk.management/com.sun.management.internal=ALL-UNNAMED
The Hazelcast documentation recommends giving access to specific Java packages for better performance.
It's unknown for now if this has any implications on Confluence features or performance.
Steps to Reproduce
- Install a vanilla instance of Confluence Data Center.
- It must be a version higher than 7.0.1, when support for Java 11 was introduced.
- Configure the node to run with Java 11 (i.e. AdoptOpenJDK 11)
- Start a Confluence node.
Expected Results
Confluence starts with all required modules loaded and Hazelcast doesn't throw a warning about not being able to access some Java packages.
Actual Results
When loading Hazelcast, the following message is logged in atlassian-confluence.log:
2020-11-12 18:31:58,355 WARN [Catalina-utility-2] [com.hazelcast.instance.HazelcastInstanceFactory] log Hazelcast is starting in a Java modular environment (Java 9 and newer) but without proper access to required Java packages. Use additional Java arguments to provide Hazelcast access to Java internal API. The internal API access is used to get the best performance results. Arguments to be used: --add-modules java.se --add-exports java.base/jdk.internal.ref=ALL-UNNAMED --add-opens java.base/java.lang=ALL-UNNAMED --add-opens java.base/java.nio=ALL-UNNAMED --add-opens java.base/sun.nio.ch=ALL-UNNAMED --add-opens java.management/sun.management=ALL-UNNAMED --add-opens jdk.management/com.sun.management.internal=ALL-UNNAMED
Workaround
Add the following entries to setenv.sh:
JDK_JAVA_OPTIONS="--add-modules java.se --add-exports java.base/jdk.internal.ref=ALL-UNNAMED ${JDK_JAVA_OPTIONS}" JDK_JAVA_OPTIONS="--add-opens java.base/java.nio=ALL-UNNAMED --add-opens jdk.management/com.sun.management.internal=ALL-UNNAMED ${JDK_JAVA_OPTIONS}" JDK_JAVA_OPTIONS="--add-opens java.base/sun.nio.ch=ALL-UNNAMED --add-opens java.management/sun.management=ALL-UNNAMED ${JDK_JAVA_OPTIONS}" export JDK_JAVA_OPTIONS
Attachments
Issue Links
- is related to
-
-
- Closed
-
- relates to
-
-
- Gathering Impact
-