Bamboo fails to startup, due to multiple deployments
Symptoms
Bamboo fails to start and this error is written in the logs:
2009-02-16 06:08:00,244 WARN [main] [ActiveManagementCoordinator] A C3P0Registry mbean is already registered.
...
2009-02-16 06:08:04,643 INFO [main] [KahaStore] Kaha Store using data directory /home/ci-admin/bamboo/jms-store/kaha.db
2009-02-16 06:08:04,655 ERROR [main] [BrokerService] Failed to start ActiveMQ JMS Message Broker. Reason: org.apache.activemq.kaha.impl.StoreLockedExcpetion: Kaha Store kaha.db is already opened by this application.
org.apache.activemq.kaha.impl.StoreLockedExcpetion: Kaha Store kaha.db is already opened by this application.
at org.apache.activemq.kaha.impl.KahaStore.lock(KahaStore.java:437)
Cause
Deploying Bamboo twice on the same application container.
For instance Tomcat's default server.xml has the following entry, which deploys any .war file in the webapps folder:
server.xml
<Host name="localhost" appBase="webapps"
unpackWARs="true" autoDeploy="true"
xmlValidation="false" xmlNamespaceAware="false">
</Host>If there is another entry in server.xml like:
<Host name="my.business.org" appBase="">
<Context path="/" docBase="/usr/local/tomcat/apache-tomcat-6.0.18/webapps/bamboo" />
</Host>then both the exploded WAR and the application given in the context above are deployed.
Resolution
- Unpack WAR manually to a place outside of Tomcat.
- Specify the the location in the
<Context ... docBase="..." />setting.
Last modified on Jun 24, 2013
Powered by Confluence and Scroll Viewport.