Upgrade from 3.2 to 3.4 WAR fails

I am running bamboo on tomcat6, sun java 1.6.26. Running successfully 3.2.2. Tried upgrade to 3.4. After doing all steps and starting tomcat I got:

2012-01-09 15:33:50,195 INFO main UpgradeLauncher Checking if schema update is required...

2012-01-09 15:33:50,196 FATAL main UpgradeLauncher Failed to initialise Bamboo container


at com.atlassian.spring.container.ContainerManager.getComponent(ContainerManager.java:32)

at com.atlassian.bamboo.upgrade.UpgradeLauncher.upgradeAndStartBamboo(UpgradeLauncher.java:85)

at com.atlassian.bamboo.upgrade.UpgradeLauncher.contextInitialized(UpgradeLauncher.java:39)

at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4135)

Full log is attached. After trying to tinker around I ultimately rolled back to 3.2.2.

1 answer

This looks like a bug in our upgrade process. Could you file a ticket with support and get them to help you with it? Thanks for reporting :)

Suggest an answer

Log in or Sign up to answer
Community showcase
Asked Thursday in Jira Ops

I'm John Allspaw, Ask Me Anything about incident analysis and postmortems

I'm John Allspaw, co-founder of   Adaptive Capacity Labs, where we help teams use their incidents to learn and improve. We bring research-driven methods and approaches to drive effective inciden...

500 views 2 5
View question

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you