Hi All,

I believe I've identified a bug in
Executors.AutoShutdownDelegatedExecutorService that can trigger a
classloader leak even in the presence of "correct" Executor lifecycling.
AutoShutdownDelegatedExecutorService only unlinks the PhantomReference used
for cleanup handling when it is shutdown via the shutdown() method. If an
Executor wrapped in this way is instead shutdown using the shutdownNow()
method and it references a classloader via an injected attribute:
ThreadFactory, AbortPolicy, etc. then the cleanup action will reference the
classloader, and the classloader will remain strongly referenced. Adding an
additional override as shown in the attached patch is sufficient to fix the
leak in my testing.

Thanks,

Chris

P.S. I believe I'm likely covered wrt OCA via my employer IBM.

Attachment: executor-classloader-leak.patch
Description: Binary data

Reply via email to