In the log messages and stack traces that you've shown, there is nothing wrong at all. These are all DEBUG
level messages. (c3p0
& com.mchange
libraries should usually be logged at INFO
.)
c3p0
& mchange-commons-java
check for potential config information in lots of different places. In many of those places, they find nothing, and so move on. Logging at DEBUG
, you are watching the process of libraries checking for, e.g., /mchange-log.properties
, in the CLASSPATH
and failing to find it. At DEBUG
, the libraries log that they looked, that they did not find, and the Exception that went along with not finding.
None of this is of concern at all. It is normal.
The main question is whether the config users put in c3p0-config.xml
is taking. You are using a relative directory for the file, rather than an absolute filesystem location. I presume that will work, with relative being interpreted relative to the working directory of the process, but I'm not sure it will work, and even if it does, are you sure that it won't be fragile, depend on how users start up your process? Will users run a script that will ensure the proper working directory?