[
https://issues.apache.org/jira/browse/POOL-242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14552642#comment-14552642
]
Phil Steitz commented on POOL-242:
----------------------------------
Sorry I mistook Michael for the OP. I agree with Michael that there is not
much point in making the timer thread name configurable. I agree with Mark
that what should be named is the pool, which already can be named (via JMX, but
we could just expose the name directly as well). I also agree that logging
enablement (making it easier to log and get the pool name in the log) is IIUC
the real issue here. This might best be addressed as part of POOL-267. As a
workaround, I will point out that a custom EvictionPolicy can do whatever
logging a user wants to add.
> Set thread name for EvictionTimer
> ---------------------------------
>
> Key: POOL-242
> URL: https://issues.apache.org/jira/browse/POOL-242
> Project: Commons Pool
> Issue Type: Improvement
> Affects Versions: 1.5, 1.6, 2.0, 2.1, 2.2, 2.3
> Reporter: Peter Plosz
> Priority: Trivial
> Fix For: 1.6.1, 1.5.8
>
>
> Setting up thread name for EvictionTimer makes life easier when debugging
> issues.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
