Bitbucket Data Center UI showing Old java version is being read
Platform Notice: Data Center - This article applies to Atlassian products on the Data Center platform.
Note that this knowledge base article was created for the Data Center version of the product. Data Center knowledge base articles for non-Data Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
A Bitbucket Data Center UI popup shows an alert that "Support for Java 11.0.24 has been deprecated and will be removed in an upcoming release" even though the Java Version utilized in Bitbucket is Java 17.
Environment
Tested on Bitbucket Data Center 8.9.10 and also applicable to other versions of Bitbucket Data Center.
Diagnosis
A. Run the below command on Bitbucket nodes to validate the Java version configured on Bitbucket nodes and Java version used by on Bitbucket processes:
1. ps -ef | grep bitbucket
2. echo $JAVA_HOMEB. Validate the set-jre-home.sh file present in <Bitbucket_Installation_Directory>/bin directory.
Cause
This issue typically arises when the set-jre-home.sh script present in <Bitbucket_Installation_Directory>/bin directory defines the JRE_HOME parameter to a Java path (e.g., version 11.0.24) that differs from the Java version in use (e.g., version 17). In situations where the JAVA_HOME environment variable is set to Java 17, the Bitbucket processes will utilize Java 17. However, a discrepancy in the set-jre-home.sh script's JRE_HOME parameter configuration can result in pop-ups in the Bitbucket user interface, indicating a misconfiguration.
Solution
There are two possible solutions for this issue:
A. Either set the JAVA_HOME path obtained from echo $JAVA_HOME command to the JRE_HOME parameter in the set-jre-home.sh present under <Bitbucket_Installation_Directory>/bin directory and restart Bitbucket nodes.
B. Or keep JRE_HOME parameter in the set-jre-home.sh empty if JAVA_HOME is already been set under User profile on Linux Server and restart Bitbucket nodes.