RE: Enhydra 5.1 Development Team, problems with Barracuda logs
"Christian Cryder" <[email protected]>
| Newsgroups | gmane.comp.java.enhydra.barracuda.general |
|---|---|
| Message-ID | <[email protected]> |
By default, the only Barracuda logging that I would set would be for the
ObjectRepositoryAssembler...
<logger
name="org.enhydra.barracuda.plankton.data.ObjectRepositoryAssembler"><level
value="warn"/><appender-ref ref="A1"/></logger>
If something blows up while parsing the object-repository file, then you
really want to know about that. But here in our projects we leave all other
logging turned off until we actually need to debug something specific.
That help?
CHristian
----------------------------------------------
Christian Cryder
Internet Architect, ATMReports.com
Project Chair, BarracudaMVC - http://barracudamvc.org
----------------------------------------------
"Coffee? I could quit anytime, just not today"
> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]]On Behalf Of Zoran Milakovic
> Sent: Monday, September 22, 2003 6:27 AM
> To: [email protected]
> Subject: [Barracuda] Enhydra 5.1 Development Team, problems with
> Barracuda logs
>
>
>
>
> Enhydra Development Team preparing new release of Enhydra5.1 final!
> We have too much log messages in log file on INFO log level with
> Barracuda. Is it possible to turn off that logging somehow or replace
> log messages to DEBUG level?
> Please answer as soon as possible.
>
> Enhydra Development Team,
> 22.09.2003
>
> _______________________________________________
> Barracuda mailing list
> [email protected]
> http://barracudamvc.org/lists/listinfo/barracuda