https://issues.apache.org/bugzilla/show_bug.cgi?id=50660
Filip Hanik fha...@apache.org changed:
What|Removed |Added
Status|NEW |RESOLVED
https://issues.apache.org/bugzilla/show_bug.cgi?id=50660
--- Comment #1 from Filip Hanik fha...@apache.org 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
https://issues.apache.org/bugzilla/show_bug.cgi?id=50660
--- Comment #2 from Daniel Mikusa dmik...@vmware.com 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/bugzilla/show_bug.cgi?id=50660
--- Comment #3 from Daniel Mikusa dmik...@vmware.com 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
https://issues.apache.org/bugzilla/show_bug.cgi?id=50660
--- Comment #4 from Filip Hanik fha...@apache.org 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
