Shulou(Shulou.com)06/02 Report--

This article is about how Spring scheduled tasks stop without reporting errors for no reason. The editor thinks it is very practical, so share it with you as a reference and follow the editor to have a look.

Spring timing task stops without reporting an error for no reason

In the beginning, timers included in Spring are used to configure scheduled tasks, which is simple and fast. The configuration is as follows:

However, after using it for a period of time, it stops for no reason and does not report an error, so there is no related error log, and you need to restart Tomcat before you can continue to execute scheduled tasks.

At first, I thought that this problem still occurred after it was set to double due to the limit of the maximum number of connections in the database. Under the reminder of my classmates, I realized that it might be caused by thread blocking, so I found out the reason on the Internet:

Spring scheduled tasks are executed concurrently by default, and do not wait for the last task to be completed, but will be executed as long as the interval is up.

Solution

1. Configure the concurrent property of JobDetail to false. Concurrent execution of tasks is not allowed.

two。 When the task takes a long time to execute, find the root problem.

So change the timer that comes with Spring to Quartz and rely on related packages:

Org.quartz-scheduler quartz 2.2.1

The scheduled tasks are configured as follows:

1 false

SchedulerFactoryBeanWithShutdownDelay is used in startQuartz because when Tomcat is turned off, it is possible that the task thread is not completely shut down, resulting in a memory leak.

SchedulerFactoryBeanWithShutdownDelay.java

Import org.quartz.SchedulerException;import org.springframework.scheduling.quartz.SchedulerFactoryBean;public class SchedulerFactoryBeanWithShutdownDelay extends SchedulerFactoryBean {@ Override public void destroy () throws SchedulerException {super.destroy (); try {Thread.sleep (1000);} catch (InterruptedException e) {throw new RuntimeException (e) Spring scheduled tasks that no longer start spring after running have the following two characteristics

1. There is a serial sequence between single timing tasks. If the previous task is not finished, the next task will not start.

2. Multiple tasks will interfere with each other. If other tasks started at the same time are not finished, the next task will not start.

Investigation mode

1. Check your code first to see if there are any problems such as deadlock, jam, bug, and no timeout for http requests.

2, check whether all scheduled tasks do not start, if the basic judgment is caused by feature 2, check which scheduled task is slow, stuck, bug and so on.

Solution idea

1. Repair bug, if any.

2. If there is a task that is slow to execute and cannot be optimized, you can use Quartz instead of spring scheduled tasks.

Dependency package

Org.quartz-scheduler quartz 2.2.1

Configuration:

1 false Thank you for your reading! This is the end of this article on "how to stop Spring scheduled tasks without reporting errors for no reason". I hope the above content can be of some help to you, so that you can learn more knowledge. if you think the article is good, you can share it out for more people to see!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.