com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@d3ade7 ,项目启动错误

最新推荐文章于 2022-06-26 14:17:47 发布
最新推荐文章于 2022-06-26 14:17:47 发布
阅读量6.5k 收藏
点赞数
分类专栏： Java Web开发 中间件技术
在使用Hibernate、Spring和Struts框架开发项目时，遇到Tomcat启动时出现死锁警告。通过检查发现是因为未创建所需的数据库，创建数据库后问题得到解决。

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

在用hibernate，spring，struts，3个框架的做项目的时候，运行tomcat，报了下面一推错误：


[0629 18:12:30 285 WARN ]     ThreadPoolAsynchronousRunner.java:608 - com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@d3ade7 -- APPARENT DEADLOCK!!! Creating emergency threads for unassigned pending tasks!

[0629 18:12:30 301 WARN ]     ThreadPoolAsynchronousRunner.java:624 - com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@d3ade7 -- APPARENT DEADLOCK!!! Complete Status: 

Managed Threads: 3

Active Threads: 3

Active Tasks: 

com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@140fee (com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#2)

com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@121fd61 (com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#1)

com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@82254d (com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#0)

Pending Tasks: 

com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@5f1ae9

com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@1dfc8a0

com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@ec898a

Pool thread stack traces:

Thread[com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#2,5,main]

java.lang.Thread.sleep(Native Method)

com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask.run(BasicResourcePool.java:1805)

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

Thread[com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#1,5,main]

java.lang.Thread.sleep(Native Method)

com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask.run(BasicResourcePool.java:1805)

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

Thread[com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#0,5,main]

java.lang.Thread.sleep(Native Method)

com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask.run(BasicResourcePool.java:1805)

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

 

弄了好久，上网也查了很久，最后没有答案，

 

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

 

吃了顿饭回来，忽然想到自己都没有在数据库里面创建一个要连接的database，所以才导致这个错误，

 

果断创建数据库，启动项目，OK，问题解决，

 

有时候真的是需要一些灵感,,,,


该博文转载自http://blog.youkuaiyun.com/kevingavinhu/article/details/6575632

死锁 com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector
amyzhang1234的博客
01-08 3984
最近在IDEA中启动Tomcat经常会碰到这个错误，起初、一直没在意，现在碰到的次数多了，就去查看下这个问题，现描述如下： =2018-01-08 14:27:30,216 WARN [com.mchange.v2.async.ThreadPoolAsynchronousRunner] - com.mchange.v2.async.ThreadPoolAsynchronousRu...
[com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector.run(ThreadPoolAsynchronousR（已解决）
车马去闲闲——落日满秋山
04-01 792
使用tomcat启动程序时，报错。出现该警告的原因：数据库连接失败。
(已解决)C3P0数据库使用配置文件链接，报错:com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector run...
avw0108的博客
04-11 3325
本帖简单来说，注意配置的xml文件中的“&”的写法，改成xml文件中支持的“&”即可解决问题。 其他类型的错误排查及排查步骤见下方 因为hibernate和spring等开源框架均使用C3P0来做来创建和管理连接。所以打算自己来体验一下C3P创建的具体过程，在使用C3P0指定的配置文件来创建连接执行简单操作测试时，出现了以下的错误： 四月 11, 201...
com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@4c6a5c15 -- APPARENT DEADLOCK!!!
Lan_Se_Tian_Ma的博客
07-09 1841
配置文件写错的可能性不大，应该是版本问题： 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@8988e90 -- APPARENT DEADLO
weixin_55051400的博客
06-26 3402
最近在跟着学校学习动态javaweb，利c3p0时出现如下错误，大概意思连接超时，找了好多，都说是c3p0配置文件的问题，最后发现与mysql版本有关，从8降低到5.5，成功查到了数据库内容报错内容如下
C3P0访问数据库死锁，com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@128e59b3 -- APPARENT
qq_34091223的博客
05-31 4102
错误信息：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
看起来是数据库连接池的问题，可能涉及c3p0库，因为com.mchange.v2包是c3p0的。用户可能在使用Hibernate或者某个需要连接池的框架时遇到了这个问题。 首先，死锁警告意味着线程池中的线程无法及时获取资源，导致...
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连接池的日志，需要分析其中的问题。首先，我需要理解日志中的各个部分。日志开始显示c3p0连接池初始化，然后出现多个警告，提示“APPARENT DEADLOCK!!!”，还有任务未能完成，尝试中断。...
警告: com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@513098 -- APPARENT DEADLOCK!!
陈楚东的专栏-学编程切记心浮气躁，贵在坚持
06-02 8065
当我们在配置成 p出现以下这些错误：
com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector
weixin_42140424的博客
09-10 5064
警告: com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@4cb6a6e0 -- APPARENT DEADLOCK!!! Creating emergency threads for unassigned pending tasks! 9月 10, 2019 9:25:06 下午 com.mchange.v2.a...
Tomcat启动项目出现com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector错误
weixin_43951534的博客
05-15 5649
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...
com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@390508 -- APP
lh19900706的博客
01-29 548
最近项目运行时总是出现这个警告，改过很多次数据库连接池配置也没弄好，现在终于解决了。之前出错的连接池配置:[code="java"] [/code] 出错信息： [code="java"]WARN - com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@390508 -- APPAR...
com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@6fb530e0
xfy18317776108的博客
01-25 784
查看一下数据库是否正常可以链接，我的就是本地链接阿里云的rds数据库时，由于本地的公网ip改变导致的链接不上，将新的ip地址添加进入白名单中即可...
idea中Exception in thread "com.mchange.v2.async.ThreadPoolAsynchronousRunner
lucky
12-06 1107
dea中Exception in thread "com.mchange.v2.async.ThreadPoolAsynchronousRunner Java.lang.OutOfMemoryError: PermGen space 内存溢出错误，解决办法 修改TOMCAT_HOME/bin/catalina.sh 在“echo "Using CATALINA_BASE: $C
com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@6440b4f -- APPARENT DEADLOCK!!!
zyd773848285的博客
08-06 656
com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@6440b4f -- APPARENT DEADLOCK!!!问题解决 这是我之前的c3p0的配置，然后服务启动就出现标题所示的错误 修改c3p0配信息为： 以上配置信息来源于其他博主的配置方案，亲测有效。 ...
com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@1c023d89 -- APPARENT DEADLOCK!!!
u013794793的博客
09-14 1090
完整问题没法复现了，导致的结果就是数据库连接不上，猜测可能是之前的操作导致数据库死锁进而导致数据库服务停止，如果不是这个原因可能需要其他解决方法。我的解决方法：查看任务管理器中MYSQL服务是否启动，若未启动右键启动
Exception in thread "com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThrea
ITaerial的博客
07-30 561
Exception in thread "com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#2"       Exception in thread "com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#2" java.lang.OutOfMe...
com.mchange.v2.async.ThreadPoolAsynchronousRunner ERROR BasicResourcePool:1853 - A RESOURCE POOL IS
u011035531的专栏
04-24 1436
今天部署项目，项目的配置如下： 数据库：mysql-5.7 JDK：1.8 Tomcat：tomcat 8 框架：hibernate+spring+springmvc 部署的时候启动项目后，发现c3p0（连接池）在获取数据库连接的时候报错，错误如下：  com.mchange.v2.async.ThreadPoolAsynchronousRunner ERROR BasicReso
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值