tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [Bug 54116] New: Deadlocks with mysql driver
Date Wed, 07 Nov 2012 22:53:33 GMT

          Priority: P2
            Bug ID: 54116
           Summary: Deadlocks with mysql driver
          Severity: critical
    Classification: Unclassified
                OS: Linux
          Hardware: PC
            Status: NEW
           Version: unspecified
         Component: jdbc-pool
           Product: Tomcat Modules

Created attachment 29567
stack information with the blockeds threads

The problem is very well detailed in the following mysql bug:

I found exactly the same situation related in this mysql bug. The answer from
mysql guys is: 

"This is precisely the reason the JDBC-4.0 spec added the abort() method. There
is no foolproof way to implement the semantics of Connection.close() *and*
never have deadlocks.

The abort() method is designed to be used in these cases (it takes no locks,
but doesn't attempt to clean up currently open statements, etc).

Have you asked your connection pool vendor why they're not using the abort()

And the bug's is market with "won't fix". My question is, ¿is jdbc-pool using
this abort method instead of close?, ¿if the "Pool-Cleaner" is one of the
threads involved in the blocking this can cause connections not removed from
the pool?. I attach to this bug the stack trace information, yo can see that
this thread is blocked. I can reproduce this error via load/stress testing the
application, in production this error occurs randomly between 3 or 4 days

For more information i'm using grails with the grails tomcat jdbc plugin

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