camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Willem Jiang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-7033) camel-quartz2 - When clustering, triggers may be left in a paused and unrecoverable state
Date Thu, 03 Apr 2014 12:04:15 GMT

    [ https://issues.apache.org/jira/browse/CAMEL-7033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13958748#comment-13958748
] 

Willem Jiang commented on CAMEL-7033:
-------------------------------------

Applied the patch into camel master, camel-2.13.x and camel-2.12.x with thanks to Arne.
I also remove the jobAdded.set(false); which makes other unit test failed.


> 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
>            Assignee: Willem Jiang
>         Attachments: 0001-Handling-clustered-scheduler-in-pauseTrigger.patch
>
>
> 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.2#6252)

Mime
View raw message