Bug #68389 dead lock in mysql-connector-java-5.1.23
Submitted: 15 Feb 2013 14:09 Modified: 15 Feb 2013 16:20
Reporter: Anton L Email Updates:
Status: Duplicate Impact on me:
None 
Category:Connector / J Severity:S2 (Serious)
Version:5.1.23 OS:Any
Assigned to: CPU Architecture:Any
Tags: deadlock

[15 Feb 2013 14:09] Anton L
Description:
I've upgraded from 5.1.20 to 5.1.23 and after a while 2 threads stuck in deadlock
thread dump:

[Thread id 8534, BLOCKED, lock: java.util.GregorianCalendar@e3520c2, lockOwner: Thread id 592]
    com.mysql.jdbc.PreparedStatement.setTimestampInternal(PreparedStatement.java:4818)
    com.mysql.jdbc.PreparedStatement.setTimestamp(PreparedStatement.java:4785)
    com.mysql.jdbc.PreparedStatement.setObject(PreparedStatement.java:4279)
    com.mysql.jdbc.PreparedStatement.setObject(PreparedStatement.java:4106)
    ........

[Thread id 592, BLOCKED, lock: com.mysql.jdbc.JDBC4Connection@49ce01a4, lockOwner: Thread id 8534]
    com.mysql.jdbc.ResultSetImpl.fastTimestampCreate(ResultSetImpl.java:1066)
    com.mysql.jdbc.ResultSetRow.getTimestampFast(ResultSetRow.java:1393)
    com.mysql.jdbc.ByteArrayRow.getTimestampFast(ByteArrayRow.java:127)
    com.mysql.jdbc.ResultSetImpl.getTimestampInternal(ResultSetImpl.java:6592)
    com.mysql.jdbc.ResultSetImpl.getTimestamp(ResultSetImpl.java:6192)
    com.mysql.jdbc.ResultSetImpl.getTimestamp(ResultSetImpl.java:6230)
    ........

How to repeat:
hard to repeat
[15 Feb 2013 14:14] Anton L
sorry, this is the same bug #67760
please close this report