https://issues.apache.org/bugzilla/show_bug.cgi?id=54116
--- Comment #1 from Patric Rufflar <pat...@rufflar.com> --- Looks like mysql jdbc driver bug because they use inconsistent locking: com.mysql.jdbc.ConnectionImpl.close() locks in the following order: 1. com.mysql.jdbc.JDBC4Connection 2. com.mysql.jdbc.JDBC4ResultSet while com.mysql.jdbc.ResultSetImpl.getString() locks in a reversed order: 1. com.mysql.jdbc.JDBC4ResultSet 2. com.mysql.jdbc.JDBC4Connection Because I see no jdbc pool classes involved in the locking of these objects I doubt that jdbc pool is responsible in this deadlock situation. -- 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
