Using InheritableThreadLocal with ThreadPoolExecutor — or — a ThreadPoolExecutor that doesn't reuse threads

Question

I am trying to use both InheritableThreadLocal and a ThreadPoolExecutor.

This breaks down because ThreadPoolExecutor reuses th

Answer 1

Why not just pass the current connection on to any sub-tasks spawned by the main task? maybe some sort of shared Context object?