[
https://jira.jboss.org/jira/browse/JBESB-2146?page=com.atlassian.jira.plu...
]
Kevin Conner commented on JBESB-2146:
-------------------------------------
The issue is that the subsequent cron trigger has misfired and the cron trigger is
currently set to ignore the misfires.
The initial reason for choosing this was to allow stop/start of Cron jobs to resume at the
next trigger rather then firing immediately, but I had not foreseen this issue. It is
only evident because I had reduced the misfire threshold.
I will change the misfire instruction to use MISFIRE_INSTRUCTION_FIRE_ONCE_NOW but, in the
meantime, a workaround is to increase the misfire threshold as follows.
<schedule-provider name="schedule">
<property name="org.quartz.jobStore.misfireThreshold"
value="1000"/>
<cron-schedule scheduleid="schedule1" cronExpression="0/2 *
* * * ?"/>
<cron-schedule scheduleid="schedule2" cronExpression="0/2 *
* * * ?"/>
</schedule-provider>
Be aware that the issue is still theoretically possible depending on the load of the
system and the setting which is chosen for the misfire threshold, the real fix is the
change to the misfire instruction.
Scheduling: Multiple cron schedules not supported
-------------------------------------------------
Key: JBESB-2146
URL:
https://jira.jboss.org/jira/browse/JBESB-2146
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.4 CP1
Reporter: Tom Fennelly
Assignee: Kevin Conner
Fix For: 4.4 CP2
If you define multiple cron schedules, or just one cron schedule with associated multiple
listeners/jobs.... only the first job gets executed. I stepped into the code and the jobs
are getting registered, started etc.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira