An error occurred while trying to run service with ID '10200'. This method is not supported in an UnloadableJiraServiceContainer

Jeff Lane August 3, 2015

Hello All,

  I have JIRA v6.4.8 running on Debian Jessie. And to following error printing about every minute in atlassian-jira.log:

2015-08-04 10:46:53,548 atlassian-scheduler-quartz1.clustered_Worker-4 ERROR anonymous    Mercurial add-on Indexer [atlassian.jira.service.ServiceRunner] An error occurred while trying to run service with ID '10200'. This method is not supported in an UnloadableJiraServiceContainer
java.lang.UnsupportedOperationException: This method is not supported in an UnloadableJiraServiceContainer
 at com.atlassian.jira.service.UnloadableJiraServiceContainer.setLastRun(UnloadableJiraServiceContainer.java:107)
 at com.atlassian.jira.service.ServiceRunner.runService(ServiceRunner.java:91)
 at com.atlassian.jira.service.ServiceRunner.runServiceId(ServiceRunner.java:54)
 at com.atlassian.jira.service.ServiceRunner.runJob(ServiceRunner.java:37)
 at com.atlassian.scheduler.core.JobLauncher.runJob(JobLauncher.java:136)
 at com.atlassian.scheduler.core.JobLauncher.launchAndBuildResponse(JobLauncher.java:101)
 at com.atlassian.scheduler.core.JobLauncher.launch(JobLauncher.java:80)
 at com.atlassian.scheduler.quartz1.Quartz1Job.execute(Quartz1Job.java:32)
 at org.quartz.core.JobRunShell.run(JobRunShell.java:223)

 

The Information from the Admin>Scheduler Details Page would seem to correlate to the error:

 31

com.atlassian.jira.service.DefaultServiceManager

4 jobscron, intervalShow less
 #1 com.atlassian.jira.service.JiraService:10000

TypeRunnableParameters{com.atlassian.jira.service.ServiceManager:serviceId=10000}Run modelocallySchedule0 * * * * ?Last RunTue Aug 04 10:55:00 CEST 2015Last run duration8 millisecondsNext RunTue Aug 04 10:56:00 CEST 2015Message

 #2 com.atlassian.jira.service.JiraService:10001

TypeRunnableParameters{com.atlassian.jira.service.ServiceManager:serviceId=10001}Run modeonce per clusterSchedule0 0 1/12 * * ?Last RunTue Aug 04 01:00:00 CEST 2015Last run duration6 secondsNext RunTue Aug 04 13:00:00 CEST 2015Message

 #3 com.atlassian.jira.service.JiraService:10002

TypeRunnableParameters{com.atlassian.jira.service.ServiceManager:serviceId=10002}Run modeonce per clusterSchedule0 0 1 * * ?Last RunTue Aug 04 01:00:00 CEST 2015Last run duration138 millisecondsNext RunWed Aug 05 01:00:00 CEST 2015Message

 #4 com.atlassian.jira.service.JiraService:10200

TypeRunnableParameters{com.atlassian.jira.service.ServiceManager:serviceId=10200}Run modeonce per clusterSchedule1 minuteLast RunTue Aug 04 10:55:53 CEST 2015Last run duration3 millisecondsNext RunTue Aug 04 10:56:53 CEST 2015MessageUnsupportedOperationException: This method is not supported in an UnloadableJiraServiceContainer

How can I solve this?

 

Thanks!

 

 

1 answer

1 accepted

2 votes
Answer accepted
crf
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
August 4, 2015

The "Scheduler Details" page is the wrong place to look for specifics about a JIRA service, as it only knows about the scheduler entry for it, and all that this knows is the service's ID.  Go to the "Services" administration page, instead.

What's going to turn out to be the case is that you have a Service defined that could not be instantiated, probably because the code that provided that service does not exist anymore.  This could happen if we removed such a service from JIRA and forgot to delete corresponding services, but it is more likely that this came from a custom plugin of some kind that you no longer have installed.  You should be able to remove the offending service using that administration page, or tell from the information there exactly what it is supposed to be.

Jeff Lane August 4, 2015

That solved it. Many Thanks!

crf
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
August 4, 2015

Happy to help!

jirajester December 19, 2017

Thanks! Worked here

Suggest an answer

Log in or Sign up to answer