Exception after restarting lucee services: javax.servlet.ServletException: Attribute "startTime" was

[Dan Baughman]

Lucee reports this error after I restarted lucee, it seems to come from tomcat.   Has anyone see an error like this before?

type Exception report

message Attribute "startTime" was already specified for element "task".

description The server encountered an internal error that prevented it from fulfilling this request.

exception

javax.servlet.ServletException: Attribute "startTime" was already specified for element "task".
	org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
	lucee.runtime.schedule.StorageUtil.loadDocument(StorageUtil.java:93)
	lucee.runtime.schedule.SchedulerImpl.<init>(SchedulerImpl.java:73)
	lucee.runtime.config.ConfigImpl.setScheduler(ConfigImpl.java:1522)
	lucee.runtime.config.ConfigWebFactory.loadScheduler(ConfigWebFactory.java:3868)
	lucee.runtime.config.ConfigWebFactory.load(ConfigWebFactory.java:396)
	lucee.runtime.config.ConfigWebFactory.newInstance(ConfigWebFactory.java:270)
	lucee.runtime.engine.CFMLEngineImpl.loadJSPFactory(CFMLEngineImpl.java:227)
	lucee.runtime.engine.CFMLEngineImpl.addServletConfig(CFMLEngineImpl.java:181)
	lucee.loader.engine.CFMLEngineFactory.getInstance(CFMLEngineFactory.java:164)
	lucee.loader.servlet.CFMLServlet.init(CFMLServlet.java:41)
	org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:474)
	org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:79)
	org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:349)
	org.apache.coyote.ajp.AjpProcessor.service(AjpProcessor.java:478)
	org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66)
	org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:798)
	org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1434)
	org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
	java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
	java.lang.Thread.run(Thread.java:745)

[Dan Baughman]

Nevermind.... it was a corrupt scheduler.xml in the web instance. It seems cfschedule can create invalid XML sometimes.