https://issues.apache.org/bugzilla/show_bug.cgi?id=50571
--- Comment #7 from Jeremy Norris <jnorri...@gmail.com> 2011-01-12 12:37:33 EST --- Agreed, the actual bug is ConnectionState swallowing the exception on pool startup, however I suspect that fixing it properly will require some of the signatures to change. In my opinion, SQLException's needs to propagate all the way up to ConnectionPool.getConnection(). SQLException is a checked exception so when we propagate it from JdbcInterceptor, it will affect the callers signature unless that caller swallows it (not what we want) or wraps it in a RuntimeException (a bit clumsy). Thanks for your time and discussion, it's very appreciated. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- 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
