You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by bu...@apache.org on 2007/03/26 09:54:42 UTC
DO NOT REPLY [Bug 36581] - [pool] GenericObjectPool Evictor should be a TimerTask, not a Thread
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=36581>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=36581
devendra.m.patil@gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |
------- Additional Comments From devendra.m.patil@gmail.com 2007-03-26 00:54 -------
I'm using DBCP on a grid infrastructure. It dynamically deploys/undeploys
resources (i.e. jars) on the individual grid servers. I found that the
EVICTION_TIMER (java.util.Timer) used in GenericObjectPool is never cancelled
(even after closing the pool). This thread keeps on running and blocks dynamic
undeployment (i.e. deleting) of jars. Setting it to daemon doesn�t help since
grid-servers do not restart during resource deployment/undeployments.
Can you please help me on this?
Thanks,
Deven
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org