Using @Async in Spring Boot: Configuration, Best Practices, and Common Pitfalls

@Async is presented as a powerful yet simple way to improve performance in Spring Boot applications by running methods in the background while the main thread continues.

To use it, add @EnableAsync to a configuration class or the main application class:

@SpringBootApplication<br/>@EnableAsync<br/>public class BackendAsjApplication {<br/>}<br/>

Define a ThreadPoolTaskExecutor bean to control pool size, queue capacity, and thread naming, optionally adding a rejection handler:

@Bean<br/>public ThreadPoolTaskExecutor taskExecutor() {<br/>  ThreadPoolTaskExecutor executor = new ThreadPoolTaskExecutor();<br/>  executor.setCorePoolSize(2);<br/>  executor.setMaxPoolSize(2);<br/>  executor.setQueueCapacity(500);<br/>  executor.setThreadNamePrefix("MyAsyncThread-");<br/>  executor.setRejectedExecutionHandler((r, executor1) -> log.warn("Task rejected, thread pool is full and queue is also full"));<br/>  executor.initialize();<br/>  return executor;<br/>}<br/>

Apply @Async to service methods, for example:

@Service<br/>public class EmailService {<br/>    @Async<br/>    public void sendEmail() {<br/>        // asynchronous code<br/>    }<br/>}<br/>

Common pitfalls:

Do not call an @Async method from the same class; it will execute synchronously. Use a separate bean instead.

Methods annotated with @Transactional lose transaction context when executed asynchronously, which can lead to data inconsistency.

Long‑running tasks can block the default pool; consider defining a dedicated executor for heavy tasks:

@Primary<br/>@Bean(name = "taskExecutorDefault")<br/>public ThreadPoolTaskExecutor taskExecutorDefault() {<br/>  // same configuration as above<br/>}<br/><br/>@Bean(name = "taskExecutorForHeavyTasks")<br/>public ThreadPoolTaskExecutor taskExecutorForHeavyTasks() {<br/>  // same configuration, different thread name prefix<br/>}<br/>

Specify the executor when declaring the async method:

@Service<br/>public class EmailService {<br/>    @Async("taskExecutorForHeavyTasks")<br/>    public void sendEmailHeavy() {<br/>        // heavy task implementation<br/>    }<br/>}<br/>

Exception handling: async methods do not propagate exceptions to the caller. Wrap the result in a Future and handle errors explicitly:

@Service<br/>public class EmailService {<br/>    @Async<br/>    public Future<String> sendEmail() throws Exception {<br/>        throw new Exception("Oops, cannot send email!");<br/>    }<br/>}<br/><br/>@Service<br/>public class PurchaseService {<br/>    @Autowired<br/>    private EmailService emailService;<br/><br/>    public void purchase() {<br/>        try {<br/>            Future<String> future = emailService.sendEmail();<br/>            String result = future.get();<br/>            System.out.println("Result: " + result);<br/>        } catch (Exception e) {<br/>            System.out.println("Caught exception: " + e.getMessage());<br/>        }<br/>    }<br/>}<br/>

In summary, @Async can greatly improve scalability when used correctly, but developers must be aware of its limitations regarding self‑invocation, transaction boundaries, thread blocking, and exception propagation.