RE: logging output

The place to start logging here is probably in ApplicationGateway - see
what's happening when a request is coming in and where the dispatching
process is going. ALso, make sure that the web.xml file in your app is up to
date with what's in Barracuda's web.xml.

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 Vladimir Ritz
> Bossicard
> Sent: Monday, February 02, 2004 1:32 AM
> To: Barracuda
> Subject: [Barracuda] logging output
>
>
> Hi all,
>
> I'll try to debug my problem and give you more infos about what's
> happening.
> Hopefully I can figure out what's going on.
>
> In the meantime, there's one thing that bugs me when I look at my server
> output:  the number of info statements of Barracuda.  Really, for a simple
> page I maybe have 60/70 lines in my log.  When writing to the file/console
> can be very costly, I think that some precious ms can be saved by moving
> these info statements into debug ones.  And not forgetting the if
> (log.isDebugEnabled()).
>
> Of course, I can set the log level to Info but IMO Info statement
> are worth
> being logged on a production environment, when debug ones clearly
> are not..
>
> But it's just my opinion.
>
> -Vladimir
>
> __________________________________
> Do you Yahoo!?
> Yahoo! SiteBuilder - Free web site building tool. Try it!
> http://webhosting.yahoo.com/ps/sb/
> _______________________________________________
> Barracuda mailing list
> [email protected]
> http://barracudamvc.org/lists/listinfo/barracuda