java.lang.RuntimeException Error scheduling service caused by Multiple services with name

Still need help?

The Atlassian Community is here for you.

Ask the community

Symptoms

After JIRA startup, the following appears in the atlassian-jira.log:

2013-08-16 02:54:35,486 localhost-startStop-1 ERROR [sal.core.lifecycle.DefaultLifecycleManager] Unable to start component: $Proxy555
java.lang.RuntimeException: Error scheduling service
	at com.atlassian.sal.jira.scheduling.JiraPluginScheduler.scheduleJob(JiraPluginScheduler.java:106)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.lang.reflect.Method.invoke(Unknown Source)

...
Caused by: java.lang.IllegalArgumentException: Multiple services with name 'com.atlassian.jira.plugin.ext.bamboo.service.PlanStatusUpdateServiceImpl:job' exist.
	at com.atlassian.jira.service.OfBizServiceConfigStore.getServiceConfigForName(OfBizServiceConfigStore.java:134)
	at com.atlassian.jira.service.DefaultServiceManager.getServiceWithName(DefaultServiceManager.java:162)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
...
Caused by: java.lang.IllegalArgumentException: Multiple services with name 'com.atlassian.streams.internal.ActivityProviderConnectionMonitorImpl:activityProviderMonitor' exist.
	at com.atlassian.jira.service.OfBizServiceConfigStore.getServiceConfigForName(OfBizServiceConfigStore.java:134)
	at com.atlassian.jira.service.DefaultServiceManager.getServiceWithName(DefaultServiceManager.java:162)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

Cause

There are duplicated Services that are present in your JIRA instance. In this example:

  1. com.atlassian.jira.plugin.ext.bamboo.service.PlanStatusUpdateServiceImpl:job
  2. com.atlassian.streams.internal.ActivityProviderConnectionMonitorImpl:activityProviderMonitor

Resolution

Perform the following steps below:

    • Navigate to Administration >> System >> Services
    • Remove all services with name com.atlassian.jira.plugin.ext.bamboo.service.PlanStatusUpdateServiceImpl:job and com.atlassian.streams.internal.ActivityProviderConnectionMonitorImpl:activityProviderMonitor 
      OR 
      If there are duplicates, remove one (or more) and ensure that there is at least one
    • Restart JIRA again

Last modified on Mar 30, 2016

Was this helpful?

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