[jira] [Commented] (SLING-4676) Clean up threads or refresh threads when put back into the pool

["Manfred Baedke (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SLING-4676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14693834#comment-14693834 ] 

Manfred Baedke commented on SLING-4676:
---------------------------------------

[~cziegeler], I will have to introduce new parameters to the thread pool configuration, which would add new methods to the interface ThreadPoolConfig. What's the policy on that? Creating a new interface extending the old one? 

> Clean up threads or refresh threads when put back into the pool
> ---------------------------------------------------------------
>
>                 Key: SLING-4676
>                 URL: https://issues.apache.org/jira/browse/SLING-4676
>             Project: Sling
>          Issue Type: Improvement
>          Components: Commons
>            Reporter: Carsten Ziegeler
>             Fix For: Commons Threads 3.2.2
>
>
> A thread from the pool might use thread locals which are - for whatever reason - not cleaned up, when the thread is put back into the pool.
> This can lead to memory leaks.
> We should protect against this.
> Unfortunately there is no official API to clean up thread locals. There are solutions out there using reflection.
> Another option is to simply discard the thread object after some time of usage and use a fresh one. This needs to include thread objects staying in the pool for a long time



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)