Pregunta

I have a Grails application with the following grails-app/conf/QuartzConfig.groovy:

quartz {
    autoStartup = true
    jdbcStore = false
    waitForJobsToCompleteOnShutdown = false
    exposeSchedulerInRepository = false
    interruptJobsOnShutdown = true

    props {
        scheduler.skipUpdateCheck = true
    }
}

However every time I shut down Tomcat, there will be a process left hanging which I'll have to kill. According to the above config file this should not happen. Is there another property I should be using to achieve this?

Furthermore upon Tomcat startup I see 10 lines of (for the 10 Quartz threads):

SEVERE: The web application [/test] appears to have started a thread named [DefaultQuartzScheduler_Worker-5] but has failed to stop it. This is very likely to create a memory leak.

The above also doesn't change with the properties in the config file, which is seemingly related to the hanging process. Any help would be greatly appreciated.

¿Fue útil?

Solución

Use the latest version of the Quartz plugin. We released it a day ago.

Licenciado bajo: CC-BY-SA con atribución
No afiliado a StackOverflow
scroll top