【问题标题】:Understanding "APPARENT DEADLOCK!!! Complete Status" details了解“明显的死锁!!!完成状态”详细信息
【发布时间】:2020-02-05 13:29:05
【问题描述】:

我在下面发布了一小部分日志,如果有人可以解码以下内容,我将不胜感激:

  • 列表项
  • 托管线程
  • 活动线程
  • 活动任务
  • 待处理的任务
  • 池线程堆栈跟踪

我有以下 C3PO 配置:

c3p0.minPoolSize=10
c3p0.maxPoolSize=40
c3p0.acquireIncrement=5
c3p0.maxIdleTime=1800
c3p0.maxStatements=50
c3p0.idleConnectionTestPeriod=180

这是日志:

09-02@12:28:43 WARN  ThreadPoolAsynchronousRunner [Timer-0] - com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@700ec336 -- APPARENT DEADLOCK!!! Creating emergency threads for unassigned pending tasks!
09-02@12:28:43 WARN  ThreadPoolAsynchronousRunner [Timer-0] - com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@700ec336 -- APPARENT DEADLOCK!!! Complete Status:
        Managed Threads: 3
        Active Threads: 3
        Active Tasks:
                com.mchange.v2.c3p0.stmt.GooGooStatementCache$1StatementCloseTask@34ac7f2c (com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#1)
                com.mchange.v2.c3p0.stmt.GooGooStatementCache$1StatementCloseTask@28d13cb8 (com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#0)
                com.mchange.v2.c3p0.stmt.GooGooStatementCache$1StatementCloseTask@40e968f7 (com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#2)
        Pending Tasks:
                com.mchange.v2.c3p0.stmt.GooGooStatementCache$1StatementCloseTask@1bea516c
                com.mchange.v2.c3p0.stmt.GooGooStatementCache$1StmtAcquireTask@348797c5
                com.mchange.v2.c3p0.stmt.GooGooStatementCache$1StatementCloseTask@31fd2174
                com.mchange.v2.c3p0.stmt.GooGooStatementCache$1StmtAcquireTask@619f604f
                com.mchange.v2.c3p0.stmt.GooGooStatementCache$1StmtAcquireTask@266c149b
                com.mchange.v2.c3p0.stmt.GooGooStatementCache$1StmtAcquireTask@1bcdfd2
                com.mchange.v2.c3p0.stmt.GooGooStatementCache$1StatementCloseTask@170a54e2
                com.mchange.v2.c3p0.stmt.GooGooStatementCache$1StmtAcquireTask@274acd3f
                com.mchange.v2.c3p0.stmt.GooGooStatementCache$1StatementCloseTask@1fe8f740
                com.mchange.v2.c3p0.stmt.GooGooStatementCache$1StmtAcquireTask@77c09b1d
                com.mchange.v2.c3p0.stmt.GooGooStatementCache$1StatementCloseTask@607ca57
                com.mchange.v2.c3p0.stmt.GooGooStatementCache$1StmtAcquireTask@697518d8
                com.mchange.v2.c3p0.stmt.GooGooStatementCache$1StatementCloseTask@6b242ff
                com.mchange.v2.c3p0.stmt.GooGooStatementCache$1StatementCloseTask@214c76c8
                com.mchange.v2.c3p0.stmt.GooGooStatementCache$1StmtAcquireTask@230a558c
                com.mchange.v2.c3p0.stmt.GooGooStatementCache$1StmtAcquireTask@7b766c4c
                com.mchange.v2.c3p0.stmt.GooGooStatementCache$1StatementCloseTask@1bc030e7
                com.mchange.v2.c3p0.stmt.GooGooStatementCache$1StatementCloseTask@66ca9bec
                com.mchange.v2.c3p0.stmt.GooGooStatementCache$1StatementCloseTask@7fc2d7ac
                com.mchange.v2.c3p0.stmt.GooGooStatementCache$1StatementCloseTask@50dd9ebb
                com.mchange.v2.c3p0.stmt.GooGooStatementCache$1StmtAcquireTask@5e03077
                com.mchange.v2.c3p0.stmt.GooGooStatementCache$1StmtAcquireTask@418dd7a4
                com.mchange.v2.c3p0.stmt.GooGooStatementCache$1StatementCloseTask@4748719b
                com.mchange.v2.c3p0.stmt.GooGooStatementCache$1StatementCloseTask@651a9bac
                com.mchange.v2.c3p0.stmt.GooGooStatementCache$1StmtAcquireTask@35e26d0f
                com.mchange.v2.c3p0.stmt.GooGooStatementCache$1StmtAcquireTask@24660f6c
                com.mchange.v2.c3p0.stmt.GooGooStatementCache$1StatementCloseTask@287e8e1f
                com.mchange.v2.c3p0.stmt.GooGooStatementCache$1StmtAcquireTask@ca4a9fe
                com.mchange.v2.c3p0.stmt.GooGooStatementCache$1StmtAcquireTask@e94692e
                com.mchange.v2.c3p0.stmt.GooGooStatementCache$1StmtAcquireTask@3185527c
                com.mchange.v2.c3p0.stmt.GooGooStatementCache$1StmtAcquireTask@27ea644a
                com.mchange.v2.resourcepool.BasicResourcePool$1RefurbishCheckinResourceTask@d5e4abf
                com.mchange.v2.c3p0.stmt.GooGooStatementCache$1StmtAcquireTask@297d4874
                com.mchange.v2.resourcepool.BasicResourcePool$1RefurbishCheckinResourceTask@601fccf3
                com.mchange.v2.c3p0.stmt.GooGooStatementCache$1StmtAcquireTask@47c896d2
                com.mchange.v2.c3p0.stmt.GooGooStatementCache$1StmtAcquireTask@4225d9cf
                com.mchange.v2.resourcepool.BasicResourcePool$1RefurbishCheckinResourceTask@42fec6f6
                com.mchange.v2.c3p0.stmt.GooGooStatementCache$1StmtAcquireTask@64b862d6
                com.mchange.v2.resourcepool.BasicResourcePool$1RefurbishCheckinResourceTask@5610343
                com.mchange.v2.resourcepool.BasicResourcePool$1RefurbishCheckinResourceTask@241d2677
                com.mchange.v2.c3p0.stmt.GooGooStatementCache$1StmtAcquireTask@75c86126
                com.mchange.v2.c3p0.stmt.GooGooStatementCache$1StmtAcquireTask@36624233
                com.mchange.v2.c3p0.stmt.GooGooStatementCache$1StmtAcquireTask@6ce83e29
                com.mchange.v2.resourcepool.BasicResourcePool$1RefurbishCheckinResourceTask@3492d9b
                com.mchange.v2.resourcepool.BasicResourcePool$1RefurbishCheckinResourceTask@39511ccc
                com.mchange.v2.resourcepool.BasicResourcePool$1RefurbishCheckinResourceTask@7c39b279
                com.mchange.v2.c3p0.stmt.GooGooStatementCache$1StmtAcquireTask@2ff465a6
                com.mchange.v2.resourcepool.BasicResourcePool$1RefurbishCheckinResourceTask@563d8de2
                com.mchange.v2.resourcepool.BasicResourcePool$1RefurbishCheckinResourceTask@632e1ca9
                com.mchange.v2.resourcepool.BasicResourcePool$1RefurbishCheckinResourceTask@685bce1d
                com.mchange.v2.resourcepool.BasicResourcePool$1RefurbishCheckinResourceTask@63390771
                com.mchange.v2.resourcepool.BasicResourcePool$1RefurbishCheckinResourceTask@3517be9b
Pool thread stack traces:
        Thread[com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#0,5,main]
                com.mysql.jdbc.StatementImpl.close(StatementImpl.java:575)
                com.mchange.v1.db.sql.StatementUtils.attemptClose(StatementUtils.java:41)
                com.mchange.v2.c3p0.stmt.GooGooStatementCache$1StatementCloseTask.run(GooGooStatementCache.java:404)
                com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:547)
        Thread[com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#2,5,main]
                com.mysql.jdbc.StatementImpl.close(StatementImpl.java:575)
                com.mchange.v1.db.sql.StatementUtils.attemptClose(StatementUtils.java:41)
                com.mchange.v2.c3p0.stmt.GooGooStatementCache$1StatementCloseTask.run(GooGooStatementCache.java:404)
                com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:547)
        Thread[com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#1,5,main]
                com.mysql.jdbc.StatementImpl.close(StatementImpl.java:575)
                com.mchange.v1.db.sql.StatementUtils.attemptClose(StatementUtils.java:41)
                com.mchange.v2.c3p0.stmt.GooGooStatementCache$1StatementCloseTask.run(GooGooStatementCache.java:404)
                com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:547)

我们将不胜感激有关明显死锁的一些信息。

【问题讨论】:

    标签: java c3p0


    【解决方案1】:

    线程池包含 3 个线程。 (“托管线程”)。他们三个都是“活跃的”,试图完成一项任务。 (“活动线程”),没有准备好工作的休眠线程。列出了任务。它们都是缓存语句关闭任务。

    当线程池中的所有任务长时间保持不变时会触发APPARENT DEADLOCK。 c3p0(实际上是它下面的线程池库)最终假定,如果池中没有任务成功完成,则池已死锁。库 interrupt()s 然后丢弃这些线程,并用新线程替换它们,以便其他任务(您有很长的任务积压,“待处理任务”)可以尝试运行。

    就您而言,这是一个众所周知的问题。某些 JDBC 驱动程序的 Statement.close() 操作在其父 Connection 正在使用时可能会死锁。对于这些(正式不合规格的)驱动程序,c3p0 实现了谨慎的Statement 关闭策略,其中Statement 销毁是tasked asynchronously and only performed when the parent Connection is known not to be in use

    TL; DR:将statementCacheNumDeferredCloseThreads 设置为1。

    c3p0.statementCacheNumDeferredCloseThreads=1
    

    【讨论】:

      【解决方案2】:

      我已将 connertor 更改为 <dependency> mysql

      <artifactId>mysql-connector-java</artifactId>
      
      
      <version>8.0.26</version>
      
      
      </dependency>
      

      然后就可以了

      【讨论】:

        猜你喜欢
        • 1970-01-01
        • 1970-01-01
        • 1970-01-01
        • 1970-01-01
        • 1970-01-01
        • 1970-01-01
        • 2018-11-10
        • 1970-01-01
        • 1970-01-01
        相关资源
        最近更新 更多