commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 13856] New: - Sharing eviction threads
Date Tue, 22 Oct 2002 17:49:57 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13856>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13856

Sharing eviction threads

           Summary: Sharing eviction threads
           Product: Commons
           Version: unspecified
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Major
          Priority: Other
         Component: Pool
        AssignedTo: commons-dev@jakarta.apache.org
        ReportedBy: roytmana@peacetech.com


One eviction thread per pool is very expensive. In app server we can have tens 
or even hundreds of applications with several jdbc and other pools. It is 
imposibble to let each one to span a thread for eviction (I like this eviction 
feature very much) We clearly need to share eviction thread among pools.
In my opinion the best would be to use some sort of Timer class which will send 
notification to all pools which need eviction (or any time driven maintenance) 
done. Timer class can be for example accessible via JNDI in server environment 
and explicetly set to a pool during its configuration

--
To unsubscribe, e-mail:   <mailto:commons-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:commons-dev-help@jakarta.apache.org>


Mime
View raw message