https://issues.apache.org/bugzilla/show_bug.cgi?id=52066
Alexander Pogrebnyak <alex-pub.apache-...@reflexion.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|WONTFIX |
--- Comment #6 from Alexander Pogrebnyak <alex-pub.apache-...@reflexion.net>
2012-03-27 17:03:49 UTC ---
(In reply to comment #5)
> Our library could definitely initiate the interruption. The easiest use case
> would be pool.close() to get rid of all the waiting threads. and the waiting
> thread in this case, would receive a SQLException
>
> In the above use case, it should absolutely be cleared.
>
> Since the waiting thread receives the SQLException, I am still not convinced.
> the call DataSource.getConnection does not have any interrupted exceptions
> associated with it.
OK, Let's get to this problem from the other end. Is it possible to provide a
user preference that by default executes a current code, but when set preserved
the thread interrupted status?
I really hate to implement yet another facade to your otherwise feature
complete product.
If this approach is acceptable to you I am willing to contribute the required
patch for review.
--
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
