tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [Bug 54116] Deadlocks with mysql driver
Date Fri, 09 Nov 2012 09:10:55 GMT

--- Comment #1 from Patric Rufflar <> ---
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:
For additional commands, e-mail:

View raw message