Skip to main content

Multi threading in SpringBoot Application

How I got my SpringBoot application to execute a service in multiple threads

  1. Enabled SpringBoot application run Async tasks
  2. Defined a service method which can be invoked asynchronously and returns CompletableFuture object as required by Spring
  3. Let Spring manage service component instance
  4. Though not required, configured TaskExecutor Spring could use

Enable SpringBoot application to run tasks asynchronously

To be able to execute tasks using multiple threads asynchronously SpringBoot application must be annotated with @EnableAsync. I defined this annotation right after @SpringBootApplication.

@SpringBootApplication
@EnableAsync
public class NosqlApplication implements CommandLineRunner {
Logger logger = LoggerFactory.getLogger(NosqlApplication.class);

Aync service method returning CompletableFuture object

Spring could invoke tasks synchronously and asynchronously. To be able to invoke tasks asynchronously (and let main thread do other things) I annotated the service method with @Async, and this method is returning CompletableFuture object.

@Override
@Async
public CompletableFuture<ArrayList<String>> generateDocuments(File templateFile, int numberOfDocuments) {
ArrayList<String> documentsList = new ArrayList<>(numberOfDocuments);

Component or service must be managed by SpringBoot

For Spring framework to be able to manage threads the component must be managed by Spring i.e. do not instantiate object using new, instead let Spring create a instance and inject it.

@Autowired
DocumentGenerator documentGenerator;

@Autowired
DocumentWriter documentWriter;

That's all it took to run multithreaded code in SpringBoot. 

Spring framework also gives you ability to configure task executor to be used for thread execution, if you wish to use.

One could configure TaskExecutor SpringBoot to use

If an Executor is not provided Spring creates and use default SimpleAsyncTaskExecutor. But to have finer control on TaskExecutor one could define a task executor bean. I created a method taskExecutor in the SpringBoot application which returns an Executor bean. The method signature must be public Exectutor taskExecutor() for Spring to identify it as TaskExecutor provider. By providing a task executor I could control how many threads to to start with, how many application could use and what to do when executor queue is full etc.

@Bean
public Executor taskExecutor() {
logger.debug("In taskExecutor");
ThreadPoolTaskExecutor executor = new ThreadPoolTaskExecutor();
executor.setCorePoolSize(10);
executor.setMaxPoolSize(20);
executor.setQueueCapacity(10);


ReferencesGetting Started | Creating Asynchronous Methods (spring.io)

Comments

  1. tips betting soccer today happyluke happyluke gioco digitale gioco digitale 카지노 카지노 840Biggest and Largest RTP RTP RTP in Slot Machine

    ReplyDelete

Post a Comment

Popular posts from this blog

Install Citrix Workspace on Groovy Gorilla on Raspeberry Pi

  How I got Citrix Workspace working on Groovy Gorilla (Ubuntu 20.10) on Raspberry Pi 400 At first installing Citrix on Ubuntu may seem like a no brainer, but because how Ubuntu and Citrix have packaged software for Raspberry Pi, it is pain in the neck to get it working correctly.  What is the issue? When I installed Ubuntu on Raspberry Pi hardware, t he only package available for Pi 4/400 was 64 bit, but Citrix has  only ARMHF packages for raspberry Pi which is 32 bit. Technically 32 bit package should work on 64 bit architecture without a fuss, but for whatever reason Citrix package checks if package to be installed matches OS bit level. Attempting to install the package as well as subsequent system updates report failure. More over Software Center can't install or remove software complaining broken packages on the system. First let me tell you how I installed Citrix then will go on fixing issue. Prepare system for Citrix installation Check system architecture using dpkg --print

Configuring Spring Framework with YAML

Spring application can be configured using YAML as effectively as using properties file. With YAML file one can, Create environment specific profiles Define properties at application level Define (or override) properties at profile level Spring Framework loads application.yml by default just the way it loads application.properties. If you want to change the name of the yml file you'll have to use context loader to tell what file to look for. Must knows of the yml based configuration Profiles - YML supports multiple profiles in a single file. One can define environment specific configurations as profiles in a single file. Profiles separator - YML configuration file uses 3 dashes ( --- ) to separate a profile. Every property you define after --- is specific to that profile. Profile name - Give profile a name using spring.config.activate.on-profile property. Active profile(s) - Define which profile or profiles are active using spring.profiles.active property. More than one profile c