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 14592] New: - DBCP must be robust against e.g. database shutdowns
Date Fri, 15 Nov 2002 14:47:04 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=14592>.
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=14592

DBCP must be robust against e.g. database shutdowns

           Summary: DBCP must be robust against e.g. database shutdowns
           Product: Commons
           Version: 1.0 Final
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: Dbcp
        AssignedTo: commons-dev@jakarta.apache.org
        ReportedBy: cetin.ergen@bgsys.de


Hi,

i'm constructing a new architecture for database based web applications. One of 
the major goals is to integrate a robust (open source) connection pooling 
component into the underlying framework.
I have tested dbcp for robustness and it has failed. In our company they often 
must restart the datbases, so for now the connection pool on the web server 
doesn't work after shutdown.
Is it possible to make dbcp robust against such szenarios ?

Sincerely
Çetin Ergen

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