网上搜了下,看到有个老外出了这个问题,发邮件不知道是不是给c3p0的开发团队,回复如下
hi, you are logging c3p0 libs at DEBUG levels. c3p0 / com.mchange libs are intended to be logged at INFO. you’ll get a lot of superfluous information, including Exception stack traces, if you log at less restrictive levels than INFO. c3p0 and its supporting libraries permit configuration resources to be put in a variety of places, including the resource-path '/mchange-commons.properties’. c3p0 looks in those places. at DEBUG levels, it reports not finding anything there, and the Exception that signals failing to find anything. please set your log level for com.mchange libs to INFO. turn on DEBUG level logging only when you have an issue to investigate (and ideally do so selectively, for particular classes or packages, to avoid a firehose of unwanted information).
However, I’d recommend that you set INFO as the default (it’s how most third-party libraries expect to be logged), and make the Exception your own application, which should log at DEBUG. Suppose that your application lives in the package edu.cmu.aforget. Then…
意思很明白,这是警告,不是异常,别把c3p0的日志级别搞成debug。大多数第三方开源软件的建议都是info级别,你自己的可以是debug,如果你把第三方的这些都搞成debug了,那活该你出异常
本文针对 C3P0 连接池的日志级别配置问题进行了解答,指出将其设置为 DEBUG 级别会导致大量冗余信息输出,并推荐使用 INFO 级别。同时建议将自定义应用程序的日志级别设为 DEBUG 以便于调试。
1万+

被折叠的 条评论
为什么被折叠?



