[SLING-11149] Expose information about cleaned up leftover ThreadLocal values

• Type: New Feature
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Fix Version/s: Commons Threads 3.3.0
• Component/s: Commons
• Assignee: Unassigned
• Reporter: Robert Munteanu
• Created: 16/Feb/22 17:02
• Updated: 28/Aug/23 13:11

Description

As discussed in SLING-10831, the ThreadLocal cleanup feature is valuable as a safeguard for code that might lead to hard-to-diagnose memory leaks.

At the same time, it does not let developers know when a leak has been prevented. We should improve this. The following improvements can be made:

1. log with a WARN level any cleanup operation. Care must be taken to not overflow the logs, so maybe a way of only reporting a cleanup for a certain key once can be used (memory-bound)
2. expose a counter that reports how many cleanup operations have been performed by a given thread pool

Issue Links

• links to: GitHub Pull Request #5