com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@3ef88fde -- APPARENT DEADLOCK!!!

最新推荐文章于 2021-02-13 07:39:57 发布
最新推荐文章于 2021-02-13 07:39:57 发布
阅读量2.8k 收藏 1
点赞数
CC 4.0 BY-SA版权
分类专栏： mysql
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.youkuaiyun.com/AlbertFly/article/details/60871931
本文记录了一次因应用服务器无法连接数据库导致的死锁问题，分析了可能的原因包括网络故障和JDBC配置错误，并提供了相应的排查思路。

摘要生成于 C知道 ，由 DeepSeek-R1 满血版支持， 前往体验 >

2017.03.08 13:10:11 com.mchange.v2.async.ThreadPoolAsynchronousRunner - com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@3ef88fde -- APPARENT DEADLOCK!!! Creating emergency threads for unassigned pending tasks!
2017.03.08 13:11:36 com.mchange.v2.async.ThreadPoolAsynchronousRunner - com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@3ef88fde -- APPARENT DEADLOCK!!! Complete Status: 
	Managed Threads: 3
	Active Threads: 2
	Active Tasks: 
		com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@41d0a916 (com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#1)
		com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@6a0d051b (com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#0)
	Pending Tasks: 
		com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@7cca6601
		com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@4bef0ba8
		com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@3ae6698a
		com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@6d1b013b
		com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@7ee0073
		com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@1a5f8216
		com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@74557fe0
		com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@193e86cb
		com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@5803865f
		com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@4f6af41d
		com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@76c0c4a6
		com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@69aeab32
		com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@4a6995d2
		com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@59eb3428
		com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@60ad5c36
		com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@15810ed0
		com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@4bf384b7
		com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@608e3155
		com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@1748f4f9
		com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@36cb1360
		com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@4e651fba
		com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@5106148b
		com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@662edb3b
		com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@e3b32e6
		com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@508aa156
		com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@3d663e69
		com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@38b7efd
		com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@3b3e15dc
		com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@690d3ce6
		com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@641955eb
		com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@3b57eaa4
		com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@8edd36c
		com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@35d35c08
		com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@473f2cd3
		com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@497f530
		com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@146224ab
		com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@37556101
		com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@4653a508
		com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@1d77d44a
		com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@26125563
		com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@7da3ea1b
		com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@145ed30e
		com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@5d724694
		com.mchange.v2.resourcepool.BasicResourcePool$AsyncTestIdleResourceTask@7977ce79
		com.mchange.v2.resourcepool.BasicResourcePool$AsyncTestIdleResourceTask@2894a83c
		com.mchange.v2.resourcepool.BasicResourcePool$AsyncTestIdleResourceTask@37b10ff4
		com.mchange.v2.resourcepool.BasicResourcePool$AsyncTestIdleResourceTask@498e78bc
Pool thread stack traces:
	Thread[com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#2,5,main]
		com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:533)
	Thread[com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#0,5,main]
		com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:562)
	Thread[com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#1,5,main]
		com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:562)

 

 

 

综合判断 发现是由于应用服务器连接不到数据库造成的 可能是网络问题。

或者检查jdbc的配置文件

[com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector.run(ThreadPoolAsynchronousR（已解决）
车马去闲闲——落日满秋山
04-01 800
使用tomcat启动程序时，报错。出现该警告的原因：数据库连接失败。
死锁 com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector
amyzhang1234的博客
01-08 3992
最近在IDEA中启动Tomcat经常会碰到这个错误，起初、一直没在意，现在碰到的次数多了，就去查看下这个问题，现描述如下： =2018-01-08 14:27:30,216 WARN [com.mchange.v2.async.ThreadPoolAsynchronousRunner] - com.mchange.v2.async.ThreadPoolAsynchronousRu...
java 线程死锁问题_Java 线程死锁的问题解决办法
weixin_35997546的博客
02-13 159
Java 线程死锁的问题解决办法【线程死锁】原因：两个线程相互等待被对方锁定的资源代码模拟：public class DeadLock {public static void main(String[] args) {Object obj = new Object();Object obj1 = new Object();DeadLockThread1 D1 = new DeadLockThrea...
com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector
weixin_33928137的博客
06-21 721
警告:com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@21eb3f-- APPARENT DEADLOCK!!! Creating emergency threads for unassigned pending tasks!2013-7-26 10:16:25 com.mchange....
com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@6440b4f -- APPARENT DEADLOCK!!!
zyd773848285的博客
08-06 656
com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@6440b4f -- APPARENT DEADLOCK!!!问题解决 这是我之前的c3p0的配置，然后服务启动就出现标题所示的错误 修改c3p0配信息为： 以上配置信息来源于其他博主的配置方案，亲测有效。 ...
C3P0访问数据库死锁，com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@128e59b3 -- APPARENT
qq_34091223的博客
05-31 4106
错误信息：com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@128e59b3 -- APPARENT DEADLOCK!!! Creating emergency threads for unassigned pending tasks!com.mchange.v2.async.ThreadPoolAsynchro...
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包是...
INFO - Initializing c3p0 pool... com.mchange.v2.c3p0.PoolBackedDataSource@309db823 [ connectionPoolDataSource -> com.mchange.v2.c3p0.WrapperConnectionPoolDataSource@234142af [ acquireIncrement -> 1, acquireRetryAttempts -> 30, acquireRetryDelay -> 1000, autoCommitOnClose -> false, automaticTestTable -> null, breakAfterAcquireFailure -> false, checkoutTimeout -> 0, connectionTesterClassName -> com.mchange.v2.c3p0.impl.DefaultConnectionTester, factoryClassLocation -> null, forceIgnoreUnresolvedTransactions -> false, identityToken -> 234142af, idleConnectionTestPeriod -> 0, initialPoolSize -> 1, maxIdleTime -> 120, maxPoolSize -> 100, maxStatements -> 0, maxStatementsPerConnection -> 0, minPoolSize -> 1, nestedDataSource -> com.mchange.v2.c3p0.DriverManagerDataSource@7a8d0ae3 [ description -> null, driverClass -> null, factoryClassLocation -> null, identityToken -> 7a8d0ae3, jdbcUrl -> jdbc:sqlserver://172.168.102.56:1432;databaseName=RTGSLiquidity, properties -> {useUnicode=true, user=******, password=******, characterEncoding=UTF-8} ], preferredTestQuery -> null, propertyCycle -> 300, testConnectionOnCheckin -> false, testConnectionOnCheckout -> false, usesTraditionalReflectiveProxies -> false ], factoryClassLocation -> null, identityToken -> 309db823, numHelperThreads -> 3 ] WARN - com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@556663b9 -- APPARENT DEADLOCK!!! Creating emergency threads for unassigned pending tasks! WARN - com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@556663b9 -- APPARENT DEADLOCK!!! Complete Status: [num_managed_threads: 3, num_active: 3; activeTasks: com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@5f9e08c9 (com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#2), com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@1a9c9d5e (com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#0), com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@7c815e1f (com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#1); pendingTasks: com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@2b4ce455] WARN - com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@556663b9 -- APPARENT DEADLOCK!!! Creating emergency threads for unassigned pending tasks! WARN - com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@556663b9 -- APPARENT DEADLOCK!!! Complete Status: [num_managed_threads: 3, num_active: 3; activeTasks: com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@171e8162 (com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#0), com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@3e0ce8dc (com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#2), com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@1332b0f9 (com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#1); pendingTasks: com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@1f308679] WARN - Task com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@1a9c9d5e (in deadlocked PoolThread) failed to complete in maximum time 60000ms. Trying interrupt(). WARN - Task com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@5f9e08c9 (in deadlocked PoolThread) failed to complete in maximum time 60000ms. Trying interrupt(). WARN - Task com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@7c815e1f (in deadlocked PoolThread) failed to complete in maximum time 60000ms. Trying interrupt() 这是一段新日志，继续帮我分析
最新发布
03-18
日志开始显示c3p0连接池初始化，然后出现多个警告，提示“APPARENT DEADLOCK!!!”，还有任务未能完成，尝试中断。这看起来像是连接池出现了死锁或资源争用的问题。 首先，检查连接池的配置。用户提供的配置中，...
警告: com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@513098 -- APPARENT DEADLOCK!!
陈楚东的专栏-学编程切记心浮气躁，贵在坚持
06-02 8066
当我们在配置成 p出现以下这些错误：
java多线程与死锁_Java多线程之死锁的出现和解决方法
weixin_36192634的博客
02-12 297
什么是死锁?死锁是这样一种情形：多个线程同时被阻塞,它们中的一个或者全部都在等待某个资源被释放.由于线程被无限期地阻塞,因此程序不能正常运行.形象的说就是:一个宝藏需要两把钥匙来打开,同时间正好来了两个人,他们一人一把钥匙,但是双方都再等着对方能交出钥匙来打开宝藏,谁都没释放自己的那把钥匙.就这样这俩人一直僵持下去,直到开发人员发现这个局面.导致死锁的根源在于不适当地运用“synchronized...
com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@d3ade7 ,项目启动错误
热门推荐
lgh_ken的专栏
06-29 2万+
在用hibernate，spring，struts，3个框架的做项目的时候，运行tomcat，报了下面一推错误：  [0629 18:12:30 285 WARN ]     ThreadPoolAsynchronousRunner.java:608 - com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetect
Tomcat启动项目出现com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector错误
weixin_43951534的博客
05-15 5658
15-May-2019 22:40:16.500 警告 [Timer-0] com.mchange.v2.async.ThreadPoolAsynchronousRunnerDeadlockDetector.runcom.mchange.v2.async.ThreadPoolAsynchronousRunnerDeadlockDetector.run com.mchange.v2.async.Th...
Exception in thread "com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#2"异常解决
weixin_30713953的博客
10-25 1468
java.lang.OutOfMemoryError: PermGen space表示你的内存永久保存区溢出了。PermGen space的全称是Permanent Generation space,是指内存的永久保存区域,这块内存主要是被JVM存放Class和Meta信息的,Class在被Loader时就会被放到PermGen space中,它和存放类实例(Instance)的Heap区域不同,...
com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@2929e5e9 -- APPARENT DEADLOCK!!!
hgsunyong的专栏
07-22 2884
MySQL数据库链接报错，上日志 2016-07-21 11:55:42,380 WARN [com.mchange.v2.async.ThreadPoolAsynchronousRunner]:608 - com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@2929e5e9 -- APPARENT DEADLOC
com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@4c6a5c15 -- APPARENT DEADLOCK!!!
Lan_Se_Tian_Ma的博客
07-09 1843
配置文件写错的可能性不大，应该是版本问题： mysql数据库版本 和 Java使用的mysql架包版本不相同 会导致报死锁异常 例： mysql数据库 8.0.15 版 Java就得使用 mysql 8.0.15 的架包 mysql 5.5 版 Java就得使用 5.1.39 的架包 不一定要对应一摸一样的版本，但首位版本号必须相同 下面写好的工具类和配置文件，可以直接...
(已解决)C3P0数据库使用配置文件链接，报错:com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector run...
avw0108的博客
04-11 3326
本帖简单来说，注意配置的xml文件中的“&”的写法，改成xml文件中支持的“&”即可解决问题。 其他类型的错误排查及排查步骤见下方 因为hibernate和spring等开源框架均使用C3P0来做来创建和管理连接。所以打算自己来体验一下C3P创建的具体过程，在使用C3P0指定的配置文件来创建连接执行简单操作测试时，出现了以下的错误： 四月 11, 201...
【解决方案】c3p0 APPARENT DEADLOCK创建紧急线程
songwenbinasdf的专栏
10-08 2万+
前言：最近碰见了一个非常稀奇古怪的问题，查遍google和baidu，只有2个人碰见的类似，但都还有差异，就此对c3p0产生 APPARENT DEADLOCK 的现象分析一遍 现象：8月10日晚18:20分左右，当日无发布的情况下，突然抛出一个这个异常，导致系统响应变慢，之后的3天内，均产生大量的异常，系统应用oracle数据库。 异常如下： Java代码  
Thread[com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#2,5,main] 异常解决办法
qq_34266804的博客
02-22 9566
转载：https://www.cnblogs.com/yuanlaihenkuang/p/7727022.html   java.lang.OutOfMemoryError: PermGen space 表示你的内存永久保存区溢出了。      PermGen space的全称是Permanent Generation space,是指内存的永久保存区域,       这块内存主要是被J...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值