https://issues.apache.org/bugzilla/show_bug.cgi?id=54116
--- Comment #3 from Patric Rufflar <pat...@rufflar.com> --- The pool cleaner thread periodically - checks for abandoned connections (depending on configuration) - does pool resizing (e.g. dropping connections), if necessary - verifies idle connections (depending on configuration) If this thread gets blocked you'll loose this functionality. It depends on your application if you rely on these features or not. Normally, this will not cause your application to fail (completely). If I were you I would drop a comment at the existing mysql issue and tell them that they use inconsistent locking in their jdbc driver which is causing the problem here. Also mention that Connection.abort() is only available in java 7. If they will not fix the inconsistent locking ask for a java 6 compatible solution. BTW: A workaround which will lower the probability of the deadlock is to disable the jdbc-pool's "remove abandoned connections" feature. -- 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
