eclipse里启动tomcat报错，c3p0相关

最新推荐文章于 2021-05-08 21:58:03 发布
最新推荐文章于 2021-05-08 21:58:03 发布
阅读量2.8k 收藏 1
点赞数
文章标签： c3p0 eclipse tomcat thread c
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/lddongyu/article/details/6734465
版权
在使用Eclipse运行Tomcat时遇到警告，c3p0连接池报告出现潜在死锁问题。错误日志显示三个线程已激活并有多个未分配的待处理任务，涉及数据库连接的获取任务。可能的原因是数据库连接超时或配置问题。

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

在eclipse 里启动tomcat，程序报错：

2011-08-25 06:22:06,163 WARN  [com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector] com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@11ea65f -- APPARENT DEADLOCK!!! Cr
eating emergency threads for unassigned pending tasks!
2011-08-25 06:22:06,163 WARN  [com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector] com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@11ea65f -- APPARENT DEADLOCK!!! Co
mplete Status:
        Managed Threads: 3
        Active Threads: 3
        Active Tasks:
                com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@f27b6e (com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#0)
                com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@185982c (com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#2)
                com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@1c984f9 (com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#1)
        Pending Tasks:
                com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@13911fe
                com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@1cc75cb
                com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@4976d6
                com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@1190cfc
                com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@1a3b17a
                com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@1d8c794
                com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@11701fd
                com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@183bff8
                com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@b04d34
                com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@9c9874
                com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@dd151f
                com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@95aedf
                com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@10bc436
                com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@17ebdf8
                com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@1e9f2e2
                com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@48e2c5
                com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@1202a06
                com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@a71c9a
                com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@146c2cb
                com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@9ecc3e
                com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@172fbca
                com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@1f08e98
                com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@21a44e
                com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@aa1384
                com.mchange.v2.resourcepool.BasicResourcePool$1RefurbishCheckinResourceTask@1e76a88
                com.mchange.v2.resourcepool.BasicResourcePool$1RefurbishCheckinResourceTask@33d09
Pool thread stack traces:
        Thread[com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#0,5,main]
                java.net.SocketInputStream.socketRead0(Native Method)
                java.net.SocketInputStream.read(SocketInputStream.java:129)
                oracle.net.ns.Packet.receive(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:414)
                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,main]
                java.net.SocketInputStream.socketRead0(Native Method)
                java.net.SocketInputStream.read(SocketInputStream.java:129)
                oracle.net.ns.Packet.receive(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:414)
                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,main]
                java.net.SocketInputStream.socketRead0(Native Method)
                java.net.SocketInputStream.read(SocketInputStream.java:129)
                oracle.net.ns.Packet.receive(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:414)
                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)
 

用tomcat单独启动，没有问题，网上查了下说要改小3p0的链接数，改了不起作用，后来修改了下maxIdleTime的参数，从300改为了1000，错误就没再出现，不知道是什么原因。
lddongyu
关注
Method com/mchange/v2/c3p0/impl/NewProxyResultSet.isClosed()Z is abstract
qq_40187702的博客
04-19 1629
今天在搭建SSM框架的时候，使用了C3P0数据库连接池，服务器启动时报了异常，原因是导入的C3P0(c3p0-0.9.1.2版本)的jar包版本低了，可能是我的mysql版本是8.0吧，然后换成c3p0-0.9.5.2版本就可以了，不过此时还要导入另一个jar包mchange-commons-java-0.2.11.jar不然会报错。 1.如果用的是Eclipse,直接在lib文件夹下导入 2.如果是用IDEA，直接在pom.xml文件添加依赖 <dependency> <gro
c3p0连接池和hibernate应用
q124113的专栏
12-31 6167
如果用c3p0作连接池，如果数据库没开启的话，就会报死锁的错误APPARENT DEADLOCK!!! 出错不要紧，恶心的是这种死锁会让你，当你停止TOMCAT的时候报错，TOMCAT停止异常，如下。Disconnected from server2008-12-31 9:56:50 org.apache.catalina.startup.Catalina stopServer严重: Cata
Eclipse下启动tomcat常见报错（1）
codeRandom
11-16 1490
Eclipse下启动tomcat报错：/bin/bootstrap.jar which is referenced by the classpath, does not exist.
tomcat配置c3p0数据库连接池遇到问题与解决
anLA_的专栏
04-29 6138
这短时间在做一个Android项目，由于牵扯到数据库，也就有服务器。app预期是想做大，所以一方面考虑到性能相关 因此就想把tomcat和比较知名的c3p0结合起来，从这一方面来提高性能。 首先第一步：把c3p0解压文件夹的3个jar包全部考到tomcat根目录下lib文件夹下面，当然还有数据库连接jar包。 第二步：配置server.xml以及content.xml； server.xm
关于tomcat启动时卡在C3P0连接池，超时报错。相关信息如下图
qq_40728339的博客
12-10 1918
解决方案： 检查数据库服务是否开启 检查数据库连接信息是否正确 查看tomcat目录下webapps下的缓存，并清理 以上方案皆不能解决，可以尝试更换mysql connector的jar包 ...
eclipse web工程配置报错及解决
okkeqin的专栏
04-24 843
2013-4-24 15:07:37 org.apache.catalina.core.StandardContext listenerStart 严重: Error configuring application listener of class org.springframework.web.context.ContextLoaderListener java.lang.ClassNot
解决：com.mchange.v2.c3p0.impl.NewProxyResultSet.getNString(Ljava/lang/String;)Ljava/lang/String;]
小圣_fighting的博客
11-13 5765
前言：       在写一个项目的时候，使用Spring+SpringMVC+Mybatis框架，数据库连接池使用c3p0。在连接SqlServer时，一切都正常。当时当查询出来的结果中含有字段类型为nvarchar时，报出了以下错误： 严重: Servlet.service() for servlet [SpringMVC] in context with path [/mobile] th
ssm项目使用ecplise报错No mapping found for HTTP request with URI [/sky……]
非凡的博客
01-08 830
该项目我使用idea编译访问没有任何问题，但使用eclipse编译时报错No mapping found for HTTP request with URI [/sky-ssm/hello] in DispatcherServlet with name 'dispatcherServlet'首先我检查了 1、web.xml文件中的配置 <!DOCTYPE web-app PUBLIC "-...
徒手搭建SSM的maven项目（Eclipse版）
weixin_38319353的博客
12-22 1735
eclipse徒手搭建SSM的maven单项目前言出于目的整体规划关于SSM开始搭建配置JDK*添加tomcat*配置maven*创建项目解决项目初始化的一系列问题引入tomcat 的JAR包匹配JRE 版本补全maven项目结构配置webapp输出目录升级动态web 3.0修改项目编码启动web项目整合SSM目录结构和整合思路目录结构整合思路引入依赖分层配置web层配置文件约束必要配置文件上传解...
com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@6440b4f -- APPARENT DEADLOCK!!!
zyd773848285的博客
08-06 651
com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@6440b4f -- APPARENT DEADLOCK!!!问题解决 这是我之前的c3p0的配置，然后服务启动就出现标题所示的错误 修改c3p0配信息为： 以上配置信息来源于其他博主的配置方案，亲测有效。 ...
eclipse run on server 时 报的错误APPARENT DEADLOCK!!! Creating emergency threads for unassigned pending t...
dieyuanjiao9299的博客
08-02 1116
写这篇日记记录一下自己的愚蠢行为。 具体报错如下： 信息: Initializing c3p0 pool... com.mchange.v2.c3p0.ComboPooledDataSource [ acquireIncrement -> 10, acquireRetryAttempts -> 30, acquireRetryDelay -> 1000, autoC...
linux环境c3p0死锁,C3P0表观死锁时，我的Tomcat启动
weixin_32306175的博客
05-08 238
，当我用Tomcat或树脂开始我的项目，我的项目将引发错误：视死锁C3P0表观死锁时，我的Tomcat启动我认为造成C3P0错误无法连接我的数据库，我改变我的XML，并通过我的数据库的ip替换域名，然后项目启动！我在我的c3p0工作之前使用了一个侦听器，我可以得到正确的域名和ip，我找不到APPARENT DEADLOCK的原因。012-10-22 16:53:04 24344 WARN [Tim...
c3p0 mysql tomcat_C3P0数据库连接池与tomcat一起使用时报错
weixin_39790760的博客
01-25 121
C3P0在自己做单元测试的时候不报错,生成web项目以后只要采用相应的连接就会报错相应配置如下:报错信息如下:六月 26, 2016 4:20:50 下午 org.apache.catalina.core.ApplicationContext log信息: No Spring WebApplicationInitializer types detected on classpath六月 26, 2...
c3p0连接mysql异常
MeiBlog
10-20 940
com.mchange.v2.resourcepool.TimeoutException: A client timed out while waiting to acquire a resource from com.mchange.v2.resourcepool.BasicResourcePool@79207381 -- timeout at awaitAvailable() 网上的整体解决...
c3p0连接池配置_关于eclipse使用c3p0连接池连接mysql8.0.19配置c3p0-config.xml文件
weixin_40006185的博客
11-28 355
c3p0-config.xml文件模板<?xml version="1.0" encoding="UTF-8" ?> <c3p0-config> <default-config> <property name="driverClass">com.mysql.cj.jdbc.Driver</property> <prop...
Tomcat启动时执行到Initializing c3p0 pool... com.mchange.v2.c3p0.ComboPooledDataSource...时卡住
热门推荐
宋铮的博客
08-11 1万+
在Eclipse中启动Tomcat时，当执行到Initializing c3p0 pool… com.mchange.v2.c3p0.ComboPooledDataSource [ acquireIncrement -> 5, acquireRetryAttempts -> 30, acquireRetryDelay -> 1000, autoCommitOnClose -> false, auto
eclipse中启动tomcat报错
03-16
您好，可能是由于以下原因导致eclipse启动tomcat报错： 1. Tomcat配置错误：请检查您的Tomcat配置是否正确，例如端口号、路径等。 2. Eclipse配置错误：请检查您的Eclipse配置是否正确，例如Tomcat版本、路径等。 3. 项目配置错误：请检查您的项目配置是否正确，例如web.xml、servlet等。 4. 环境配置错误：请检查您的Java环境配置是否正确，例如JDK版本、路径等。 建议您逐一排查以上原因，找到具体原因后进行修复。如果还有问题，请提供具体错误信息，以便更好地帮助您解决问题。
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值