Latest posts for the topic "JVM ends immediately with running scheduler while expected to wait for its shutdown"

JVM ends immediately with running scheduler while expected to wait for its shutdown

szpak — GMT

Hi, I have read in the documentation that:

Once you obtain a scheduler using StdSchedulerFactory.getDefaultScheduler(), your application will not terminate until you call scheduler.shutdown(), because there will be active threads.

I have found a blog entry about ShutdownHookPlugin and wanted to write some (self) integration test to prove the new configuration works. The strange thing is that it seems in the default configuration (no custom quartz.properties) JVM is shutdown anyway. With following code I would expect to have a timeout, but it finishes nicely: Code:

@Test(timeout = 500L)
public void runningQuartzSchedulerShouldNotBlockJvmShutdown() throws SchedulerException {
    Scheduler scheduler = StdSchedulerFactory.getDefaultScheduler();
    scheduler.start();
    //should stop test immediately
}

Do you think it could be an "issue" with JUnit runner which ignores/kills other threads? How can I test it? Regards Marcin

Re:JVM ends immediately with running scheduler while expected to wait for its shutdown

szpak — GMT

Do you think it is just an outdated text in a documentation and in a current version there is no issue with hanging active threads?

Re:JVM ends immediately with running scheduler while expected to wait for its shutdown

hhuynh — GMT

Maybe you'll need to add some trigger and jobs to see those extra threads? and allows at least one job triggered to see them in action (adding some sleep())

Re:JVM ends immediately with running scheduler while expected to wait for its shutdown

jhouse — GMT

No, I think the test framework must be doing something to kill it. Once you call start() there are definitely threads running. And unless you've set the quartz config properties that cause them to be daemon threads, they should cause the JVM to stay up until they are terminated.