[
https://issues.apache.org/jira/browse/SLING-4676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14697315#comment-14697315
]
Carsten Ziegeler commented on SLING-4676:
-----------------------------------------
[~baedke] I'm confused :) Isn't your patch already doing all that is required?
As far as i can tell setting allowCoreThreadTimeOut to true and settings the
keep alive time should do it. Or do I overlook something?
> 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
>
> Attachments: sling-4676-provisional.patch
>
>
> 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)
