ListenableFuture in Guava
Join the DZone community and get the full member experience.
Join For FreeListenableFuture
in Guava is an attempt to define consistent API for Future
objects to register completion callbacks. With the ability to add callback when Future
completes, we can asynchronously and effectively respond to incoming
events. If your application is highly concurrent with lots of future
objects, I strongly recommend using ListenableFuture
whenever you can.
Technically ListenableFuture
extends Future
interface by adding simple
void addListener(Runnable listener, Executor executor)
method. That's it. If you get a hold of ListenableFuture
you can register Runnable
to be executed immediately when future in question completes. You must also supply Executor
(ExecutorService
extends it) that will be used to execute your listener - so that long-running listeners do not occupy your worker threads.
Let's put that into action. We will start by refactoring our first example of web crawler to use ListenableFuture
. Fortunately in case of thread pools it's just a matter of wrapping them using MoreExecutors.listeningDecorator()
:
ListeningExecutorService pool = MoreExecutors.listeningDecorator(Executors.newFixedThreadPool(10)); for (final URL siteUrl : topSites) { final ListenableFuture<String> future = pool.submit(new Callable<String>() { @Override public String call() throws Exception { return IOUtils.toString(siteUrl, StandardCharsets.UTF_8); } }); future.addListener(new Runnable() { @Override public void run() { try { final String contents = future.get(); //...process web site contents } catch (InterruptedException e) { log.error("Interrupted", e); } catch (ExecutionException e) { log.error("Exception in task", e.getCause()); } } }, MoreExecutors.sameThreadExecutor()); }
There are several interesting observations to make. First of all notice how ListeningExecutorService
wraps existing Executor
. This is similar to ExecutorCompletionService
approach. Later on we register custom Runnable
to be notified when each and every task finishes. Secondly notice how ugly error handling becomes: we have to handle InterruptedException
(which should technically never happen as Future
is already resolved and get()
will never throw it) and ExecutionException
. We haven't covered that yet, but Future<T>
must somehow handle exceptions occurring during asynchronous computation. Such exceptions are wrapped in ExecutionException
(thus the getCause()
invocation during logging) thrown from get()
.
Finally notice MoreExecutors.sameThreadExecutor()
being used. It's a handy abstraction which you can use every time some API wants to use an Executor
/ExecutorService
(presumably thread pool) while you are fine with using current
thread. This is especially useful during unit testing - even if your
production code uses asynchronous tasks, during tests you can run
everything from the same thread.
No matter how handy it is, whole code seems a bit cluttered. Fortunately there is a simple utility method in fantastic Futures
class:
Futures.addCallback(future, new FutureCallback<String>() { @Override public void onSuccess(String contents) { //...process web site contents } @Override public void onFailure(Throwable throwable) { log.error("Exception in task", throwable); } });
FutureCallback
is a much simpler abstraction to work with, resolves future and does
exception handling for you. Also you can still supply custom thread pool
for listeners if you want. If you are stuck with some legacy API that
still returns Future
you may try JdkFutureAdapters.listenInPoolThread()
which is an adapter converting plain Future<V>
to ListenableFuture<V>
. But keep in mind that once you start using addListener()
, each such adapter will require one thread exclusively to work so this solution doesn't scale at all and you should avoid it.
Future<String> future = //... ListenableFuture<String> listenableFuture = JdkFutureAdapters.listenInPoolThread(future);
Once we understand the basics we can dive deeply into biggest strength of listening futures: transformations and chaining. This is advanced stuff, you have been warned.
Published at DZone with permission of Tomasz Nurkiewicz, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.
Comments