You’d be better off using the get() method. futureOne.get(); futureTwo.get(); Both of which wait for notification from the thread that it finished processing, this saves you the busy-wait-with-timer you are now using which is not efficient nor elegant. As a bonus, you have the API get(long timeout, TimeUnit unit) which allows you to define a … Read more
How does wrapping a Callable in a FutureTask help if the Thread can’t be stopped by cancel? You want to cancel the task, not the thread running it. Using cancel(true) prevents the task from starting (but doesn’t remove it from the queue) and interrupts the thread if the task has started. The Task can ignore … Read more
It is not the same thing. In the second example where thenApply is not used it is certain that the call to convertToB is executed in the same thread as the method doSomethingAndReturnA. But, in the first example when the thenApply method is used other things can happen. First of all, if the CompletableFuture that … Read more
FutureTask This class provides a base implementation of Future, with methods to start and cancel a computation Future is the interface