In what cases does Future.get() throw ExecutionException or InterruptedException

Question

My code snippet:

ExecutorService executor = Executors.newSingleThreadExecutor(); try {     Task t = new Task(response,inputToPass,pTypes,unit.getInstance(),methodName,unit.getUnitKey());     Future<SCCallOutResponse> fut = executor.submit(t);     response = fut.get(unit.getTimeOut(),TimeUnit.MILLISECONDS); } catch (TimeoutException e) {     // if the task is still running, a TimeOutException will occur while fut.get()     cat.error("Unit " + unit.getUnitKey() + " Timed Out");     response.setVote(SCCallOutConsts.TIMEOUT); } catch (InterruptedException e) {     cat.error(e); } catch (ExecutionException e) {     cat.error(e); } finally {     executor.shutdown(); } 

How should i handle the InterruptedException and ExecutionException in the code?

And in what cases, are these exceptions thrown?

Answer 1

ExecutionException and InterruptedException are two very different things.

ExecutionException wraps whatever exception the thread being executed threw, so if your thread was, for instance, doing some kind of IO that caused an IOException to get thrown, that would get wrapped in an ExecutionException and rethrown.

An InterruptedException is not a sign of anything having gone wrong. It is there to give you a way to let your threads know when it's time to stop so that they can finish up their current work and exit gracefully. Say I want my application to stop running, but I don't want my threads to drop what they're doing in the middle of something (which is what would happen if I made them daemon threads). So when the application is being shutdown, my code calls the interrupt method on these threads, which sets the interrupt flag on them, and the next time those threads are waiting or sleeping they check the interrupt flag and throw an InterruptedException, which I can use to bail out of whatever infinite-loop processing/sleeping logic the threads are engaged in. (And if the thread doesn't wait or sleep, it can just check the interrupt flag periodically.) So it is an instance of an exception being used to change the logical flow. The only reason you would log it at all is in an example program to show you what's happening, or if you're debugging a problem where interrupt logic is not working correctly.