[
https://issues.apache.org/jira/browse/CAMEL-6686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13773210#comment-13773210
]
Babak Vahdat commented on CAMEL-6686:
-------------------------------------
Raised CAMEL-6773 to get this fixed for {{camel-quartz2}} as well. As the
Quartz API 1.x is different than it's 2.x counterpart the applied fix here
should be first adapted to the Quartz 2.x API.
Would you please setup a new JIRA component for {{camel-quartz2}}?
> camel-quartz - scheduled route policy - Should support clustered jobs
> ---------------------------------------------------------------------
>
> Key: CAMEL-6686
> URL: https://issues.apache.org/jira/browse/CAMEL-6686
> Project: Camel
> Issue Type: Improvement
> Components: camel-quartz
> Affects Versions: 2.10.2
> Reporter: Claus Ibsen
> Assignee: Babak Vahdat
> Fix For: 2.11.3, 2.12.2, 2.13.0
>
>
> See nabble
> http://camel.465427.n5.nabble.com/Cluster-in-camel-using-Quartz-ObjectAlreadyExistsException-tp5737167.html
> When the 2nd Camel app startup it tries also to schedule the job, but the job
> is already registered in the quartz scheduler, and you get an exception.
> The route policy should deal with that.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
