c3p0 不断的输出debug错误信息
2012-04-25 08:37
344 查看
在网上查了一些资料,这是c3p0连接管理为检测连接目标是否可连接的测试输出信息,可以忽略掉,把log4j的级别设为DEBUG就会输出,设为INFO以上就不会再输出了。
java.lang.Exception: DEBUG -- CLOSE BY CLIENT STACK TRACE
at com.mchange.v2.c3p0.impl.NewPooledConnection.close(NewPooledConnection.java:566)
at com.mchange.v2.c3p0.impl.NewPooledConnection.close(NewPooledConnection.java:234)
at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.destroyResource(C3P0PooledConnectionPool.java:470)
at com.mchange.v2.resourcepool.BasicResourcePool$1DestroyResourceTask.run(BasicResourcePool.java:964)
at com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:547)
08:35:28,668 DEBUG C3P0PooledConnectionPool:476 - Successfully destroyed PooledConnection: com.mchange.v2.c3p0.impl.NewPooledConnection@1f36445
08:35:28,669 DEBUG BasicResourcePool:967 - Successfully destroyed resource: com.mchange.v2.c3p0.impl.NewPooledConnection@1f36445
08:35:28,662 DEBUG NewPooledConnection:566 - com.mchange.v2.c3p0.impl.NewPooledConnection@121484b closed by a client.
java.lang.Exception: DEBUG -- CLOSE BY CLIENT STACK TRACE
at com.mchange.v2.c3p0.impl.NewPooledConnection.close(NewPooledConnection.java:566)
at com.mchange.v2.c3p0.impl.NewPooledConnection.close(NewPooledConnection.java:234)
at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.destroyResource(C3P0PooledConnectionPool.java:470)
at com.mchange.v2.resourcepool.BasicResourcePool$1DestroyResourceTask.run(BasicResourcePool.java:964)
at com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:547)
08:35:28,668 DEBUG C3P0PooledConnectionPool:476 - Successfully destroyed PooledConnection: com.mchange.v2.c3p0.impl.NewPooledConnection@1f36445
08:35:28,669 DEBUG BasicResourcePool:967 - Successfully destroyed resource: com.mchange.v2.c3p0.impl.NewPooledConnection@1f36445
08:35:28,662 DEBUG NewPooledConnection:566 - com.mchange.v2.c3p0.impl.NewPooledConnection@121484b closed by a client.
相关文章推荐
- c3p0 不断的输出debug信息 Log4j 指定项目的 输出级别
- 设置调试PHP,debug php输出所有错误信息
- C# DEBUG 调试信息打印及输出详解
- 错误 4 创建调试信息文件 ……obj\Debug\Sims.Reports.Data.pdb: 拒绝访问
- 由于内部错误,服务器无法处理该请求。有关该错误的详细信息,请打开服务器上的 IncludeExceptionDetailInFaults (从 ServiceBehaviorAttribute 或从 <serviceDebug> 配置行为)以便将异常信息发送回客户端,
- 将Linux脚本中的正常输出,警告,错误等信息输出到文件中
- cocos2d-x 输出debug信息
- android第四步查看应用输出的错误信息与如何部署应用到真实手机
- win32调试工具原理OutputDebugString以及如何获取输出信息
- 编译器错误信息: CS0016: 未能写入输出文件,..\Temporary ASP.NET Files\WebApp\d087da43\c12930d8\9ze28k_8.dll”--拒绝访问
- [ecshop 调试 ]ecshop中的 debug_mode 是在哪里定义的 查看sql日志 输出错误 显示debug
- 关闭jvm错误堆栈信息优化(不输出)
- Debug技巧-------控制台程序或者应用程序输出错误到txt
- 编译器错误信息: CS0016: 未能写入输出文件,..\Temporary ASP.NET Files\WebApp\d087da43\c12930d8\9ze28k_8.dll”--拒绝访问
- Logback在配置中不能正确输出debug信息的解决
- Linux Advance--输出错误信息
- C#将Trace,Debug信息输出到控件上
- 在手机上调试,输出Debug信息到计算机
- 在错误信息里输出N以内的素数
- 手机一连上Android Studio,Logcat不断输出信息