Bamboo Data Center fails to startup on Windows with Cannot invoke "com.atlassian.bamboo.setup.BootstrapManager.isSetupComplete()"
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
At times when performing an upgrade or a fresh Bamboo Data Center install, you might encounter a Cannot invoke "com.atlassian.bamboo.setup.BootstrapManager.isSetupComplete()"
error message on the <bamboo-install>/logs/catalina.out
log file and difficulties in accessing Bamboo from the User Interface.
Environment
The solution has been validated in Bamboo Data Center 10.2.1 but may be applicable to other versions.
This only affects Bamboo Data Center running with:
Windows
Diagnosis
When upgrading or performing a fresh installation of Bamboo Data Center, it is crucial to correctly specify the bamboo-home
directory in the bamboo-init.properties
file located at <bamboo-install>\atlassian-bamboo\WEB-INF\classes
.
There are two possible issues that can be observed:
- If the Bamboo configuration is commented out or incorrect, you may encounter errors in the
<bamboo-install>/logs/catalina.out
file:SEVERE [main] org.apache.catalina.core.StandardContext.listenerStart Exception sending context initialized event to listener instance of class [com.atlassian.bamboo.upgrade.UpgradeLauncher] java.lang.NullPointerException: Cannot invoke "com.atlassian.bamboo.setup.BootstrapManager.isSetupComplete()" because "bootstrapManager" is null at com.atlassian.bamboo.upgrade.UpgradeLauncher.upgradeAndStartBamboo(UpgradeLauncher.java:101) at com.atlassian.bamboo.upgrade.UpgradeLauncher.contextInitialized(UpgradeLauncher.java:56) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4016)
If Bamboo cannot recognize the specified path due to incorrect slashes or an invalid path, it may default to creating the home directory within the installation folder.
Cause
- If the error message is showing in the
<bamboo-install>/logs/catalina.out
, it is possibly that thebamboo-home
property is commented out on<bamboo-install>\atlassian-bamboo\WEB-INF\classes\
.bamboo-init.properties
- The bamboo-home path might have the incorrect syntax for Windows. In many programming languages, a single backslash is used as an escape character. This means that it is used to give special meaning to the character that follows it. To avoid the escape sequence interpretation, a double backslash is used. This tells the language to treat it as a literal backslash.
- For example, in a string,
C:\\atlassian\\bamboo-home
would be correctly interpreted as the file pathC:\atlassian\bamboo-home.
- For example, in a string,
Solution
- Double check that the bamboo-home path is uncommented inside
<bamboo-install>\atlassian-bamboo\WEB-INF\classes\bamboo-init.properties
. - So that Bamboo and Windows can properly interpret the path use double backslash or forward slashes as the example below:
C:\\atlassian\\bamboo-home or C:/atlassian/bamboo-home