http://lsd.luminis.eu/scheduledthreadpoolexecutor-horribly-broken/ Fri, 20 Jan 2012 08:31:42 +0100 http://wordpress.org/?v=2.8.6 hourly 1 http://lsd.luminis.eu/scheduledthreadpoolexecutor-horribly-broken/comment-page-1/#comment-53614 Lukasz Szelag Mon, 19 Sep 2011 17:32:37 +0000 http://lsd.luminis.net/?p=100#comment-53614 I solved this problem by keeping a map of submitted futures to corresponding tasks. Then in the overriden afterExecute() method I was able to retrieve both the future and the task (Future future = (Future)r). Using futures was helpful for handling errors (future.get() would rethrow any exceptions). For this to work submitted tasks need to implement Callable. I solved this problem by keeping a map of submitted futures to corresponding tasks. Then in the overriden afterExecute() method I was able to retrieve both the future and the task (Future future = (Future)r). Using futures was helpful for handling errors (future.get() would rethrow any exceptions). For this to work submitted tasks need to implement Callable.

]]>