Thread: [c3p0-users] Configuring Logs for c3p0
Status: Beta
Brought to you by:
swaldman
From: Madonesa s. <san...@gm...> - 2008-04-24 04:09:48
|
Hi All, I want to log the FINE level log entries. I have added the following entry into the mchange-log.properties com.mchange.v2.log.FallbackMLog.DEFAULT_CUTOFF_LEVEL=FINE But I still the FINE level logs are not logged. Could someone help me to configure the c3p0 logging correctly Best Regards, Sanjaya. |
From: Steve W. <swa...@mc...> - 2008-04-24 04:21:51
|
Hi. That only works if c3p0 cannot find either log4j or the jdk14 logging library. It configures c3p0's "fallback" logging scheme (to stderr), which is (and should be) very rarely used. Configure c3p0's log levels in whatever logging library you use. c3p0 generally uses the fully-qualified classname convention for logger names, so if you want to see everything c3p0 has to spew (which may be a lot), just set your logger to dump FINE (or FINEST) / DEBUG level info for all loggers starting with com.mchange. If you know what you're interested in, go ahead and filter by package name or fully qualified class name. smiles, Steve On Apr 24, 2008, at 12:09 AM, Madonesa sanjaya wrote: > Hi All, > > I want to log the FINE level log entries. I have added the following > entry into the mchange-log.properties > > com.mchange.v2.log.FallbackMLog.DEFAULT_CUTOFF_LEVEL=FINE > > But I still the FINE level logs are not logged. > > Could someone help me to configure the c3p0 logging correctly > > Best Regards, > Sanjaya. > ------------------------------------------------------------------------- > This SF.net email is sponsored by the 2008 JavaOne(SM) Conference > Don't miss this year's exciting event. There's still time to save > $100. > Use priority code J8TL2D2. > http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone_______________________________________________ > c3p0-users mailing list > c3p...@li... > https://lists.sourceforge.net/lists/listinfo/c3p0-users ~oo~ Steve Waldman swa...@mc... |