Fixed
Details
Details
Assignee
Michael Offner
Michael OffnerReporter
Adam Stetzer
Adam StetzerPriority
Labels
New Issue warning screen
Before you create a new Issue, please post to the mailing list first https://dev.lucee.org
Once the issue has been verified, one of the Lucee team will ask you to file an issue
Sprint
None
Affects versions
Created 23 August 2021 at 11:47
Updated 29 December 2021 at 15:47
Resolved 15 October 2021 at 20:55
We built to new job servers (2 completely independent Lucee servers with staggered timing for scheduled tasks) from scratch, using the 5.3.8.193 installer - and then upgraded to 5.3.8.201 in ADMIN…
We then copied our Scheduler.xml file from the old from 5.2.8.50 Lucee server to the new 5.3.8.201 servers. After reboots of the new servers - Seemed like jobs were running great (about 25 each minute each / staggered appropriately).
Noticed the next morning morning that SOME DAILY jobs did not fire at all (on either of two completely independent boxes).
We have Box 1 firing at 03:15 EST - no log file. The output of the job (which it to create a bunch of emails) did not happen.
We have Box 2 firing this same job at 03:30 EST (locally, each have copy of Prod code) - No job on this box either…
Yet - Another job that is scheduled for 5:20 DID run fine…???
We failed one box back to 5.2.8.50 so that we can get up-and-running…
We’ve kept the other one on 5.3.8.201 to try and replicate the behavior. The issue IS replicating.
When I hit “EXECUTE” - the job runs fine. When it is on a DAILY schedule - it will not run at the appropriate time. Ran this test 4 times.
When I manually rebuild the task, with the exact same settings (Daily, logging, time, etc) - it fires on the DAILY schedule just fine. So, this is isolated to migrated Scheduler.xml files.
I thought the Scheduler.xml was supposed to be completely portable between versions???
I’m noticing a new feature in Scheduled Tasks called “Run Exclusive” - is this where the trouble is coming from? Since this XML was migrated, and that feature didn’t exist before, I could see there being an issue. I would have hoped that because the feature is NOT selected, the Daily Scheduled Tasks would still run… And why are my other Scheduled Tasks running? Confusing…
Here is a task from Scheduler.xml that is NOT firing on the new 5.3.8.201 box:
<task autoDelete="false" file="/var/www/html/semseo/logs/act_Task_Auto_Script_Queue_Build.html" hidden="false" interval="daily" name="act_Task_Auto_Script_Queue_Build" paused="false" port="80" proxyHost="" proxyPassword="" proxyPort="0" proxyUser="" publish="true" readonly="false" resolveUrl="false" startDate="{d '2020-12-22'}" startTime="{t '03:15:00'}" timeout="300000" url="http://10.0.1.74:80/act_Task_Auto_Script_Queue_Build.cfm"/>