[
https://issues.apache.org/jira/browse/CAMEL-15243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17144946#comment-17144946
]
nizar.ben.mansour commented on CAMEL-15243:
-------------------------------------------
Hello
I can confirm that the bug is fixed on the 2.23.4 version.In fact the algorithm
have been changed in setting the sched_name .
The old algorithm was using an antomicInteger NEXT_COUNTER to be appened to the
bundle name.
For the new one,each new installation of the bundle it delete the previous
qrtz_triggers rows and create new one.
Besides,the schedularName (sched_name ) is now a concatination of the
bundleName+ContextID (see attached picture).
!image-2020-06-25-15-53-30-855.png!
> 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
> 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)
