https://bz.apache.org/bugzilla/show_bug.cgi?id=61022
--- Comment #7 from Christopher Schultz ---
You mean like this?
http://tomcat.apache.org/tomcat-8.0-doc/jdbc-pool.html
--
You are receiving this mail because:
You are the assignee for the bug.
https://bz.apache.org/bugzilla/show_bug.cgi?id=61022
--- Comment #6 from Gary Murphy ---
Thank you. That resolved the issue. Is there documentation for this and other
available interceptors?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bz.apache.org/bugzilla/show_bug.cgi?id=61022
Keiichi Fujino changed:
What|Removed |Added
Resolution|--- |INVALID
Status|NEEDINFO
https://bz.apache.org/bugzilla/show_bug.cgi?id=61022
--- Comment #4 from Gary Murphy ---
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 t
https://bz.apache.org/bugzilla/show_bug.cgi?id=61022
--- Comment #3 from Christopher Schultz ---
Are you saying that bug #48392 is actually not completely fixed? 48392 was
reported for getResultSet().getConnection(), but the comments indicate that
also getResultSet().getStatement().getConnection(
https://bz.apache.org/bugzilla/show_bug.cgi?id=61022
--- Comment #2 from Gary Murphy ---
I am not sure what you are needing. I am using the connection pool with
functional programming, not in a serlvet container as the normal use case would
expect. As a result, I don't always easily have the re
https://bz.apache.org/bugzilla/show_bug.cgi?id=61022
Christopher Schultz changed:
What|Removed |Added
Status|NEW |NEEDINFO
--- Comment #1 from Chr
