Editing JVM parameters in Fisheye/Crucible on Windows with no option to add Java variables to the service
Platform Notice: Data Center Only - This article only applies to Atlassian apps 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
Summary
In some versions of Windows where Fisheye/Crucible is installed as a service, there is no option to add Java variables to the service. In these cases, you can add the properties by viewing the option list in the registry.
Environment
Fisheye/Crucible 4.7.2
Windows 10
Diagnosis
Stop the
FishEye/Crucibleinstance;Go to Windows
Start Menu > All Programs > Fisheye > Configure FisheyeThe
Configure Fisheyewindow blinks and doesn't load.
Cause
The option to add Java variables was not installed during the initial installation of Fisheye/Crucible.
Solution
Stop the
Fisheye/CrucibleServiceOpen Start.
Search for
Servicesand select the top result to open the console.Select the service
Atlassian Fisheye.Select the
Stopbutton.
Edit the JVM parameters
Go to the Registry Editor
(Start > regedit.exe).Find the Services entry:
HKEY_LOCAL_MACHINE >> SOFTWARE >> WOW6432Node >> Apache Software Foundation >> Procrun 2.0 >> Atlassian Fisheye >> Parameters >> JavaSelect
optionsthen copy and save the current content (just in case you need to revert to the initial configuration).Add the JVM parameters as below:
-Xmx2048m -Xms2048m -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=C:\Atlassian\Data\fecru\var\log -XX:+PrintGCTimeStamps -verbose:gc -Xloggc:C:\Atlassian\Data\fecru\var\log\atlassian-fecru-gc%t.logThis will update the minimum and maximum JVM heap size to 2G, enable heap dump when OOO error occurs, and allow for future analysis of the garbage collection activities. Ensure there are no spaces after the last letter of each line.
Select
OKtoSave.
Start the
Atlassian Fisheyeservice.Verify the parameters are updated on
Fisheye/Crucibleby navigating toAdministration > Sys Info/Support > System Infoand looking at"JVM Input Arguments".
Possible error
In case the Fisheye Service fails to start, check the following files for errors:
D:\Program Files\Atlassian\Data\fecru\service-logs\stderr
D:\Program Files\Atlassian\Data\fecru\service-logs\stdout
Common issues could be attributed to spaces between the added JVM parameters.
Was this helpful?