Arne M. Størksen created CAMEL-7033:
---------------------------------------
Summary: camel-quartz2 - When clustering, triggers may be left in
a paused and unrecoverable state
Key: CAMEL-7033
URL: https://issues.apache.org/jira/browse/CAMEL-7033
Project: Camel
Issue Type: Bug
Components: camel-quartz2
Environment: camel-quartz2, 2.13-SNAPSHOT clustered on Oracle database
Reporter: Arne M. Størksen
The reason seems to be that onConsumerStop() is called when camel is shut down.
This method does not take clustering into account and pauses the trigger in the
quartz database, leaving it in a state that is unrecoverable from camel. I was
able to prevent this by removing pauseTrigger() from onConsumerStop(), but I'm
not sure what the correct procedure should be. It seems to me like
onConsumerStop() and doStop() has some overlap.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
