Guide to Java 8 Concurrency Using Executors
Here's an overview of the improvements Java 8 brought to concurrent programming with a focus on ExecutorService.
Join the DZone community and get the full member experience.
Join For FreeWorking with the Thread class in Java can be very tedious and error-prone. For this reason, the Concurrency API was introduced back in 2004 with the release of Java 5 and has been enhanced with every new Java release. The API is located in the package java.util.concurrent. It contains a set of classes that make it easier to develop concurrent (multi-threaded) applications in Java.
The executor services are one of the most important parts of the Concurrency API. With the help of this guide, you can learn how to execute code in parallel via tasks and executor services in Java 8.
ExecutorService
The Concurrency API introduces the concept of an ExecutorService as a higher-level replacement for working with threads directly.
Executors are capable of managing a pool of threads, so we do not have to manually create new threads and run tasks in an asynchronous fashion.
Have a look at a simple Java ExecutorService:
ExecutorService executor = Executors.newSingleThreadExecutor();
executor.submit(() -> {
String threadName = Thread.currentThread().getName();
System.out.println("Hello " + threadName);
});
Here, it submits a Runnable task for execution and returns a Future representing that task. Since Runnable is a functional interface, we are utilizing Java 8 lambda expressions to print the current threads name to the console.
ExecutorService Implementation
Since ExecutorService is an interface, it has to be implemented in order to make any use of it. The ExecutorService has the following implementations in the java.util.concurrent package:
- ThreadPoolExecutor
- ScheduledThreadPoolExecutor
Executors' factory class can also be used to create executor instances.
For example:
ExecutorService executorService1 = Executors.newSingleThreadExecutor();
ExecutorService executorService2 = Executors.newFixedThreadPool(5);
Delegating Tasks to ExecutorService
Below are few of the different ways that can be used to delegate tasks for execution to an ExecutorService:
- execute(Runnable command)
- submit(Callable task)
- submit(Runnable task)
- invokeAny(Collection<? extends Callable<T>> tasks)
- invokeAll(Collection<? extends Callable<T>> tasks)
execute(Runnable Command)
This method takes a java.lang.Runnable object and executes it asynchronously.
ExecutorService executor = Executors.newSingleThreadExecutor();
executor.execute(() -> {
String threadName = Thread.currentThread().getName();
System.out.println("Hello " + threadName);
});
submit(Callable Task) and submit(Runnable Task)
The submit(Runnable task) method takes a Runnable implementation and returns a Future object, which can be used to check if the Runnable as finished executing.
Runnable task=()-> {
System.out.println("runnable task");
};
ExecutorService executorService= Executors.newSingleThreadExecutor();
Future future= executorService.submit(task);
System.out.println("value - "+future.get()); //returns null if the task has finished successfully
Callables are functional interfaces, but unlike Runnable, they return a value. A submit(callable task) method takes a Callable implementation
Callable<String> task = () -> "task 1 ";
ExecutorService executorService= Executors.newSingleThreadExecutor();
Future future = executorService.submit(task);
System.out.println("value - "+future.get()); //returns task1
invokeAll(Collection<? extends Callable<T>> tasks)
This method supports batch submitting of multiple callables at once. It accepts a collection of callables and returns a list of futures.
ExecutorService executor = Executors.newFixedThreadPool(1);
List<Callable<String>> callables = Arrays.asList(
() -> "t1",
() -> "t2"
);
executor.invokeAll(callables)
.stream()
.map(future -> {
try {
return future.get();
}
catch (Exception e) {
throw new IllegalStateException(e);
}
})
.forEach(System.out::println);
invokeAny(Collection<? extends Callable<T>> Tasks)
This method works slightly differently than invokeAll(). Instead of returning future objects, it blocks until the first callable terminates and returns the result of that callable.
ExecutorService executor = Executors.newWorkStealingPool();
List<Callable<String>> callables = Arrays.asList(
()->"task 1 completed",
ExecutorService Shutdown
ExecutorService provides two methods for this purpose:
- shutdown() waits for currently running tasks to finish.
- shutdownNow() interrupts all running tasks and shuts the executor down immediately.
References
Published at DZone with permission of Himani Arora, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.
Comments