https://bz.apache.org/bugzilla/show_bug.cgi?id=61022
--- Comment #4 from Gary Murphy <g...@hilbertinc.com> --- I didn't go back through the source code history, since 48392 was fixed in 2011. I suspect it was fixed properly and regressed at some subsequent refactor. I think the proper fix would be the one discussed there - meaning that the connection should provide a proxy for the statement and the statement should provide a proxy for the result set. That will keep the semantics of the Connection class consistent. However, the fix I made to ConnectionPool to simply check for a closed connection would be simpler and would resolve my issue. I would be glad to send that to you for your review if you would like. -- 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
