can't enable subversion plugin in Jira 7

Hello,

Just testing the migration procedure to JIRA 7 and i'm facing an error when installing Subversion plugin.

No errors in log, but the timeout (60s) is hit when attempting to enable it, and the plugin remains "disabled".

 

Any clue on how to get extra info about the cause of this problem?

 

JIRA 7.1.1 / Subversion plugin 3.0.1

 

Thanks.

2 answers

0 vote
Vasiliy Zverev Community Champion Mar 15, 2016

Try to investigate atlassian-jira.log.

Setup logs for com.atlassian.jira.plugin.ext.subversion to DEBUG and got the following error. 

If I uninstall the Subversion plugin and re-install from scratch, UPM waits for 1 min before rendering the plugin as inactive:

2016-03-29 12:56:54,364 UpmAsynchronousTaskManager:thread-3 INFO root 835x163x1 12xmkfj a.b.c.d /rest/plugins/1.0/installed-marketplace [c.a.plugin.util.WaitUntil] Plugins that have yet to be enabled: (1): [com.atlassian.jira.plugin.ext.subversion], 60 seconds remaining
2016-03-29 12:56:55,364 UpmAsynchronousTaskManager:thread-3 INFO root 835x163x1 12xmkfj a.b.c.d /rest/plugins/1.0/installed-marketplace [c.a.plugin.util.WaitUntil] Plugins that have yet to be enabled: (1): [com.atlassian.jira.plugin.ext.subversion], 59 seconds remaining
2016-03-29 12:56:56,364 UpmAsynchronousTaskManager:thread-3 INFO root 835x163x1 12xmkfj a.b.c.d /rest/plugins/1.0/installed-marketplace [c.a.plugin.util.WaitUntil] Plugins that have yet to be enabled: (1): [com.atlassian.jira.plugin.ext.subversion], 1 seconds remaining
2016-03-29 12:57:53,381 UpmAsynchronousTaskManager:thread-3 INFO root 835x163x1 12xmkfj a.b.c.d /rest/plugins/1.0/installed-marketplace [c.a.plugin.util.WaitUntil] Plugins that have yet to be enabled: (1): [com.atlassian.jira.plugin.ext.subversion], 0 seconds remaining
2016-03-29 12:57:54,381 UpmAsynchronousTaskManager:thread-3 INFO root 835x163x1 12xmkfj a.b.c.d /rest/plugins/1.0/installed-marketplace [c.a.plugin.manager.DefaultPluginManager] Disabling com.atlassian.jira.plugin.ext.subversion
2016-03-29 12:58:03,147 ThreadPoolAsyncTaskExecutor::Thread 51 DEBUG root 835x163x1 12xmkfj a.b.c.d /rest/plugins/1.0/installed-marketplace [c.a.j.p.e.subversion.revisions.RevisionIndexer] Number of repositories: 137
2016-03-29 12:58:03,194 ThreadPoolAsyncTaskExecutor::Thread 51 INFO root 835x163x1 12xmkfj a.b.c.d /rest/plugins/1.0/installed-marketplace [c.a.j.p.e.subversion.messages.DefaultIndexMessageService] Registered IndexMessageConsumer: com.atlassian.jira.plugin.ext.subversion.messages.DefaultIndexMessageService$IndexMessageConsumer@22a25fe7
java.lang.IllegalStateException: LifecycleProcessor not initialized - call 'refresh' before invoking lifecycle methods via the context: NonValidatingOsgiBundleXmlApplicationContext(bundle=com.atlassian.jira.plugin.ext.subversion.atlassian-jira-subversion-plugin, config=osgibundle:/META-INF/spring/*.xml): startup date [Tue Mar 29 12:56:54 CEST 2016]; root of context hierarchy
at org.springframework.context.support.AbstractApplicationContext.getLifecycleProcessor(AbstractApplicationContext.java:357)
at org.springframework.context.support.AbstractApplicationContext.doClose(AbstractApplicationContext.java:877)
at org.eclipse.gemini.blueprint.context.support.AbstractOsgiBundleApplicationContext.doClose(AbstractOsgiBundleApplicationContext.java:187)
at org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext.access$501(AbstractDelegatedExecutionApplicationContext.java:60)
at org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext$2.run(AbstractDelegatedExecutionApplicationContext.java:194)
at org.eclipse.gemini.blueprint.util.internal.PrivilegedUtils.executeWithCustomTCCL(PrivilegedUtils.java:85)
at org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext.normalClose(AbstractDelegatedExecutionApplicationContext.java:190)
at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.close(DependencyWaiterApplicationContextExecutor.java:382)
at org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext.doClose(AbstractDelegatedExecutionApplicationContext.java:214)
at org.springframework.context.support.AbstractApplicationContext.close(AbstractApplicationContext.java:836)
at org.eclipse.gemini.blueprint.extender.internal.activator.LifecycleManager.closeApplicationContext(LifecycleManager.java:326)
at org.eclipse.gemini.blueprint.extender.internal.activator.LifecycleManager.access$200(LifecycleManager.java:51)
at org.eclipse.gemini.blueprint.extender.internal.activator.LifecycleManager$2.run(LifecycleManager.java:291)
at org.eclipse.gemini.blueprint.extender.internal.util.concurrent.RunnableTimedExecution$MonitoredRunnable.run(RunnableTimedExecution.java:55)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
2016-03-29 12:58:03,194 ThreadPoolAsyncTaskExecutor::Thread 51 DEBUG root 835x163x1 12xmkfj a.b.c.d /rest/plugins/1.0/installed-marketplace [c.a.j.p.e.subversion.revisions.RevisionIndexer] Number of repositories: 137
2016-03-29 12:58:03,194 Gemini Blueprint context shutdown thread2 INFO root 835x80x1 12xmkfj a.b.c.d /rest/plugins/1.0/com.logister.jira.logister-key [c.a.j.p.e.subversion.messages.DefaultIndexMessageService] Unregistered IndexMessageConsumer: com.atlassian.jira.plugin.ext.subversion.messages.DefaultIndexMessageService$IndexMessageConsumer@22a25fe7
2016-03-29 12:58:03,194 ThreadPoolAsyncTaskExecutor::Thread 51 ERROR root 835x163x1 12xmkfj a.b.c.d /rest/plugins/1.0/installed-marketplace [o.e.g.b.e.internal.support.ExtenderConfiguration] Application context refresh failed (NonValidatingOsgiBundleXmlApplicationContext(bundle=com.atlassian.jira.plugin.ext.subversion.atlassian-jira-subversion-plugin, config=osgibundle:/META-INF/spring/*.xml))
org.springframework.beans.factory.BeanCreationNotAllowedException: Error creating bean with name 'schedulerLauncher': Singleton bean creation not allowed while the singletons of this factory are in destruction (Do not request a bean from a BeanFactory in a destroy method implementation!)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:216)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:299)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:194)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:755)
at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:757)
at org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext.access$1600(AbstractDelegatedExecutionApplicationContext.java:60)
at org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext$4.run(AbstractDelegatedExecutionApplicationContext.java:325)
at org.eclipse.gemini.blueprint.util.internal.PrivilegedUtils.executeWithCustomTCCL(PrivilegedUtils.java:85)
at org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext.completeRefresh(AbstractDelegatedExecutionApplicationContext.java:290)
at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$CompleteRefreshTask.run(DependencyWaiterApplicationContextExecutor.java:137)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
2016-03-29 12:58:03,194 UpmAsynchronousTaskManager:thread-3 DEBUG root 835x163x1 12xmkfj a.b.c.d /rest/plugins/1.0/installed-marketplace [c.a.activeobjects.osgi.ActiveObjectsServiceFactory] onPluginDisabledEvent removing delegate for [com.atlassian.jira.plugin.ext.subversion]
2016-03-29 12:58:03,194 ThreadPoolAsyncTaskExecutor::Thread 51 ERROR root 835x163x1 12xmkfj a.b.c.d /rest/plugins/1.0/installed-marketplace [o.e.g.b.e.i.dependencies.startup.DependencyWaiterApplicationContextExecutor] Unable to create application context for [com.atlassian.jira.plugin.ext.subversion.atlassian-jira-subversion-plugin], unsatisfied dependencies: none
org.springframework.beans.factory.BeanCreationNotAllowedException: Error creating bean with name 'schedulerLauncher': Singleton bean creation not allowed while the singletons of this factory are in destruction (Do not request a bean from a BeanFactory in a destroy method implementation!)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:216)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:299)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:194)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:755)
at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:757)
at org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext.access$1600(AbstractDelegatedExecutionApplicationContext.java:60)
at org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext$4.run(AbstractDelegatedExecutionApplicationContext.java:325)
at org.eclipse.gemini.blueprint.util.internal.PrivilegedUtils.executeWithCustomTCCL(PrivilegedUtils.java:85)
at org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext.completeRefresh(AbstractDelegatedExecutionApplicationContext.java:290)
at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$CompleteRefreshTask.run(DependencyWaiterApplicationContextExecutor.java:137)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
2016-03-29 12:58:03,210 UpmAsynchronousTaskManager:thread-3 DEBUG root 835x163x1 12xmkfj a.b.c.d /rest/plugins/1.0/installed-marketplace [c.a.jira.plugin.JiraPluginManager] Plugin with key 'com.atlassian.jira.plugin.ext.subversion' has been disabled.
2016-03-29 12:58:03,225 UpmAsynchronousTaskManager:thread-3 DEBUG root 835x163x1 12xmkfj a.b.c.d /rest/plugins/1.0/installed-marketplace [c.a.jira.plugin.JiraPluginManager] Disabling plugin with key 'com.atlassian.jira.plugin.ext.subversion' without persisting. This should occur if this plugin depends on a plugin that is currently being upgraded
2016-03-29 12:58:03,225 UpmAsynchronousTaskManager:thread-3 ERROR root 835x163x1 12xmkfj a.b.c.d /rest/plugins/1.0/installed-marketplace [c.a.plugin.manager.PluginEnabler] Unable to start the following plugins due to timeout while waiting for plugin to enable: com.atlassian.jira.plugin.ext.subversion

Also, I have about 150 SVN repositories defined ... I have been "playing" with the repos and Ive found this query that seems to show the repo's config in Jira:

select pe.id,property_key,propertyvalue
from propertyentry pe
join propertystring ps on pe.id = ps.id
where property_key = 'svn.root';

In further tests Ive shut down JIRA instance and UPDATEd propertyentry/propertystring tables to replace all property keys starting with "svn" to "1svn" (to avoid using that info from SVN plugin).

Then the plugin starts in 1-2s.

In other tests I left only about 50 SVN repos with the "svn" and the rest (~100) as "1svn.XXXX". The plugin starts smoothly in 1-2s.

I think that the problem is somehow related to the number of SVN repositories ...

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published yesterday in Jira

5 ways you can make the most of Jira Software and Bitbucket Cloud

As part of the Bitbucket product team I'm always interested in better understanding what kind of impact the use of our tools have on the way you work. In a recent study we conducted of software devel...

59 views 0 5
Read article

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