https://bz.apache.org/bugzilla/show_bug.cgi?id=64083
--- Comment #2 from Christopher Schultz <ch...@christopherschultz.net> --- (In reply to ToolGuy1 from comment #1) > We have faced this issue in our shop as well with MS SQL Server on version > 9.2.x driver for Java 11. Wondering if a configurable option could be added > to the code to allow exceptions thrown from clearWarnings() calls to cause > the pool to discard connections during return to the pool. Seems like if the > underlying DB vendor supports clearWarnings commands that hit the db server > ( suspect most do ), that this failing with an Exception should be a decent > indicator that the underlying connection is not in good health. SQL WARNINGs are not an indication of a broken connection. In fact, they are specifically an indication of a GOOD connection: the database is in fact communicating. -1 on the suggestion in comment #1, though the original report seems reasonable. to me. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
