dead lock with mysql connector/J 3.1.12-bin.jar (1 reply)

Hi,
We have the following environment:

mysql-connector-java-3.1.12-bin.jar
JDK 1.6
Connection Pool - tomcat-jdbc.jar
Linux OS
Tomcat 6.0.35

We are experiencing deadlock issue as follows:

Found one Java-level deadlock:
=============================
"catalina-exec-1":
waiting to lock monitor 0x000000005d7944b8 (object 0x00000005bd522568, a com.mysql.jdbc.Connection),
which is held by "[Pool-Cleaner]:Tomcat Connection Pool[1-1015483951]"
"[Pool-Cleaner]:Tomcat Connection Pool[1-1015483951]":
waiting to lock monitor 0x000000005dcdea28 (object 0x00000005bd659ce8, a com.mysql.jdbc.ResultSet),
which is held by "catalina-exec-1"


The code has been using the 3.1.12 mysql connect and we did not upgrade to 5 because there seems to be some issues regarding the data trunction on columns and other issues.

Looks like this deadlock issue is due to the ordering of the locks (connection and statement).Is this a known issue, i have seen some bugs related to this but not sure which version had the fix for these as the end comments are not clear.

http://bugs.mysql.com/bug.php?id=15636

http://bugs.mysql.com/bug.php?id=14972&error=lp

Please let me know if upgrading to other versions like 3.1.14 would solve this issue.

Thanks
ggn