Justin Tilson - [04/Jan/05 02:14 PM ] org.quartz.plugin.jobInitializer.class = org.quartz.plugins.xml.JobInitializationPlugin org.quartz.plugin.jobInitializer.fileName = jobs.xml org.quartz.plugin.jobInitializer.overWriteExistingJobs = true org.quartz.plugin.jobInitializer.failOnFileNotFound = true org.quartz.plugin.jobInitializer.validating = false org.quartz.plugin.jobInitializer.validatingSchema = false Adding the following line to quartz.properties causes log.warn("File '"+fileName+"' does not exist.") to execute. org.quartz.plugin.jobInitializer.scanInterval = 30 The scan interval fails because it uses the same fileName as the initialization process (which looks on the class path - see QUARTZ-105). The check here requires an absolute path. If an abolute path is specified in quartz.properties the initialization fails. Code below is from FileScanJob.execute(JobExecutionContext context) File file = new File(fileName); if(!file.exists()) {     log.warn("File '"+fileName+"' does not exist.");     return; } I would make both methods work the same, either on the class path or using an absolute path or both. I'm using Tomcat 5.0.25 on Win2K.