APPARENT DEADLOCK!!! Creating emergency threads for unassigned pending tasks!

最新推荐文章于 2022-08-26 09:56:09 发布
最新推荐文章于 2022-08-26 09:56:09 发布
阅读量2.8k 收藏
点赞数
CC 4.0 BY-SA版权
分类专栏： 工作
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.youkuaiyun.com/Bii_yu/article/details/80966400
本文记录了一次C3P0连接池出现死锁的情况，详细展示了出现问题时的警告日志及线程堆栈信息。通过分析，可以发现所有活动线程都在尝试获取数据库连接，而连接池中没有可用连接，导致了任务堆积。

2018-07-09 10:00:57.862 WARN  [C3P0PooledConnectionPoolManager[identityToken->1bqrudf9wyma3jctc8ecn|172099cb]-AdminTaskTimer] [c.m.v.a.ThreadPoolAsynchronousRunner:211] - com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@69173a6c -- APPARENT DEADLOCK!!! Creating emergency threads for unassigned pending tasks!
2018-07-09 10:00:57.867 WARN  [C3P0PooledConnectionPoolManager[identityToken->1bqrudf9wyma3jctc8ecn|172099cb]-AdminTaskTimer] [c.m.v.a.ThreadPoolAsynchronousRunner:211] - com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@69173a6c -- APPARENT DEADLOCK!!! Complete Status: 
Managed Threads: 3
Active Threads: 3
Active Tasks: 
com.mchange.v2.resourcepool.BasicResourcePool$ScatteredAcquireTask@58a9583a
on thread: C3P0PooledConnectionPoolManager[identityToken->1bqrudf9wyma3jctc8ecn|172099cb]-HelperThread-#1
com.mchange.v2.resourcepool.BasicResourcePool$ScatteredAcquireTask@55df754f
on thread: C3P0PooledConnectionPoolManager[identityToken->1bqrudf9wyma3jctc8ecn|172099cb]-HelperThread-#0
com.mchange.v2.resourcepool.BasicResourcePool$ScatteredAcquireTask@7d5ec44b
on thread: C3P0PooledConnectionPoolManager[identityToken->1bqrudf9wyma3jctc8ecn|172099cb]-HelperThread-#2
Pending Tasks: 
com.mchange.v2.resourcepool.BasicResourcePool$ScatteredAcquireTask@346fd2c
com.mchange.v2.resourcepool.BasicResourcePool$ScatteredAcquireTask@29975562
com.mchange.v2.resourcepool.BasicResourcePool$ScatteredAcquireTask@e66aa43
com.mchange.v2.resourcepool.BasicResourcePool$ScatteredAcquireTask@76341c17
com.mchange.v2.resourcepool.BasicResourcePool$ScatteredAcquireTask@572066a1
com.mchange.v2.resourcepool.BasicResourcePool$ScatteredAcquireTask@103200b7
com.mchange.v2.resourcepool.BasicResourcePool$ScatteredAcquireTask@42ccf6af
Pool thread stack traces:
Thread[C3P0PooledConnectionPoolManager[identityToken->1bqrudf9wyma3jctc8ecn|172099cb]-HelperThread-#0,5,main]
java.net.DualStackPlainSocketImpl.connect0(Native Method)
java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source)
java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)
java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)
java.net.AbstractPlainSocketImpl.connect(Unknown Source)
java.net.PlainSocketImpl.connect(Unknown Source)
java.net.SocksSocketImpl.connect(Unknown Source)
java.net.Socket.connect(Unknown Source)


net.sf.log4jdbc.DriverSpy.connect(DriverSpy.java:728)
com.mchange.v2.c3p0.DriverManagerDataSource.getConnection(DriverManagerDataSource.java:175)
com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:220)
com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:206)
com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.acquireResource(C3P0PooledConnectionPool.java:203)
com.mchange.v2.resourcepool.BasicResourcePool.doAcquire(BasicResourcePool.java:1138)
com.mchange.v2.resourcepool.BasicResourcePool.doAcquireAndDecrementPendingAcquiresWithinLockOnSuccess(BasicResourcePool.java:1125)
com.mchange.v2.resourcepool.BasicResourcePool.access$700(BasicResourcePool.java:44)
com.mchange.v2.resourcepool.BasicResourcePool$ScatteredAcquireTask.run(BasicResourcePool.java:1870)
com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:696)
Thread[C3P0PooledConnectionPoolManager[identityToken->1bqrudf9wyma3jctc8ecn|172099cb]-HelperThread-#1,5,main]
java.net.DualStackPlainSocketImpl.connect0(Native Method)
java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source)
java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)
java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)
java.net.AbstractPlainSocketImpl.connect(Unknown Source)
java.net.PlainSocketImpl.connect(Unknown Source)
java.net.SocksSocketImpl.connect(Unknown Source)

net.sf.log4jdbc.DriverSpy.connect(DriverSpy.java:728)
com.mchange.v2.c3p0.DriverManagerDataSource.getConnection(DriverManagerDataSource.java:175)
com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:220)
com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:206)
com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.acquireResource(C3P0PooledConnectionPool.java:203)
com.mchange.v2.resourcepool.BasicResourcePool.doAcquire(BasicResourcePool.java:1138)
com.mchange.v2.resourcepool.BasicResourcePool.doAcquireAndDecrementPendingAcquiresWithinLockOnSuccess(BasicResourcePool.java:1125)
com.mchange.v2.resourcepool.BasicResourcePool.access$700(BasicResourcePool.java:44)
com.mchange.v2.resourcepool.BasicResourcePool$ScatteredAcquireTask.run(BasicResourcePool.java:1870)
com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:696)
Thread[C3P0PooledConnectionPoolManager[identityToken->1bqrudf9wyma3jctc8ecn|172099cb]-HelperThread-#2,5,main]
java.net.DualStackPlainSocketImpl.connect0(Native Method)
java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source)
java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)
java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)
java.net.AbstractPlainSocketImpl.connect(Unknown Source)
java.net.PlainSocketImpl.connect(Unknown Source)
java.net.SocksSocketImpl.connect(Unknown Source)
java.net.Socket.connect(Unknown Source)

net.sf.log4jdbc.DriverSpy.connect(DriverSpy.java:728)
com.mchange.v2.c3p0.DriverManagerDataSource.getConnection(DriverManagerDataSource.java:175)
com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:220)
com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:206)
com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.acquireResource(C3P0PooledConnectionPool.java:203)
com.mchange.v2.resourcepool.BasicResourcePool.doAcquire(BasicResourcePool.java:1138)
com.mchange.v2.resourcepool.BasicResourcePool.doAcquireAndDecrementPendingAcquiresWithinLockOnSuccess(BasicResourcePool.java:1125)
com.mchange.v2.resourcepool.BasicResourcePool.access$700(BasicResourcePool.java:44)
com.mchange.v2.resourcepool.BasicResourcePool$ScatteredAcquireTask.run(BasicResourcePool.java:1870)

com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:696)

 

 

就是数据库连接问题，哈哈哈哈！  选中查看答案~

 

数据库连接池之c3p0-0.9.1.2，线上偶发APPARENT DEADLOCK，如何解？
m0_54854356的博客
07-17 1255
本篇其实是承接前面两篇的，都是讲定位线上的c3p0数据库连接池，发生连接泄露的问题。第二篇讲到，可以配置两个参数，来找出是哪里的代码借了连接后没有归还。但是，在我这边的情况是，对于没有归还的连接，借用者的堆栈确实是打印到日志了，但是我在本地模拟的时候，发现其实这些场景是有归还连接的，所以，我开始怀疑不是代码问题。不是业务代码问题，能是啥问题呢？我们先来看看连接是怎么归还到连接池的。
java deadlock oracle_APPARENT DEADLOCK!!! - C3P0连接池DeadLock机制分析
weixin_42394054的博客
03-04 688
1 问题近期，刚上线不久的生产系统的数据库连接池 C3P0 (版本为0.9.5.2)突然报出 APPARENT DEADLOCK!!! 错误。1.1 错误日志错误日志如下。com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@7cf60134 -- APPARENT DEADLOCK!!! Creating emerg...
C3P0错误APPARENT DEADLOCK 解决根本问题
12-06
网上传言C3P0是因为本身的BUG问题，然而今天我遇到这个问题并解决了，结果发现并不是。通过配置c3p0.maxStatements=0 这种方案只是治标不治本，或者干脆无效。我上传的解决方案肯定能解决这个问题的根本原因。出现这种问题，用的数据库都是oracle。
APPARENT DEADLOCK!!! Creating emergency threads for unassigned pending tasks
热门推荐
chinesesword的专栏
08-24 4万+
http://www.blogjava.net/bnlovebn/archive/2011/06/12/352125.html 最近orcale数据只有一台可以服务，导致hibernate 连接数据库每个13分钟就会报“APPARENT DEADLOCK!!! Creating emergency threads for unassigned pending tasks”的错误. 原因是
c3p0 APPARENT DEADLOCK!!! Creating emergency threads for unassigned pending tasks
weixin_33989058的博客
01-04 2725
2018-01-04 15:02:03,319 ---com.mchange.v2.async.ThreadPoolAsynchronousRunner: com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@4d6c4ebb -- APPARENT DEADLOCK!!! Creating emergency thr...
APPARENT DEADLOCK!!! Creating emergency threads for unassigned pending tasks!如何优化
06-01
这个错误信息通常表示出现了死锁（Deadlock）问题，即多个线程或进程互相等待对方释放资源而陷入无限等待的状态。针对这个问题，可以考虑以下几个方面： 1. 分析日志和堆栈信息：首先需要分析系统日志和堆栈信息，...
APPARENT DEADLOCK!!! 错误解决过程
weixin_33963594的博客
05-22 2652
项目环境数据库：oracle中间件：WAS2. 问题描述 2015.05.21（是个好日子），早上发现was后台报错如下：[15-5-217:31:01:171CST]00000027SystemErrRcom.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@498e49...
WARN - com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@1a24556b -- APPARENT DEADLOCK!!! Creating emergency threads for unassigned pending tasks! WARN - com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@1a24556b -- APPARENT DEADLOCK!!! Complete Status: [num_managed_threads: 3, num_active: 3; activeTasks: com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@3b3684a0 (com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#1), com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@4739bd1d (com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#0), com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@47d9c673 (com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#2); pendingTasks: com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@66d5ce15] WARN - Task com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@10dc3e1b (in deadlocked PoolThread) failed to complete in maximum time 60000ms. Trying interrupt(). WARN - Task com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@6de93ab9 (in deadlocked PoolThread) failed to complete in maximum time 60000ms. Trying interrupt(). WARN - Task com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@55deb264 (in deadlocked PoolThread) failed to complete in maximum time 60000ms. Trying interrupt().
最新发布
03-18
嗯，用户问的是关于Java应用中出现的一系列WARN日志，特别是提到“APPARENT DEADLOCK”和线程池的问题。首先，我需要理解这些日志的具体含义。看起来是数据库连接池的问题，可能涉及c3p0库，因为com.mchange.v2包是...
eclipse run on server 时 报的错误APPARENT DEADLOCK!!! Creating emergency threads for unassigned pending t...
dieyuanjiao9299的博客
08-02 1128
写这篇日记记录一下自己的愚蠢行为。 具体报错如下： 信息: Initializing c3p0 pool... com.mchange.v2.c3p0.ComboPooledDataSource [ acquireIncrement -> 10, acquireRetryAttempts -> 30, acquireRetryDelay -> 1000, autoC...
解决 APPARENT DEADLOCK!!! Creating emergency threads for unassigned pending tas
weixin_33779515的博客
03-24 1297
报错信息：APPARENT DEADLOCK!!! Creating emergency threads for unassigned pending tasks!在网上查了一下，大部分网友分析是c3p0造成的，我根据网友给出的参数修改了一下我的项目的参数，改好后重新启动，不再报错，稳定性需要观察。原文内容如下：最近部在生产环境的应用，系统重启后，跑了一天后就挂掉了，每天都是如此，之前一直都是挺稳...
APPARENT DEADLOCK Creating emergency threads for unassigned pending tasks
QiwzDeBLOG的博客
08-26 3264
在迁移CDH集群的元数据库后，重新启动集群失败，报APPARENT DEADLOCK!!! 错误
APPARENT DEADLOCK!!! Creating emergency threads for unas signed pending tasks!
无忌
08-27 228
2012-08-27 16:14:28 [WARN] [payCenter] [com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector->run(608) com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@7db242 -- ...
使用C3P0-0.9.1.jar包的问题：APPARENT DEADLOCK!!! Creating emergency threads for unassigned pending tasks!
学技术的时期
06-09 1万+
tomcat运行的好好的，老大说服务器挂了，你赶紧去看看。。。确实还是运行着，但报了错……小问题，重启一下tomcat呗，so...restart...C3P0-0.9.1.jar包的问题出现了：2011-06-09 16:15:57.500 [com.mchange.v2.c3p0.C3P0Registry]-[INFO] Initializing c3p0-0.9.1 [bui
c3po异常:Creating emergency threads for unassigned pending tasks!
彻底拆分，一切可控！
05-19 3884
原因是：原来是在同一时间触发一个insert操作，导致冲突。 这种情况下可以把 insert 操作延迟几秒钟之后再执行。
（转）解决 APPARENT DEADLOCK!!! Creating emergency threads for unassigned pending tas
wzf7065的博客
04-08 724
原文来源：http://billyshao.iteye.com/blog/1831840 最近把项目迁移到weblogic下运行，结果一直报错，报错信息： APPARENT DEADLOCK!!! Creating emergency threads for unassigned pending tasks! 在网上查了一下，大部分网友分析是c3p0造成的，我根据网友给出的参数修...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值