Tuesday, November 11, 2003, 8:56:19 AM, you wrote: > Actually you are correct, > I thought about this last night and remembered that the app in question > was losing its connection to the database due to the firewall > configuration. It was fixed by convincing the sysadmin that his > firewall needs to let idle connections from the webserver to the db > server stay open.
> The result was the same though, dbPool tries to use a connection that it > thinks is still open, but in reality is closed. > -Aaron It seems like dbPool ought to be able to trap an error like this gracefully and seamlessly open new, replacement connections without notice. At least that's what I would expect it to do. Maybe it still needs a bit of work? Jacob ------------------------------------------------------- This SF.Net email sponsored by: ApacheCon 2003, 16-19 November in Las Vegas. Learn firsthand the latest developments in Apache, PHP, Perl, XML, Java, MySQL, WebDAV, and more! http://www.apachecon.com/ _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
