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 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

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

  1. Stop the FishEye/Crucible instance;

  2. Go to WindowsStart Menu > All Programs > Fisheye > Configure Fisheye

  3. The Configure Fisheye window blinks and doesn't load.

Cause

The option to add Java variables was not installed during the initial installation of Fisheye/Crucible.

Solution

  1. Stop the Fisheye/Crucible Service

    • Open Start.

    • Search for Services and select the top result to open the console.

    • Select the service Atlassian Fisheye .

    • Select the Stop button.

  2. 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 >> Java

    • Select options then copy and save the current content (just in case you need to revert to the initial configuration).

    • Add the JVM parameters as below:

      1 2 3 4 5 6 -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.log

      This 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 OK to Save .

  3. Start the Atlassian Fisheye service.

  4. Verify the parameters are updated on Fisheye/Crucible by navigating to Administration > Sys Info/Support > System Info and 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.

Updated on March 24, 2025

Still need help?

The Atlassian Community is here for you.