All tasks in a thread pool must provide a mechanism for notifying the application if they terminate abnormally. Failure to do so cannot cause resource leaks because the threads in the pool are still recycled, but it makes failure diagnosis extremely difficult or impossible.
The best way to handle exceptions at the application level is to use an exception handler. The handler can perform diagnostic actions, clean-up and shut down the JVM, or simply log the details of the failure.
...
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="589085a8e4cdab23-fc4e5ee9-417e481d-8b2590ce-aaa4d1a3f2de44c72f1125b6"><ac:plain-text-body><![CDATA[ | [[API 2006 | AA. References#API 06]] | Interfaces | ]]></ac:plain-text-body></ac:structured-macro> |
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="9020f7419dd75e26-05889fd5-45bf4d50-bf22a34c-9442d6ce896ca449a6f16bad"><ac:plain-text-body><![CDATA[ | [[Goetz 2006 | AA. References#Goetz 06]] | Chapter 7.3, Handling Abnormal Thread Termination | ]]></ac:plain-text-body></ac:structured-macro> |
...