最近在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. CDH集群搭建部署

    1. 硬件准备     使用了五台机器,其中两台8c16g,三台4c8g.一台4c8g用于搭建cmServer和NFS服务端,另外4台作为cloudera-manager agent部署CDH集群. ...

  2. YiShop_网上商城系统多少钱

    电子商务的发展,网上商城系统的开发也变得越来越热门.商城系统开发对于企业来说是非常有必要的,一个好的网上商城系统对于企业来说是非常重要.那么到底网上商城系统多少钱呢?下面YiShop带大家去了解. 网 ...

  3. 【下一代核心技术DevOps】：（一）容器服务的Rancher选型

    为什么说是下一代核心技术 其实经过互联网的多次变革说起,早期的C/S架构,到后来的B/S架构,一直到现在最普遍的M/S架构,他们的背后都是技术不断的优化改进,以适应促进IT技术的发展 整体而言在过去1 ...

  4. 虚拟DOM详解

    虚拟DOM简介 Virtual Dom可以看做一棵模拟了DOM树的JavaScript对象树,其主要是通过vnode,实现一个无状态的组件,当组件状态发生更新时,然后触发Virtual Dom数据的变 ...

  5. Java-----SSM（SpringMVC+Spring+mybaties）框架整合

    在进行整合之前,首先了解这个框架的作用 Mybaties: 丰富的标签库,可写动态sql,并统一的在.XML文件中编写,方便统一管理,解耦 SpringMVC: 标准的MVC思想(mode,view, ...

  6. 3.python元组与列表

    Python的元组与列表类似,同样可通过索引访问,支持异构,任意嵌套.不同之处在于元组的元素不能修改.元组使用小括号,列表使用方括号. 创建元组 元组创建很简单,只需要在括号中添加元素,并使用逗号隔开 ...

  7. 【回文】leetcode - Shortest Palindrome

    题目: Shortest Palindrome Given a string S, you are allowed to convert it to a palindrome by adding ch ...

  8. 25个增强iOS应用程序性能的提示和技巧(0基础篇)

    在开发iOS应用程序时,让程序具有良好的性能是非常关键的. 这也是用户所期望的,假设你的程序执行迟钝或缓慢,会招致用户的差评.然而因为iOS设备的局限性,有时候要想获得良好的性能,是非常困难的. 在开 ...

  9. Java深入 - MyBatis的经常用法

    MyBatis我们这篇文章主要记录一些经常使用的操作方法.这样在开发和使用的过程中这篇文章能够当做工具书来使用. MyBatis的数据源配置 <bean id="dataSource& ...

  10. iKcamp团队制作｜基于Koa2搭建Node.js实战（含视频）☞ 路由koa-router

    路由koa-router--MVC 中重要的环节:Url 处理器