DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports Events Over 2 million developers have joined DZone. Join Today! Thanks for visiting DZone today,
Edit Profile Manage Email Subscriptions Moderation Admin Console How to Post to DZone Article Submission Guidelines
View Profile
Sign Out
Refcards
Trend Reports
Events
Zones
Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Partner Zones AWS Cloud
by AWS Developer Relations
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Partner Zones
AWS Cloud
by AWS Developer Relations
The Latest "Software Integration: The Intersection of APIs, Microservices, and Cloud-Based Systems" Trend Report
Get the report
  1. DZone
  2. Coding
  3. Java
  4. Guide to Java 8 Concurrency Using Executors

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.

Himani Arora user avatar by
Himani Arora
·
May. 17, 18 · Tutorial
Like (27)
Save
Tweet
Share
119.43K Views

Join the DZone community and get the full member experience.

Join For Free

Working 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();
    &nbsp;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

  • Java 8 docs
  • Concurrency in Java

This article was first published on the Knoldus blog.

Java (programming language) Executor (software) Task (computing)

Published at DZone with permission of Himani Arora, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • Utilizing Database Hooks Like a Pro in Node.js
  • Isolating Noisy Neighbors in Distributed Systems: The Power of Shuffle-Sharding
  • Kubernetes-Native Development With Quarkus and Eclipse JKube
  • Key Elements of Site Reliability Engineering (SRE)

Comments

Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends: