How to point to a different JAVA installation in Crowd Windows Service
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs 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
Problem
When using your own JDK with Crowd, you may want to upgrade the Java version to a later one and change the one Crowd uses. Following the instructions to change the path to JAVA_HOME may not work when you run Crowd as a Windows Service.
Resolution #1 - via Command Line
Open the Windows Services via Command Line as in the instructions of this documentation (expand Windows Service section).
Into the JAVA properties screen, click on the
Javatab to see the list of current start-up options.Uncheck the "Use default' option.
Edit the filled Java Virtual Machine and point to the jvm.dll file of the new JAVA 64-bit installation.
Click 'OK'.
Start Crowd.
Resolution #2 - via the Windows Registry
Open the Windows Registry as in the instructions of this documentation (expand Windows Service section);
Find the Services entry:
32-bit:
HKEY_LOCAL_MACHINE >> SOFTWARE >> Apache Software Foundation >> Procrun 2.0 >> Crowd64-bit:HKEY_LOCAL_MACHINE >> SOFTWARE >> Wow6432Node >> Apache Software Foundation >> Procrun 2.0 >> CrowdClick on
Parameters >> Java.Change the
Jvmsetting to point to the jvm.dll file of the new JAVA 64-bit installation.
Was this helpful?