JIRA is unavaliable due to subversion plugin

Richard Koivusalo September 24, 2013

Hi,

We use JIRA 5.2, and subversion plugin v.0.10.13. Jira starts but the service is unavaliable. This seems to be due to subversion plugin.

See atlassian-jira log :

2013-09-25 10:12:06,132 localhost-startStop-1 ERROR [atlassian.jira.service.OfBizServiceConfigStore] Unable to create a service config for service with the name : Subversion Revision Indexing Service

com.atlassian.jira.service.OfBizServiceConfigStore$ClassNotFoundServiceException: Could not find class: com.atlassian.jira.plugin.ext.subversion.revisions.RevisionIndexService

at com.atlassian.jira.service.OfBizServiceConfigStore.instantiateServiceContainer(OfBizServiceConfigStore.java:217)

at com.atlassian.jira.service.OfBizServiceConfigStore.getServiceContainer(OfBizServiceConfigStore.java:179)

at com.atlassian.jira.service.OfBizServiceConfigStore.getAllServiceConfigs(OfBizServiceConfigStore.java:159)

at com.atlassian.jira.service.DefaultServiceManager.loadServices(DefaultServiceManager.java:309)

at com.atlassian.jira.service.DefaultServiceManager.ensureServicesLoaded(DefaultServiceManager.java:299)

at com.atlassian.jira.service.DefaultServiceManager.getServices(DefaultServiceManager.java:74)

at com.atlassian.jira.upgrade.ConsistencyCheckImpl.getServices(ConsistencyCheckImpl.java:167)

at com.atlassian.jira.upgrade.ConsistencyCheckImpl.ensureSingleService(ConsistencyCheckImpl.java:521)

at com.atlassian.jira.upgrade.ConsistencyCheckImpl.checkMailListenerAndService(ConsistencyCheckImpl.java:382)

at com.atlassian.jira.upgrade.ConsistencyCheckImpl.checkDataConsistency(ConsistencyCheckImpl.java:221)

at com.atlassian.jira.upgrade.ConsistencyCheckImpl.checkConsistency(ConsistencyCheckImpl.java:210)

at com.atlassian.jira.upgrade.ConsistencyCheckImpl.initialise(ConsistencyCheckImpl.java:174)

at com.atlassian.jira.startup.DefaultJiraLauncher$3.run(DefaultJiraLauncher.java:106)

at com.atlassian.jira.config.database.DatabaseConfigurationManagerImpl.doNowOrEnqueue(DatabaseConfigurationManagerImpl.java:284)

at com.atlassian.jira.config.database.DatabaseConfigurationManagerImpl.doNowOrWhenDatabaseActivated(DatabaseConfigurationManagerImpl.java:169)

at com.atlassian.jira.startup.DefaultJiraLauncher.postDbLaunch(DefaultJiraLauncher.java:98)

at com.atlassian.jira.startup.DefaultJiraLauncher.access$100(DefaultJiraLauncher.java:25)

at com.atlassian.jira.startup.DefaultJiraLauncher$1.run(DefaultJiraLauncher.java:64)

at com.atlassian.jira.util.devspeed.JiraDevSpeedTimer.run(JiraDevSpeedTimer.java:33)

at com.atlassian.jira.startup.DefaultJiraLauncher.start(DefaultJiraLauncher.java:59)

at com.atlassian.jira.startup.LauncherContextListener$1.create(LauncherContextListener.java:80)

at com.atlassian.jira.startup.LauncherContextListener$1.create(LauncherContextListener.java:75)

at com.atlassian.multitenant.impl.MultiTenantComponentMapImpl.get(MultiTenantComponentMapImpl.java:121)

at com.atlassian.multitenant.impl.MultiTenantComponentMapImpl.onTenantStart(MultiTenantComponentMapImpl.java:165)

at com.atlassian.multitenant.impl.DefaultMultiTenantManager$1.consume(DefaultMultiTenantManager.java:134)

at com.atlassian.multitenant.impl.DefaultMultiTenantManager$1.consume(DefaultMultiTenantManager.java:131)

at com.atlassian.multitenant.impl.DefaultMultiTenantManager.runForEachListener(DefaultMultiTenantManager.java:256)

at com.atlassian.multitenant.impl.DefaultMultiTenantManager.startTenant(DefaultMultiTenantManager.java:130)

at com.atlassian.multitenant.impl.DefaultMultiTenantManager.startAll(DefaultMultiTenantManager.java:203)

at com.atlassian.jira.startup.LauncherContextListener.contextInitialized(LauncherContextListener.java:108) <+5> (StandardContext.java:4791) (StandardContext.java:5285) (LifecycleBase.java:150) (ContainerBase.java:1559) (ContainerBase.java:1549)

at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)

at java.util.concurrent.FutureTask.run(FutureTask.java:166)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)

at java.lang.Thread.run(Thread.java:722)

Caused by: java.lang.ClassNotFoundException: Class 'com.atlassian.jira.plugin.ext.subversion.revisions.RevisionIndexService' not found.

at com.atlassian.jira.plugin.DefaultComponentClassManager.constructEvenIfNotEnabled(DefaultComponentClassManager.java:151)

at com.atlassian.jira.plugin.DefaultComponentClassManager.newInstance(DefaultComponentClassManager.java:70)

at com.atlassian.jira.service.OfBizServiceConfigStore.loadServiceClass(OfBizServiceConfigStore.java:351)

at com.atlassian.jira.service.OfBizServiceConfigStore.instantiateServiceContainer(OfBizServiceConfigStore.java:212)

... 39 more

2013-09-25 10:12:06,148 localhost-startStop-1 ERROR [atlassian.jira.service.OfBizServiceConfigStore] The class 'com.atlassian.jira.plugin.ext.subversion.revisions.RevisionIndexService' could not be found. This can happen when a plugin is uninstalled or disabled

2013-09-25 10:12:06,148 localhost-startStop-1 ERROR [atlassian.jira.service.OfBizServiceConfigStore] A NoOp Service has been returned and hence 'Subversion Revision Indexing Service' will not do anything until fixed.

Best regards

Richard

2 answers

0 votes
Theinvisibleman
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
September 24, 2013
Hi Richard, Perhaps you could try going to your Jira Home Directory, head to the 'data' folder, under the indexes subdirectory, an delete the Subversion indexes? Once done, restart your Subversion and Jira
Max Rößler December 22, 2018

I know this is over 5 years old, but for people like me searching for this. In Version 7.3.5 and later the path could be find in "<JIRA_HOMEDIR>\caches\indexes\plugins\atlassian-subversion-revisions"

0 votes
Richard Koivusalo September 24, 2013

How should we solve it?

Suggest an answer

Log in or Sign up to answer