DO NOT REPLY [Bug 50660] Improve validationQuery error handling

2012-03-20 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=50660 Filip Hanik changed: What|Removed |Added Status|NEW |RESOLVED Resolution|

DO NOT REPLY [Bug 50660] Improve validationQuery error handling

2011-01-26 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=50660 --- Comment #4 from Filip Hanik 2011-01-26 13:23:24 EST --- If the connection to the database fails here, the interceptor will print out validationQuery has failed. and that is not correct I think the pool itself needs to do some validation

DO NOT REPLY [Bug 50660] Improve validationQuery error handling

2011-01-26 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=50660 --- Comment #3 from Daniel Mikusa 2011-01-26 12:49:46 EST --- What about adding an Interceptor to do the validation? The attached interceptor would take the validation query and run it when the pool is created. If there is a problem with

DO NOT REPLY [Bug 50660] Improve validationQuery error handling

2011-01-26 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=50660 --- Comment #2 from Daniel Mikusa 2011-01-26 12:48:21 EST --- Created an attachment (id=26553) --> (https://issues.apache.org/bugzilla/attachment.cgi?id=26553) proposed interceptor -- Configure bugmail: https://issues.apache.org/bugzill

DO NOT REPLY [Bug 50660] Improve validationQuery error handling

2011-01-26 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=50660 --- Comment #1 from Filip Hanik 2011-01-26 12:05:16 EST --- hi Dan, this is a tricky one. Cause, we'd also be logging a lot of false positive. Connections that have gone stale and simply need to be reconnected. So WARN log level would not