[ https://jira.jboss.org/jira/browse/JBESB-2146?page=com.atlassian.jira.plu... ] Tom Fennelly commented on JBESB-2146: ------------------------------------- Actually... if you create 2 crons with different expressions, they both fire. When they're the same, only the first trigger seems to fire. -- 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

[ https://jira.jboss.org/jira/browse/JBESB-2146?page=com.atlassian.jira.plu... ] Len DiMaggio commented on JBESB-2146: ------------------------------------- FYI - where this discussion started... http://www.jboss.com/index.html?module=bb&op=viewtopic&t=144556 -- 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

[ 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. -- 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

[ https://jira.jboss.org/jira/browse/JBESB-2146?page=com.atlassian.jira.plu... ] Kevin Conner commented on JBESB-2146: ------------------------------------- Ignore my last, the helloworld_ftp_action QS, on which that is based, does explicitly use a cron schedule. -- 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

[ https://jira.jboss.org/jira/browse/JBESB-2146?page=com.atlassian.jira.plu... ] Kevin Conner closed JBESB-2146. ------------------------------- Resolution: Done Fixed in revision 23680. -- 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