Unable to compile Soy template in plugin module
Platform Notice: Server and Data Center Only - This article only applies to Atlassian products on the server and data center platforms.
When accessing the Bamboo UI it may not render properly. The following error is displayed instead of the dashboard (it can appear in the logs as well):
com.atlassian.soy.renderer.SoyException: Unable to compile Soy templates at: com.atlassian.plugins.atlassian-nav-links-plugin:rotp-menu at com.atlassian.soy.impl.DefaultSoyManager.render(DefaultSoyManager.java:162) at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2197) ... 190 more
Check if the
$BAMBOO_HOME/atlassian-bamboo.log files are indicating that plugins are disabled due to a timeout:
WARN [Timer-4] [internal.dependencies.startup.DependencyWaiterApplicationContextExecutor] timeout Timeout occurred before finding service dependencies for [NonValidatingOsgiBundleXmlApplicationContext(bundle=com.atlassian.aui.plugin-integration-sal, config=osgibundle:/META-INF/spring/*.xml)]
Bamboo bundled plugin Shared Access Layer (SAL) is not being enabled due to a timeout during startup. This plugin is required to render Bamboo pages.
The cause of the shorter timeout being reached can vary but its commonly related to resource contention while Bamboo is bootstrapping or the plugin load being slowed down by something such as antivirus.
- Shutdown Bamboo.
Add the JVM parameter:setenv.sh
In the installation folder of Bamboo edit either
bin/setenv.bat(non Windows Service) or
bin/setenv.shfile in a text editor.
- Edit Window Service Java Options. See Configuring your system properties for steps on how configure additional arguments for Bamboo running as a Windows service.
Clean the cache by removing the files inside the directories below:
This will remove cache files only. It will not permanently remove any plugins. These directories will be recreated during the next Bamboo startup.
- Start Bamboo.