You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
2013-05-17 09:26:44,618 [MLog-Init-Reporter] [ INFO] MLog:106 - MLog clients using log4j logging.
2013-05-17 09:26:44,633 [MLog-Init-Reporter] [DEBUG] MLog:95 - Could not find resource path text file for path '/com/mchange/v2/cfg/vmConfigResourcePaths.txt'
2013-05-17 09:26:44,633 [MLog-Init-Reporter] [DEBUG] MLog:95 - Added paths from resource path text file at '/mchange-config-resource-paths.txt'
2013-05-17 09:26:44,633 [MLog-Init-Reporter] [DEBUG] MLog:95 - Reading VM config for path list /com/mchange/v2/log/default-mchange-log.properties, hocon:/reference.conf, /mchange-commons.properties, hocon:/application.conf, /c3p0.properties, hocon:/c3p0.conf, /mchange-log.properties, /
2013-05-17 09:26:44,633 [MLog-Init-Reporter] [DEBUG] MLog:95 - The configuration file for resource identifier 'hocon:/reference.conf' could not be found. Skipping.
java.io.FileNotFoundException: No resource available at '/reference.conf' for HOCON identifier 'hocon:/reference.conf'. Also HOCON lib (typesafe-config) is not available.
at com.mchange.v2.cfg.BasicMultiPropertiesConfig.configSource(BasicMultiPropertiesConfig.java:86)
at com.mchange.v2.cfg.BasicMultiPropertiesConfig.firstInit(BasicMultiPropertiesConfig.java:174)
at com.mchange.v2.cfg.BasicMultiPropertiesConfig.(BasicMultiPropertiesConfig.java:110)
at com.mchange.v2.cfg.ConfigUtils.read(ConfigUtils.java:57)
at com.mchange.v2.cfg.ConfigUtils.readVmConfig(ConfigUtils.java:106)
at com.mchange.v2.cfg.MLogConfigSource.readVmConfig(MLogConfigSource.java:46)
at com.mchange.v2.log.MLogConfig.(MLogConfig.java:58)
at com.mchange.v2.log.MLog.(MLog.java:50)
Action Taken
Revert to version 0.9.2.1
The text was updated successfully, but these errors were encountered:
hi. this is okay; it is not an error at all. note that these items are being logged at DEBUG level. the config library is checking in a bunch of places for config information, and logging at DEBUG where it has failed to find it. but there are now lots of different places config information can live. not finding it in any one particular place is not a problem. (maybe we shouldn't log the stack trace, because it freaks people out to see stack traces even in DEBUG logs?)
anything that users should consider an error will be logged by c3p0/mchange-commons-java at some level above INFO. logging can be quite verbose at DEBUG log levels. If these messages are bothersome to you, just edit your logging config so that the logger com.mchange.v2.log.MLog logs at INFO and above.
Version Used
Given this configuration in Spring 3
The following error was thrown
Action Taken
Revert to version 0.9.2.1
The text was updated successfully, but these errors were encountered: