• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
0

Scheduled Tasks Deleted After CF 11 - Update 16

Engaged ,
Feb 15, 2019 Feb 15, 2019

Copy link to clipboard

Copied

We installed the CF11 Update 16 today and it deleted all our scheduled tasks.  Unfortunately, we didn't notice until we installed on 3 other servers.  All tasks gone.

We tried to restore with a recent CF Archive from the Admin.  Did not restore tasks.

It looks like the system did create a backup of the old tasks file: neo-chron.bak.

However, when we rename this back to neo-chron.xml and restart the server, CF replaces it with a blank file and makes a backup again.

Any help or ideas?  Looks like we need to crawl through the XML and re-enter tasks by hand?

Logs look to show Null Point Exception:

"Error","localhost-startStop-1","02/15/19","14:14:25",,""

java.lang.NullPointerException

    at coldfusion.runtime.Cast._boolean(Cast.java:323)

    at coldfusion.scheduling.ScheduleTagData.setAttributes(ScheduleTagData.java:1309)

    at coldfusion.scheduling.ScheduleTagData.<init>(ScheduleTagData.java:349)

    at coldfusion.scheduling.CronServiceImpl.updateTasks(CronServiceImpl.java:291)

    at coldfusion.scheduling.CronServiceImpl.load(CronServiceImpl.java:246)

    at coldfusion.server.ServiceBase.start(ServiceBase.java:59)

    at coldfusion.scheduling.CronServiceImpl.start(CronServiceImpl.java:186)

    at coldfusion.server.CFService.setupCron(CFService.java:328)

    at coldfusion.server.CFService.start(CFService.java:599)

    at coldfusion.server.j2ee.CFStartUpServlet.startCFService(CFStartUpServlet.java:553)

    at coldfusion.server.j2ee.CFStartUpServlet.init(CFStartUpServlet.java:505)

    at javax.servlet.GenericServlet.init(GenericServlet.java:158)

    at coldfusion.bootstrap.ClassloaderHelper.initServletClass(ClassloaderHelper.java:121)

    at coldfusion.bootstrap.BootstrapServlet.init(BootstrapServlet.java:59)

    at org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1230)

    at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1174)

    at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1066)

    at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5409)

    at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5707)

    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:145)

    at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1702)

    at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1692)

    at java.util.concurrent.FutureTask.run(Unknown Source)

    at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)

    at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

    at java.lang.Thread.run(Unknown Source)

Views

1.1K

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Engaged ,
Feb 15, 2019 Feb 15, 2019

Copy link to clipboard

Copied

We uninstalled Update 16 and re-inserted the backup of the neo-cron.xml file.  Scheduled tasks are back.

What's the deal, Adobe?

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Feb 15, 2019 Feb 15, 2019

Copy link to clipboard

Copied

Hi,

We encountered this problem with this update and it is deleting the task. You have to take the back up of neo-cron.xml and replace it after the update. We have listed this issue as Known issue because we encountered this after the release.

https://coldfusion.adobe.com/2019/02/coldfusion-2018-release-update-2-coldfusion-2016-release-update...

We will come up with a solution soon and we will share more details.

Thanks,

Priyank

Thanks,
Priyank Shrivastava

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Engaged ,
Feb 15, 2019 Feb 15, 2019

Copy link to clipboard

Copied

Priyank,

Thanks for the reply but, no, we can't use the backup of neo-cron.  When we try to apply that, CF just replaces it with a blank XML file again.

Only solution was to uninstall Update 16

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Feb 15, 2019 Feb 15, 2019

Copy link to clipboard

Copied

LATEST

Hi,

I understand this is frustrating. But there is a workaround, I copied Charlie's comment from the blog and just putting it here.

"Workaround – Manually edit a backup copy of the neo-crons.xml adding <var name=’clustered’><boolean value=’false’/></var> to each job and then replace the wiped out copy with this one and restart the services. If it gets wiped out again you missed a job. You can also rebuild all of your jobs by hand too."

Thanks,

Priyank

Thanks,
Priyank Shrivastava

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Resources
Documentation