The task is not executed due to a dead issue of quartz 1.6.1.

A concurrency problem occurs when you use quartz 1.6.1.

Because multiple jobs are almost concurrent at the same time, sometimes the quartz is in the dead state and no longer executes the task.

Specific bug visible: http://jira.opensymphony.com/browse/QUARTZ-707? Page = com. Atlassian. Jira. plugin. system. issuetabpanels % 3acomment-tabpanel

Corresponds to SRC: http://svn.terracotta.org/fisheye/browse/Quartz/trunk/src/java/org/quartz/core/QuartzSchedulerThread.java? R = 865.

This problem may occur when a large number of concurrent tasks and the execution time is not fixed, which may be equal to or greater than the interval between two tasks.

The reason is that there is a wait (time) method in row 296 of quartzschedulerthread, where the time may be 0, resulting in a dead state.

This has been fixed in Versions later than quartz 1.6.2.

It took two days to study and finally found this problem.

In Linux, if the thread is in trouble, you can use the kill-3 PID Method to print the running state of the thread,

We can see where each thread runs. Print the output in the standard output. For example, the Tomcat thread is in Catalina. Out.