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=5902>. 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=5902 Database Connection pooling error [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WORKSFORME ------- Additional Comments From [EMAIL PROTECTED] 2002-03-16 05:25 ------- My experience with MySQL has been that, when you restart the database for any reason, any existing connections will experience "Communications link failure". The original version of the Struts connection pool (in 1.0) did not have any mechanism to detect such problems. Now, however, you can use the "pingQuery" property of GenericDataSource to define an SQL "SELECT" statement that will be tried, whenever the pool is asked for a connection, before it is returned to you. If the query fails for any reason, the pool will assume that the old connection no longer works, so it closes that one and creates a new one instead. This catches nearly all cases of problems caused by database shutdowns and restarts, or other similar problems--please try this on your own application. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>