I have two separate mule (3.x.0) applications, each with a quartz inbound endpoint defined (see samples attached).
When the second application is deployed, the timer in the first application produces only the following:
INFO 2011-01-13 17:46:00,018 [QuartzScheduler_Worker-5] org.quartz.core.JobRunShell: Job mule.quartz://job1 threw a JobExecutionException:
org.quartz.JobExecutionException: No receiver with key "connector.quartz.0" could be found in connector "quartz://job1"
at org.mule.transport.quartz.jobs.EventGeneratorJob.execute(EventGeneratorJob.java:81)
at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:529)
... and the remainder of the application doesn't execute.
(If I explicitly declare a quartz connector, then its name is used as the key, but the message is the same).
Any suggestions as to how I can get the two applications running together?
This happens with Mule 3.0.0 and 3.1.0.
Many thanks in advance.
<quartz:connector name="quartz.connector" scheduler-ref="scheduler1"/>
<spring:bean id="scheduler1" factory-bean="scheduler.factory1" factory-method="getScheduler"/>
<spring:bean id="scheduler.factory1" class="org.quartz.impl.StdSchedulerFactory">
<spring:constructor-arg>
<spring:props>
<spring:prop key="org.quartz.scheduler.instanceName">scheduler1</spring:prop>
<spring:prop key="org.quartz.threadPool.class">org.quartz.simpl.SimpleThreadPool</spring:prop>
<spring:prop key="org.quartz.threadPool.threadCount">3</spring:prop>
<spring:prop key="org.quartz.scheduler.rmi.export">false</spring:prop>
<spring:prop key="org.quartz.scheduler.rmi.proxy">false</spring:prop>
<spring:prop key="org.quartz.jobStore.class">org.quartz.simpl.RAMJobStore</spring:prop>
</spring:props>
</spring:constructor-arg>
</spring:bean>
Is there a cleaner solution using the inbuilt scheduler?
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
entered it here just in case the nut behind the wheel was at fault.
Here's the Jira ref:
http://www.mulesoft.org/jira/browse/MULE-5337
Thanks.