You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2011/01/11 22:47:12 UTC
DO NOT REPLY [Bug 50571] Tomcat 7 JDBC connection pool exception
enhancement
https://issues.apache.org/bugzilla/show_bug.cgi?id=50571
Filip Hanik <fh...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
OS/Version| |All
--- Comment #1 from Filip Hanik <fh...@apache.org> 2011-01-11 16:47:08 EST ---
hi Jeremy,
I'm looking at your patch, and I will take a look at the connection state
interceptor. most SQL exceptions, as you say, should percolate through when it
makes sense.
I wont apply the patch as it is, as I don't understand why most of the methods
just change the signature of the method by adding "throws SQLException".
for example ConnectionPool.abandon doesn't really need to throw a SQLException
best
Filip
--
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-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org