Concurrent access in ESB Quartz Scheduler initialization -------------------------------------------------------- Key: JBESB-2459 URL: https://jira.jboss.org/jira/browse/JBESB-2459 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.4 CP2 Reporter: Jiri Pechanec Assignee: Kevin Conner Attachments: exs.log.gz I placed all Seam examples to deploy dir and started the server, I got the following exception during the startup 2009-03-09 11:34:20,945 INFO [org.quartz.core.QuartzScheduler] Quartz Scheduler v.1.5.2 created. 2009-03-09 11:34:20,945 INFO [org.quartz.simpl.RAMJobStore] RAMJobStore initialized. 2009-03-09 11:34:20,945 INFO [org.quartz.impl.StdSchedulerFactory] Quartz scheduler 'ESBScheduler:jbossesb.esb' initialized from an externally provided properties instance. 2009-03-09 11:34:20,945 INFO [org.quartz.impl.StdSchedulerFactory] Quartz scheduler version: 1.5.2 2009-03-09 11:34:20,945 INFO [org.quartz.core.QuartzScheduler] Scheduler ESBScheduler:jbossesb.esb_$_NON_CLUSTERED started. 2009-03-09 11:34:21,087 INFO [org.quartz.core.JobRunShell] Job ESBScheduler.ESBJob1 threw a JobExecutionException: org.quartz.JobExecutionException: Unexpected exception on ESBJob1 at org.jboss.soa.esb.schedule.SchedulerJob$ESBScheduledJob.execute(SchedulerJob.java:299) at org.quartz.core.JobRunShell.run(JobRunShell.java:203) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520) Caused by: java.util.ConcurrentModificationException at java.util.TreeMap$PrivateEntryIterator.nextEntry(TreeMap.java:1031) at java.util.TreeMap$KeyIterator.next(TreeMap.java:1058) at org.jboss.mx.loading.LoadMgr3.beginLoadTask(LoadMgr3.java:235) at org.jboss.mx.loading.RepositoryClassLoader.loadClassImpl(RepositoryClassLoader.java:514) at org.jboss.mx.loading.RepositoryClassLoader.loadClass(RepositoryClassLoader.java:408) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) at org.jboss.internal.soa.esb.message.format.xml.MessageImpl.<init>(MessageImpl.java:78) at org.jboss.internal.soa.esb.message.format.xml.XMLMessagePlugin.getMessage(XMLMessagePlugin.java:46) at org.jboss.internal.soa.esb.message.format.MessageFactoryImpl.getMessage(MessageFactoryImpl.java:109) at org.jboss.soa.esb.schedule.RedeliverEventMessageComposer.composeMessage(RedeliverEventMessageComposer.java:25) at org.jboss.soa.esb.listeners.ScheduleListener.onSchedule(ScheduleListener.java:118) at org.jboss.soa.esb.listeners.lifecycle.AbstractScheduledManagedLifecycle$1.onSchedule(AbstractScheduledManagedLifecycle.java:68) at org.jboss.soa.esb.schedule.SchedulerJob$ESBScheduledJob.execute(SchedulerJob.java:289) ... 2 more Unfortunately it is very very very rare to generate it twice. Full log is attached -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira