Shulou(Shulou.com)05/31 Report--

In this article, the editor introduces in detail "how to deal with Springboot asynchronous tasks and timing tasks". The content is detailed, the steps are clear, and the details are handled properly. I hope this article "how to deal with Springboot asynchronous tasks and timing tasks" can help you solve your doubts.

1 preface

In Springboot, asynchronous tasks and timing tasks are often encountered to deal with problems. In order to make good use of these two configurations and not interfere with normal business, they need to be asynchronized. How to set up a reasonable asynchronous processing thread is its core and key.

2 Asynchronous task settings

Using asynchronous tasks in projects is a common way to solve problems, usually in order to reduce the waiting time of requests, the business processing is processed asynchronously in the background, which can improve the user experience and increase the throughput of the system.

It is also very simple to enable asynchronous tasks in springboot, which requires only two steps:

1 Open the @ EnableAsync annotation.

2 add @ Async to the methods that require asynchronous processing.

It is important to note that the method executed asynchronously can have a return value, but it must be Future, here and multithreaded submit to submit the task and get the processing result.

At this point, the configuration and use of asynchronous tasks is over. Asynchronous tasks also use multi-thread thread pool technology, using SimpleAsyncTaskExecutor by default to achieve, but how can their own fate in the hands of others, always feel not very secure, asynchronous tasks how to use a custom thread pool to achieve, this is a good question, the answer is also AsyncConfigurer. This is an interface, you need to implement the getAsyncExecutor method to get a thread pool, if you need to grab exception information, you can implement a method getAsyncUncaughtExceptionHandler.

The specific code is as follows:

The execution result of the asynchronous task is as follows, which indicates that the thread pool configuration of the asynchronous task has taken effect:

3 scheduled task configuration

Timed tasks can be said to be a very common configuration in project development, and exist as compensation for business functions, which plays an important role. The use of timed tasks can be divided into fixed time and crontab expressions. In the implementation tools, spring has its own @ Schedule, which is widely used in single projects and does not need other platforms and additional configurations. It is sufficient for simple tasks. But for distributed systems, it is a bit inadequate, and then quartz, elastic-job and xxl-job are born, among which xxl-job is particularly excellent. Here, I will only introduce the use of @ Schedule:

1 enable @ EnableScheduling annotation globally.

2 add @ Schedule annotations to the tasks that need to be performed, and specify the execution method, whether to execute fixedly or with cron expressions.

In actual project development, crontab expressions are widely used:

Like asynchronous task execution, scheduled task execution also has its own asynchronous task thread pool. Here, the API you need to implement is SchedulingConfigurer, and you can implement its configureTasks method:

After all the configuration files are done, you can see that the thread pool configuration for scheduled tasks has taken effect:

After reading this, the article "how to deal with Springboot asynchronous tasks and timing tasks" has been introduced. If you want to master the knowledge points of this article, you still need to practice and use it yourself. If you want to know more about related articles, welcome to follow the industry information channel.

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.