commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Thomas (JIRA)" <>
Subject [jira] Commented: (POOL-97) EVICTION_TIMER is never cancelled.
Date Sat, 08 Dec 2007 08:57:43 GMT


Mark Thomas commented on POOL-97:

I can reproduce this. I have been thinking about a solution that would fix this and POOL-56.
I am not quite there yet. I'll post some patches here when I have something concrete. Being
able to break binary compatibility at the package private level should make a solution easier.

> EVICTION_TIMER is never cancelled.
> ----------------------------------
>                 Key: POOL-97
>                 URL:
>             Project: Commons Pool
>          Issue Type: Bug
>    Affects Versions: 1.3
>            Reporter: Devendra Patil
>             Fix For: 1.4
>         Attachments: timer.patch
> The static EVICTION_TIMER (java.util.Timer) used in GenericObjectPool is never cancelled
(even after closing the pool). The GenericObjectPool.close() method just cancels the _evictor
(TimerTask). I agree this behaviour is ideal if EVICTION_TIMER is to be used across multiple
> But, In my case, the resources (i.e. jars) are dynamically deployed and undeployed on
remote grid-servers. If EVICTION_TIMER thread doesn't stop, the grid-servers fails to undeploy
(i.e. delete) the jars. The grid-server doesn't restart during resource deployment/undeployment,
so, setting EVICTION_TIMER to daemon doesn't help me.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message