Commit Graph Version 2020.05.01 • Bitbucket Data Center 4.0.0 - 7.2.4 Fails to Enable
Upgraded to Bitbucket latest (version 7.2.4) this weekend; unable to enable Commit Graph.
2020-06-01 13:35:32,555 ERROR [ThreadPoolAsyncTaskExecutor::Thread 22] c.a.plugin.osgi.factory.OsgiPlugin Unable to start the plugin container for plugin 'com.bit-booster.graph' org.springframework.beans.factory.BeanDefinitionStoreException: Unexpected exception parsing XML document from URL [bundle://134.0:0/META-INF/spring/plugin-context.xml]; nested exception is java.lang.NullPointerException ... 2020-06-01 13:35:32,569 ERROR [ThreadPoolAsyncTaskExecutor::Thread 22] o.e.g.b.e.i.s.ExtenderConfiguration Application context refresh failed (NonValidatingOsgiBundleXmlApplicationContext(bundle=com.bit-booster.graph, config=osgibundle:/META-INF/spring/*.xml)) ... 2020-06-01 13:35:32,570 ERROR [ThreadPoolAsyncTaskExecutor::Thread 22] o.e.g.b.e.i.d.s.DependencyWaiterApplicationContextExecutor Unable to create application context for [com.bit-booster.graph], unsatisfied dependencies: none
I've already shutdown, deleted BITBUCKET_HOME/plugins/.osgi-cache folder and restarted the service with same results.
Comments (3)
-
-
repo owner Thanks for the bug report and confirming the known-fix for this still works! :-)
For future reference (for others seeing this page):
This is a duplicate of #116 and also
#86On each node of your datacenter cluster:
- shut down bitbucket
- take backup of $BITBUCKET_HOME/plugins/.osgi-cache/
- completely delete $BITBUCKET_HOME/plugins/.osgi-cache/
- restart bitbucket
-
repo owner - changed status to duplicate
Duplicate of
#86. - Log in to comment
After shutting down all cluster nodes, deleting .osgi-cache folder and restarting node 1, Commit Graph enabled. Please close.
Note: I wasn’t stopping all nodes before deleting the .osgi-cache cache folder