Does anyone know how to correctly clean threaded resources up on an exception (say a network blip) that results in an restart? I have some DB pools that if an exception occurs elsewhere in the DAG, when it restarts the process the pool thread is just abandoned and still living in the JVM process leaving connections opened. Only if the exception occurs inside the actual DB task can I catch and properly close the pool.