Based on this discussion on your community site we decided to upgrade from Bitbucket Server 5.14 to 5.16 so we could begin to use OpenJDK.
We have successfully installed OpenJDK 1.8.202. Configured both JAVA_HOME and JRE_HOME to point to this new installation directory for the OpenJDK as well as added an extra environment variable JVM_SUPPORT_RECOMMENDED_ARGS to allow use of OpenJDK (per this article)
Despite a restart and a reboot it appears that our installation is not fully pointing to/using the OpenJDK. Specifically the JRE in use still seems to be what was bundled with our initial Bitbucket Server installation (some background - we were on 4.1.3, upgraded to 5.14.1 and then finally to 5.16 for the OpenJDK support).
Here's why we think its not fully pointing to the OpenJDK
- In this admin screen (<our_host>/plugins/servlet/troubleshooting/view/) where we can view the System Information I can see the following (which is right)
Environment Variables
...
JAVA_HOME C:\Java\jdk8u202-b08
JVM_SUPPORT_RECOMMENDED_ARGS -Dbitbucket.allow.openjdk=true
JRE_HOME C:\Java\jdk8u202-b08\jre
...
- But in the same admin screen, further up in another section it still refers to the older version.
Java Runtime Environment
...
sun.boot.class.path c:\atlassian\bitbucket\4.1.3\jre\lib\resources.jar;c:\atlassian\bitbucket\4.1.3\jre\lib\rt.jar;c:\atlassian\bitbucket\4.1.3\jre\lib\sunrsasign.jar;c:\atlassian\bitbucket\4.1.3\jre\lib\jsse.jar;c:\atlassian\bitbucket\4.1.3\jre\lib\jce.jar;c:\atlassian\bitbucket\4.1.3\jre\lib\charsets.jar;c:\atlassian\bitbucket\4.1.3\jre\lib\jfr.jar;c:\atlassian\bitbucket\4.1.3\jre\classes
java.vm.specification.vendor Oracle Corporation
java.runtime.version 1.8.0_60-b27
I am trying to figure out why this is the case and what do we need to do to make sure it is OpenJDK that is being referred to through out the application? Am I missing any step/setting/configuration?
Cheers,
Mahesh Gudapakkam
Web & Application Developer
Massachusetts College of Art and Design