[CAMEL-17588] Missing Clean-Up for DefaultReactiveExecutor.Worker-ThreadLocals

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Won't Do
• Affects Version/s: 3.14.1
• Fix Version/s: 3.17.0
• Component/s: camel-core
• Estimated Complexity: Unknown
• Assignee: Unassigned
• Reporter: Björn Ohm
• Created: 02/Feb/22 15:24
• Updated: 04/Apr/22 07:20
• Resolved: 31/Mar/22 04:50

Description

We are running a Camel-Application on a Tomcat. While the Tomcat-Shutdown we observed a bunch of Thread-Local-WARNINGS in the catalina.out like:

02-Feb-2022 01:31:23.810 SCHWERWIEGEND [main] org.apache.catalina.loader.WebappClassLoaderBase.checkThreadLocalMapForLeaks The web application [provinzial-integration-intern] created a ThreadLocal with key of type [java.lang.ThreadLocal.SuppliedThreadLocal] (value [java.lang.ThreadLocal$SuppliedThreadLocal@4a4357f5]) and a value of type [org.apache.camel.impl.engine.DefaultReactiveExecutor.Worker] (value [org.apache.camel.impl.engine.DefaultReactiveExecutor$Worker@76e66f23]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak.

Obviously this belongs to the ThreadLocals used in org.apache.camel.impl.engine.DefaultReactiveExecutor.

In the worst case, this can lead to memory problems. 
The ThreadLocals should be cleaned up.

Issue Links

• relates to: CAMEL-17712 Memory leak in DefaultCamelContext reported by Tomcat 10
• relates to: CAMEL-17785 camel-core - DefaultReactorExecutor use an non thread-local worker pool
• links to: GitHub Pull Request #7182
• links to: https://lists.apache.org/thread/y5zgnz8ndyjdcmyp4vkt5oht15dtq0kw