Bitbucket Server fails to start when using Java 11

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

Problem

When using Java 11, Bitbucket Server or Data Center does not start. No error is displayed on the console, but the <BitbucketHome>/log/launcher.log file shows the following error:

1 2 3 Unrecognized VM option 'PrintGCTimeStamps' Error: Could not create the Java Virtual Machine. Error: A fatal exception has occurred. Program will exit.

Note: Instead of PrintGCTimeStamps the name of another Java Virtual Machine (JVM) option may be listed, for instance PrintGCDateStamps.

Diagnosis

Environment

  • Any version of Bitbucket Server started with Java 11.

Cause

One or more of the JVM options configured for Bitbucket Server are no longer supported in Java 11.

Solution

Resolution

To resolve this problem you can do one of the following:

  1. Use an older supported version of Java before version 11

  2. Remove the offending JVM options by following these steps:

    1. Open the file <BitbucketInstallation>/bin/_start-webapp.sh

    2. Locate the line starting with JVM_SUPPORT_RECOMMENDED_ARGS - this line lists all the custom JVM options you have configured

    3. From the value of this variable (within the double quotes) remove the offending JVM option(s) - for instance if the offending JVM option listed in the log file is PrintGCDateStamps, remove -DPrintGCDateStamps

    4. Save the file

    5. Start Bitbucket Server

    6. If Bitbucket Server still fails to start, check the <BitbucketHome>/log/launcher.log file again to see if there are more offending JVM options you need to remove.

Updated on April 2, 2025

Still need help?

The Atlassian Community is here for you.