camel-quartz component dosen't support start with a new camelContext after the
scheduler is shutdown
-----------------------------------------------------------------------------------------------------
Key: CAMEL-2810
URL: https://issues.apache.org/activemq/browse/CAMEL-2810
Project: Apache Camel
Issue Type: Bug
Reporter: Willem Jiang
Assignee: Willem Jiang
Fix For: 2.4.0
You will get the below error if you want to create a new camel context after
the scheduler is shutdown.
{code}
org.quartz.SchedulerException: The Scheduler has been shutdown.
at
org.quartz.core.QuartzScheduler.validateState(QuartzScheduler.java:637)
at org.quartz.core.QuartzScheduler.scheduleJob(QuartzScheduler.java:688)
at org.quartz.impl.StdScheduler.scheduleJob(StdScheduler.java:265)
at
org.apache.camel.component.quartz.QuartzComponent.addJob(QuartzComponent.java:150)
at
org.apache.camel.component.quartz.QuartzEndpoint.addTrigger(QuartzEndpoint.java:77)
at
org.apache.camel.component.quartz.QuartzEndpoint.consumerStarted(QuartzEndpoint.java:190)
at
org.apache.camel.component.quartz.QuartzConsumer.doStart(QuartzConsumer.java:39)
at org.apache.camel.impl.ServiceSupport.start(ServiceSupport.java:56)
at
org.apache.camel.util.ServiceHelper.startService(ServiceHelper.java:53)
at
org.apache.camel.impl.DefaultCamelContext.start(DefaultCamelContext.java:1015)
at
org.apache.camel.component.quartz.QuartzTwoCamelContextTest.setUp(QuartzTwoCamelContextTest.java:47)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:592)
at
org.junit.internal.runners.MethodRoadie.runBefores(MethodRoadie.java:122)
at
org.junit.internal.runners.MethodRoadie.runBeforesThenTestThenAfters(MethodRoadie.java:86)
at org.junit.internal.runners.MethodRoadie.runTest(MethodRoadie.java:77)
at org.junit.internal.runners.MethodRoadie.run(MethodRoadie.java:42)
at
org.junit.internal.runners.JUnit4ClassRunner.invokeTestMethod(JUnit4ClassRunner.java:88)
at
org.junit.internal.runners.JUnit4ClassRunner.runMethods(JUnit4ClassRunner.java:51)
at
org.junit.internal.runners.JUnit4ClassRunner$1.run(JUnit4ClassRunner.java:44)
at
org.junit.internal.runners.ClassRoadie.runUnprotected(ClassRoadie.java:27)
at
org.junit.internal.runners.ClassRoadie.runProtected(ClassRoadie.java:37)
at
org.junit.internal.runners.JUnit4ClassRunner.run(JUnit4ClassRunner.java:42)
at
org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:46)
at
org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
{code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
