You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "nizar.ben.mansour (Jira)" <ji...@apache.org> on 2020/06/25 13:55:00 UTC
[jira] [Closed] (CAMEL-15243) Old misfire is triggered in a Karaf
environement
[ https://issues.apache.org/jira/browse/CAMEL-15243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
nizar.ben.mansour closed CAMEL-15243.
-------------------------------------
> Old misfire is triggered in a Karaf environement
> ------------------------------------------------
>
> Key: CAMEL-15243
> URL: https://issues.apache.org/jira/browse/CAMEL-15243
> Project: Camel
> Issue Type: Bug
> Components: camel-quartz2
> Affects Versions: 2.16.0
> Reporter: nizar.ben.mansour
> Priority: Minor
> Fix For: 2.23.4
>
> Attachments: image-2020-06-25-12-07-34-075.png, image-2020-06-25-15-53-30-855.png
>
>
> I'm having a karaf application (4.0.2)in which i have multiple blueprint projects.Each of them have multiple quartz2 job.
> Each time i install the application,Quartz add new rows in the qrtz_triggers table.
> The sched_name takes the name of the bundle and append a counter.
>
> !image-2020-06-25-12-07-34-075.png!
> Each time i install a new version of my application it creates a new rows with the same mecanism(bundleName+Counter).
> Now suppose i have a misfire say for example for MyBundle-23.After many installation there is a risk that the new created row in qrtz_triggers will be same as MyBundle-23 and thus triggering an old misfire.
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)