-
Bug
-
Resolution: Done
-
Major
-
jboss-fuse-6.2
-
None
-
%
Setting a camel-quartz2 bundle in a profile in Fabric and getting these strange INFO messages from the logs.
If the route consumes from
<from uri="master:poc_parking_main:quartz2://pocparking?cron=0/5+0/1+*+1/1+*+?+*"/>
it does not trigger a new message but only logs:
2015-05-06 11:11:20,896 | INFO | ZooKeeperGroup-0 | QuartzEndpoint | component.quartz2.QuartzEndpoint 249 | 264 - org.apache.camel.camel-quartz2 - 2.12.0.redhat-611431 | Job Camel_quartz2-issue.pocparking (triggerType=CronTriggerImpl, jobClass=CamelJob) is scheduled. Next fire date is Wed May 06 11:11:25 CEST 2015 2015-05-06 11:11:25,007 | INFO | 2-issue_Worker-1 | QuartzEndpoint | component.quartz2.QuartzEndpoint 249 | 264 - org.apache.camel.camel-quartz2 - 2.12.0.redhat-611431 | Job Camel_quartz2-issue.pocparking (triggerType=CronTriggerImpl, jobClass=CamelJob) is scheduled. Next fire date is null 2015-05-06 11:11:30,006 | INFO | 2-issue_Worker-2 | QuartzEndpoint | component.quartz2.QuartzEndpoint 249 | 264 - org.apache.camel.camel-quartz2 - 2.12.0.redhat-611431 | Job Camel_quartz2-issue.pocparking (triggerType=CronTriggerImpl, jobClass=CamelJob) is scheduled. Next fire date is null
If however I remove the master component from the route as in
<from uri="quartz2://pocparking?cron=0/5+0/1+*+1/1+*+?+*"/>
it correctly triggers a new msg every 5 secs.
2015-05-06 11:10:45,008 | INFO | 2-issue_Worker-1 | quartz scheduler | rg.apache.camel.util.CamelLogger 176 | 142 - org.apache.camel.camel-core - 2.12.0.redhat-611431 | MESSAGE 2015-05-06 11:10:50,005 | INFO | 2-issue_Worker-2 | quartz scheduler | rg.apache.camel.util.CamelLogger 176 | 142 - org.apache.camel.camel-core - 2.12.0.redhat-611431 | MESSAGE
- relates to
-
MR-916 FUSE "master" component conflicts with camel-quartz2
- Resolved