Details
-
Bug
-
Resolution: Fixed
-
Medium
-
3.13
-
3.13
-
Description
It is possible for the following exception to occur while starting Jira.
2008-10-27 11:34:55,158 JiraQuartzScheduler_Worker-3 ERROR [org.quartz.core.JobRunShell] Job DEFAULT.ServicesJob threw an unhandled Exception: java.util.ConcurrentModificationException at java.util.HashMap$HashIterator.nextEntry(HashMap.java:793) at java.util.HashMap$ValueIterator.next(HashMap.java:822) at java.util.Collections$UnmodifiableCollection$1.next(Collections.java:1010) at com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:35) at org.quartz.core.JobRunShell.run(JobRunShell.java:191) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:516) 2008-10-27 11:34:55,158 JiraQuartzScheduler_Worker-3 ERROR [org.quartz.core.ErrorLogger] Job (DEFAULT.ServicesJob threw an exception. org.quartz.SchedulerException: Job threw an unhandled exception. [See nested exception: java.util.ConcurrentModificationException] at org.quartz.core.JobRunShell.run(JobRunShell.java:202) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:516) * Nested Exception (Underlying Cause) --------------- java.util.ConcurrentModificationException at java.util.HashMap$HashIterator.nextEntry(HashMap.java:793) at java.util.HashMap$ValueIterator.next(HashMap.java:822) at java.util.Collections$UnmodifiableCollection$1.next(Collections.java:1010) at com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:35) at org.quartz.core.JobRunShell.run(JobRunShell.java:191) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:516)
This occured when there was some services in Jira that could not be loaded. There where also some services that could not be started. Not sure if this has anything to do with the problem.
I am not sure if this stops the services from running in the future (i.e. the service runner dies), but this is something that we should check and possibly harden against.