[
https://issues.apache.org/jira/browse/POOL-348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16573179#comment-16573179
]
Gary Gregory edited comment on POOL-348 at 8/16/18 11:56 PM:
-------------------------------------------------------------
Thank you for your report. Feel free to provide a patch. Please make sure all
unit tests pass. BUT this is likely a bug in the users of Commons Pool. The
evictor thread is managed by a scheduler. This scheduler is canceled when its
owning pool is closed. I would make sure you close all pool resources you
allocate.
Notice the calls to
org.apache.commons.pool2.impl.BaseGenericObjectPool.startEvictor(-1) from
various close() implementations.
was (Author: garydgregory):
Thank you for your report. Feel free to provide a patch. Please make sure all
unit tests pass.
> The commons-pool-evictor-thread should run as a Deamon
> ------------------------------------------------------
>
> Key: POOL-348
> URL: https://issues.apache.org/jira/browse/POOL-348
> Project: Commons Pool
> Issue Type: Bug
> Affects Versions: 2.6.0
> Reporter: Thomas Neerup
> Priority: Major
>
> The thread "commons-pool-evictor-thread" does not run as a Deamon and keeps
> the JVM alive when all other non Deamon threads has ended.
> Is there any reason for this behaviour? Otherwise the thread should be
> started as a Deamon.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
