commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Phil Steitz (JIRA)" <>
Subject [jira] Commented: (POOL-97) EVICTION_TIMER is never cancelled.
Date Sun, 22 Jul 2007 19:04:06 GMT


Phil Steitz commented on POOL-97:

A more conservative solution would be to revert to the pool 1.2 setup where the Evictor is
a thread.  This would also break backward compatibility at the package private level, but
would revert to a well-tested solution with essentially the same scaling / perfornance challenges
as the per instance Timer in the patch.  See POOL-56 or 1.2 sources for changes to revert.

> EVICTION_TIMER is never cancelled.
> ----------------------------------
>                 Key: POOL-97
>                 URL:
>             Project: Commons Pool
>          Issue Type: Bug
>    Affects Versions: 1.3
>            Reporter: Devendra Patil
>             Fix For: 2.0
>         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.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message