Bamboo 3.2 to 4.0 Upgrade Fails

Still need help?

The Atlassian Community is here for you.

Ask the community

Symptoms

Upgrading Bamboo from version 3.2 to version 4.0 or 4.0.1 fails on upgrade task 2707 with the following error:

2013-07-19 17:34:52,969 INFO [4-UpgradeTaskBackgroundThread:pool-11-thread-1] [AbstractUpgradeManager] Completed upgrade task 2704 successfully.
2013-07-19 17:34:52,974 INFO [4-UpgradeTaskBackgroundThread:pool-11-thread-1] [AbstractUpgradeManager] -----------------------------------------------------------------------------
2013-07-19 17:34:52,974 INFO [4-UpgradeTaskBackgroundThread:pool-11-thread-1] [AbstractUpgradeManager] Running upgrade task 2707 : Move Job Repository to Plan and add default tasks
2013-07-19 17:34:52,974 INFO [4-UpgradeTaskBackgroundThread:pool-11-thread-1] [AbstractUpgradeManager] -----------------------------------------------------------------------------
2013-07-19 17:34:52,992 INFO [4-UpgradeTaskBackgroundThread:pool-11-thread-1] [UpgradeTask2707MoveJobRepositoryToPlan] Adding default checkout task to job PROJ1-PLAN4-JOB1
2013-07-19 17:34:53,022 ERROR [4-UpgradeTaskBackgroundThread:pool-11-thread-1] [LazyInitializer] Exception initializing proxy
net.sf.hibernate.HibernateException: Could not initialize proxy - the owning Session was closed
    at net.sf.hibernate.proxy.LazyInitializer.initialize(LazyInitializer.java:47)
    at net.sf.hibernate.proxy.LazyInitializer.initializeWrapExceptions(LazyInitializer.java:60)
    at net.sf.hibernate.proxy.LazyInitializer.getImplementation(LazyInitializer.java:164)
    at net.sf.hibernate.proxy.CGLIBLazyInitializer.intercept(CGLIBLazyInitializer.java:108)
    at com.atlassian.bamboo.plan.AbstractChain$$EnhancerByCGLIB$$3073e6da.getBuildDefinition(<generated>)
    at com.atlassian.bamboo.plan.PlanHelper.getConfigObject(PlanHelper.java:200)
    at com.atlassian.bamboo.plugins.maven.dependencies.AutomaticDependencyManagementPlugin.getConfig(AutomaticDependencyManagementPlugin.java:108)
...

Resolution

  1. Sometimes just restarting Bamboo and letting that upgrade task run again can solve this problem.
  2. This issue is identified and fixed in a later Bamboo versions - 4.x. 
  3. Bamboo version 3.2 is EOL since August 2013, so there won't be any point release for this issue.
  4. The last resort is to upgrade to another version in between 3.2 and 4.0 before upgrading to version 4.0 or 4.0.1.

 

Last modified on Nov 2, 2018

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.