EVICTION_TIMER is never cancelled.
----------------------------------

                 Key: POOL-97
                 URL: https://issues.apache.org/jira/browse/POOL-97
             Project: Commons Pool
          Issue Type: Bug
    Affects Versions: 1.3
            Reporter: Devendra Patil


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 pools.

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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to