Thread[com.mchange.v2.async.ThreadPoolAsynchronous

Managed Threads: 3
	Active Threads: 3
	Active Tasks: 
		com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@c22681 (com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#2)
		com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@6e12d5 (com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#0)
		com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@96613f (com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#1)
	Pending Tasks: 
		com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@ca81dd
		com.mchange.v2.resourcepool.BasicResourcePool$1DestroyResourceTask@113daba
		com.mchange.v2.resourcepool.BasicResourcePool$1DestroyResourceTask@7d0bbd
		com.mchange.v2.resourcepool.BasicResourcePool$1DestroyResourceTask@18dcc86
		com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@6e84ad
		com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@1c87a13
		com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@c6a26b
Pool thread stack traces:
	Thread[com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#2,5,main]
		com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:562)
	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.resourcepool.BasicResourcePool.doAcquire(BasicResourcePool.java:1026)
		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)

看以前同事的写的功能模块，一点击就死了。。。不知道什么原因？
c3po配置：

<bean id="dataSource" class="com.mchange.v2.c3p0.ComboPooledDataSource" destroy-method="close">
		<property name="driverClass" value="${jdbc.driverClassName}"/>
		<property name="jdbcUrl" value="${jdbc.url}"/>
		<property name="user" value="${jdbc.username}"/>
		<property name="password" value="${jdbc.password}"/>
		<property name="minPoolSize" value="10"/>
		<property name="maxPoolSize" value="20"/>
		<property name="initialPoolSize" value="10"/>
		<property name="maxIdleTime" value="30"/>
		<property name="maxStatements" value="0"/>
		<property name="idleConnectionTestPeriod" value="60"/>
	</bean>

评论

3 楼 cmzy 2009-05-19  

这个我也遇到了，请看这里http://www.iteye.com/topic/22160?page=3

2 楼 anzn20 2009-02-23  

lusen 写道

<property name="idleConnectionTestPeriod" value="60"/>
这个是检查连接池连接状态的周期，单位是毫秒，设为60毫秒有点短了。

一点就死，看日志抛了什么异常。可以通过jconsole监控c3p0连接池。

谢谢！

1 楼 lusen 2009-02-20  

<property name="idleConnectionTestPeriod" value="60"/>
这个是检查连接池连接状态的周期，单位是毫秒，设为60毫秒有点短了。

一点就死，看日志抛了什么异常。可以通过jconsole监控c3p0连接池。