Hello All,
After recently patching a lucee install from 5.3.9.141 to 6.0.3.1 I noticed my testing system was not removing scheduled tasks properly. I am creating schedule tasks in code, then deleting in code and watching my access logs continue to show calls to the task.
The schedule task is no longer listed in the admin interface but continues running in the background until Lucee is restarted.
After rolling back and working through the patches I have noticed that the issue starts after 6.0.0.585. The system deletes scheduled tasks cleanly in 6.0.0.585 but once I patch to 6.0.1.83, scheduled tasks seem to keep running in memory until a Lucee restart.
Has anyone else experienced this issue? It may be related to this post but it seems a little different.
OS: Windows 11 Java Version: 11.0.11 (AdoptOpenJDK) 64bit Tomcat Version: Apache Tomcat/9.0.4 Lucee Version: 6.0.0.585 works, patch to 6.0.1.83 and the tasks continue running
this is my first post; therefore, not sure if i am to add it to this similar thread or start a new request – so please forgive me/guide me where to post if it should not be here. my issue is: running lucee 6.2.2.91 on latest iis in single user mode. I deleted all scheduled tasks from the lucee admin console and restarted the entire server. Currently, no tasks appear in admin console or in my CFConfig.json – HOWEVER - there are still phantom tasks running everyday!!! (And, for what it is worth, i see various “exampletaskname$cf.class” files in the C:\lucee\tomcat\lucee-server\context\cfclasses\CFG__iissites_exampledomainname2278\examplehostname\schedtasks folders.) Any ideas how stop these phantom tasks from executing in 6.2.2.91 (especially because, Jira leads me to believe that the problem i’m having may have been fixed as of 6.1.2.20+ releases. Or, is this a completely different issue entirely?) thank you!!!
I’d recommend you prove that the template being run is called as a phantom, by having it log or dump the cgi scope vars like remote_addr (the ip that made the request) and user_agent (the self-identifying indication of the browser or client, like Lucee or something else, making the request).
You may be surprised if the values are not what you’d expect. I mean you may come to realize that the request is not coming in due to a scheduled task running on the instance where you feel you’d deleted it.
never even considered it could be coming from elsewhere. when you mentioned remote_addr, went straight to the iis logs and, lo and behold, it was being posted from a testing VM on the same server! thank you!
Great to hear, and thanks for the update. Yep, just one of those lessons we tend to learn only in the school of hard knocks…or from seeing others do that.
