Deadlocks occur in c3p0 GooGoStatementCache when using MS SQL Server

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Medium
    • 2.9.0
    • Affects Version/s: 2.7.7
    • Component/s: None
    • None

      A typical stack for a stuck thread is:

      "Task-Thread-for-com.mchange.v2.async.ThreadPerTaskAsynchronousRunner@6ac1d821" daemon prio=6 tid=0x0000000056e78800 nid=0x2430 waiting for monitor entry [0x000000006a23f000]
   java.lang.Thread.State: BLOCKED (on object monitor)
	at net.sourceforge.jtds.jdbc.ConnectionJDBC2.releaseTds(ConnectionJDBC2.java:1965)
	- waiting to lock <0x0000000027a5b5f0> (a net.sourceforge.jtds.jdbc.ConnectionJDBC3)
	at net.sourceforge.jtds.jdbc.JtdsStatement.close(JtdsStatement.java:853)
	at net.sourceforge.jtds.jdbc.JtdsPreparedStatement.close(JtdsPreparedStatement.java:485)
	at com.mchange.v1.db.sql.StatementUtils.attemptClose(StatementUtils.java:41)
	at com.mchange.v2.c3p0.stmt.GooGooStatementCache$1StatementCloseTask.run(GooGooStatementCache.java:404)
	at com.mchange.v2.async.ThreadPerTaskAsynchronousRunner$TaskThread.run(ThreadPerTaskAsynchronousRunner.java:255)

            Assignee:
            Val Trubnikov [Atlassian]
            Reporter:
            Tom Davies
            Votes:
            2 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: