最近在IDEA中启动Tomcat经常会碰到这个错误，起初、一直没在意，现在碰到的次数多了，就去查看下这个问题，现描述如下：

=2018-01-08 14:27:30,216 WARN  [com.mchange.v2.async.ThreadPoolAsynchronousRunner] - com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@29165a67 -- APPARENT DEADLOCK!!! Complete Status:

    Managed Threads: 3

    Active Threads: 3

    Active Tasks:

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

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

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

    Pending Tasks:

        com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@25f19032

        com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@1631d614

        com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@21ddc66e

        com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@670e7120

        com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@652520bb

        com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@688808dd

        com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@3afe1ac8

Pool thread stack traces:

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

        java.net.PlainSocketImpl.socketConnect(Native Method)

        java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:351)

        java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:213)

        java.net.PlainSocketImpl.connect(PlainSocketImpl.java:200)

        java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)

        java.net.Socket.connect(Socket.java:529)

        java.net.Socket.connect(Socket.java:478)

        java.net.Socket.<init>(Socket.java:375)

        java.net.Socket.<init>(Socket.java:189)

        oracle.net.nt.TcpNTAdapter.connect(Unknown Source)

        oracle.net.nt.ConnOption.connect(Unknown Source)

        oracle.net.nt.ConnStrategy.execute(Unknown Source)

        oracle.net.resolver.AddrResolution.resolveAndExecute(Unknown Source)

        oracle.net.ns.NSProtocol.establishConnection(Unknown Source)

        oracle.net.ns.NSProtocol.connect(Unknown Source)

        oracle.jdbc.driver.T4CConnection.connect(T4CConnection.java:844)

        oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:268)

        oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:420)

        oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:165)

        oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:35)

        oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:801)

        com.mchange.v2.c3p0.DriverManagerDataSource.getConnection(DriverManagerDataSource.java:134)

        com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:182)

        com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:171)

        com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.acquireResource(C3P0PooledConnectionPool.java:137)

        com.mchange.v2.resourcepool.BasicResourcePool.doAcquire(BasicResourcePool.java:1014)

        com.mchange.v2.resourcepool.BasicResourcePool.access$800(BasicResourcePool.java:32)

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

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

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

        java.net.PlainSocketImpl.socketConnect(Native Method)

        java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:351)

        java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:213)

        java.net.PlainSocketImpl.connect(PlainSocketImpl.java:200)

        java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)

        java.net.Socket.connect(Socket.java:529)

        java.net.Socket.connect(Socket.java:478)

        java.net.Socket.<init>(Socket.java:375)

        java.net.Socket.<init>(Socket.java:189)

        oracle.net.nt.TcpNTAdapter.connect(Unknown Source)

        oracle.net.nt.ConnOption.connect(Unknown Source)

        oracle.net.nt.ConnStrategy.execute(Unknown Source)

        oracle.net.resolver.AddrResolution.resolveAndExecute(Unknown Source)

        oracle.net.ns.NSProtocol.establishConnection(Unknown Source)

        oracle.net.ns.NSProtocol.connect(Unknown Source)

        oracle.jdbc.driver.T4CConnection.connect(T4CConnection.java:844)

        oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:268)

        oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:420)

        oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:165)

        oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:35)

        oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:801)

        com.mchange.v2.c3p0.DriverManagerDataSource.getConnection(DriverManagerDataSource.java:134)

        com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:182)

        com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:171)

        com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.acquireResource(C3P0PooledConnectionPool.java:137)

        com.mchange.v2.resourcepool.BasicResourcePool.doAcquire(BasicResourcePool.java:1014)

        com.mchange.v2.resourcepool.BasicResourcePool.access$800(BasicResourcePool.java:32)

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

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

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

        java.net.PlainSocketImpl.socketConnect(Native Method)

        java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:351)

        java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:213)

        java.net.PlainSocketImpl.connect(PlainSocketImpl.java:200)

        java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)

        java.net.Socket.connect(Socket.java:529)

        java.net.Socket.connect(Socket.java:478)

        java.net.Socket.<init>(Socket.java:375)

        java.net.Socket.<init>(Socket.java:189)

        oracle.net.nt.TcpNTAdapter.connect(Unknown Source)

        oracle.net.nt.ConnOption.connect(Unknown Source)

        oracle.net.nt.ConnStrategy.execute(Unknown Source)

        oracle.net.resolver.AddrResolution.resolveAndExecute(Unknown Source)

        oracle.net.ns.NSProtocol.establishConnection(Unknown Source)

        oracle.net.ns.NSProtocol.connect(Unknown Source)

        oracle.jdbc.driver.T4CConnection.connect(T4CConnection.java:844)

        oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:268)

        oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:420)

        oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:165)

        oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:35)

        oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:801)

        com.mchange.v2.c3p0.DriverManagerDataSource.getConnection(DriverManagerDataSource.java:134)

        com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:182)

        com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:171)

        com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.acquireResource(C3P0PooledConnectionPool.java:137)

        com.mchange.v2.resourcepool.BasicResourcePool.doAcquire(BasicResourcePool.java:1014)

        com.mchange.v2.resourcepool.BasicResourcePool.access$800(BasicResourcePool.java:32)

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

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

在一番求知的过程中，大概了解到这个问题出现的几种可能情况，随记录下来，以供后人鉴赏：

1.数据库服务没有启动

大千世界无奇不有，这种错也有人遇到的话，真不想说什么了；如果是故意测试的话呢，个人感觉还是没有必要的，毕竟不开启数据库服务就去连接数据库，你让人作何感想啊。

2.没有创建对应数据库

这个问题同上，访问不到数据库，都不是技术性的问题，在此、不多啰嗦。

3.就涉及到c3p0连接池的配置文件了

这个问题就比较偏重于技术层面了，相关解决方案介绍如下：

①maxStatements 和checkoutTimeout

JDBC的标准参数，用以控制数据源内加载的PreparedStatements数量。但由于预缓存的statements属于单个connection而不是整个连接池。所以设置这个参数需要考虑到多方面的因素。如果maxStatements与maxStatementsPerConnection均为0，则缓存被关闭。Default: 0。

通过上面的描述，解决方案：

<property name="maxStatements" value="0"/> 

<property name="checkoutTimeout" value="100"/> 

②maxPoolSize和initialPoolSize

关于这方面，我大概能够了解到我个人的问题是由于这个原因导致的。由于数据库的连接数是有限的，每有应用启动C3p0都会占用数据库的连接来填充C3p0的连接池，而当数据库的资源被占光时就会因为无法获得共享资源而报死锁。

③更新c3p0的包

至于c3p0的包版本过旧造成的，这大概是历史遗留的问题。低版本c3p0包会导致获取连接的时间过长而在获取新的连接时造成死锁，具体请参考stackoverflow中别人提出的一个问题

The tasks that are dealocking are Connection acquisition tasks. That is, c3p0 is trying to acquire new Connections from your database, and those Connection acquisition attempts are taking a long time.

The first thing I would do is upgrade to 0.9.2.1, which has a much improved means of performing a round of Connection acquisitions in situations where acquisition attempts sometimes fail.

If that doesn't solve your problem, then you'll need to figure out why c3p0's attempts to acquire a Connection are hanging for long periods of time: neither succeeding nor failing with an Exception.

com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector APPARENT DEADLOCK的更多相关文章

  1. com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@1035079 -- APPARENT DEADLOCK!!! Complete Status:

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

  2. C3P0连接池问题，APPARENT DEADLOCK!!! Creating emergency..... [问题点数：20分，结帖人lovekong]

    采用c3p0连接池,每次调试程序,第一次访问时(Tomcat服务器重启后再访问)都会出现以下错误,然后连接库需要很长时间,最终是可以连上的,之后再访问就没问题了,请高手们会诊一下,希望能帮小弟解决此问 ...

  3. C3P0 APPARENT DEADLOCK

    一,c3p0执行一段时间后报错例如以下 W 07-26_00:58:27 ThreadPoolAsynchronousRunner.java 608 com.mchange.v2.async.Thre ...

  4. 解决 APPARENT DEADLOCK!!! Creating emergency threads for unassigned pending tas

    报错信息:APPARENT DEADLOCK!!! Creating emergency threads for unassigned pending tasks! 在网上查了一下,大部分网友分析是c ...

  5. eclipse run on server 时 报的错误APPARENT DEADLOCK!!! Creating emergency threads for unassigned pending tasks!

    写这篇日记记录一下自己的愚蠢行为. 具体报错如下: 信息: Initializing c3p0 pool... com.mchange.v2.c3p0.ComboPooledDataSource [ ...

  6. c3p0 APPARENT DEADLOCK!!! Creating emergency threads for unassigned pending tasks

    2018-01-04 15:02:03,319 ---com.mchange.v2.async.ThreadPoolAsynchronousRunner: com.mchange.v2.async.T ...

  7. APPARENT DEADLOCK！！！c3p0数据库连接池死锁问题

    项目进行压力测试的时候,运行大概1小时候,后台抛出以下异常: Nov 9, 2012 1:41:59 AM com.mchange.v2.async.ThreadPoolAsynchronousRun ...

  8. c3p0 空指针异常 com.mchange.v2.resourcepool.CannotAcquireResourceException: A ResourcePool could not acquire a resource from its primary factory or source.

    com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@11d9f05 -- Acquisition Attempt Failed!!! C ...

  9. com.mchange.v2.c3p0.impl.NewPooledConnection@be1839d closed by a client的正确解答

    关于c3p0在debug模式下控制台抛出的如下异常: java.lang.Exception: DEBUG -- CLOSE BY CLIENT STACK TRACE at com.mchange. ...

随机推荐

  1. Android 从零搭建简单MVP Demo

    首先简单介绍一下MVP的构成及优缺点: MVP的全称为Model-View-Presenter, Model提供数据(网络请求.数据存储等): View负责页面显示: Presenter负责逻辑的处理 ...

  2. hdoj 1285 确定比赛名次 【拓扑排序】

    确定比赛名次 Time Limit: 2000/1000 MS (Java/Others)    Memory Limit: 65536/32768 K (Java/Others) Total Sub ...

  3. POJ 1661 Help Jimmy(DP,注意边界)

    Help Jimmy Time Limit: 1000MS   Memory Limit: 10000K Total Submissions: 9399   Accepted: 3025 Descri ...

  4. 2014/08/23——OJ及相关站点打开速度非常慢，训练计划login直接error！

    问题: 这个问题存在已经将近一个星期了.刚開始时发现OJ及相关的站点有时候打开有点慢,那时候也没在意,后来时快时慢的越来越频繁:今天早上直接一直都打开非常慢(无论什么时候.这样的情况);训练计划和做题 ...

  5. C++ Primer高速入门之三：几种常见的控制语句

    语句总是顺序运行的:第一条语句运行完了接着是第二条,第三条等等.这是最简单的情况,为了更好的控制语句的运行.程序设计语言提供了多种控制结构支持更为复杂的语句运行.我们就来看看C++ 提供的控制方式. ...

  6. Node.js显示页面

    首先我们先要下载并安装Nodejs,然后进入Node.js中安装supervisor, npm -g install supervisor -g表示全局模式 (无论windows哪一个用户登陆都可以使 ...

  7. 《About Face 3：交互设计精髓》【PDF】下载

    <About Face 3:交互设计精髓>[PDF]下载链接: https://u253469.pipipan.com/fs/253469-230384328 内容简介 全书分成3篇:第1 ...

  8. loadrunner录制、加载以及分析过程

    loadrunner主要组件包括: Virtual User Generator(录制脚本,编写脚本直到调通) Controller(加载脚本,设计并发人数.监控点之类的,模拟场景,开始性能测试,最后 ...

  9. iOS 应用中加载文档pdf／word／txt

    一.加载PDF文档:应用内打开文档.手机中其他应用打开文档 Demo 首先拖入一个文档pdf.word.txt,打开不同的文档知识 文件名字.类型修改即可 #import "ReadView ...

  10. 如何用VSCode愉快的写Python

    在学习Python的过程中,一直没有找到比较趁手的第三方编辑器,用的最多的还是Python自带的编辑器.由于本人用惯了宇宙第一IDE(Visual Studio),所以当Visual Studio C ...