You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lenya.apache.org by Michael Wechner <mi...@wyona.com> on 2005/05/13 01:05:11 UTC
set loglevel to WARN instead ERROR
Dear All
I think we should set the loglevel to WARN instead ERROR within
src/webapp/WEB-INF/log4j.xconf
because quite a lot of messages which can be very helpful during runtime
are being missed, whereas on the other hand there aren't that many WARNINGS
generated, so it shouldn't be a performance problem.
WDYT?
Michi
--
Michael Wechner
Wyona Inc. - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
michael.wechner@wyona.com michi@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: set loglevel to WARN instead ERROR
Posted by "Gregor J. Rothfuss" <gr...@apache.org>.
Michael Wechner wrote:
> Dear All
>
> I think we should set the loglevel to WARN instead ERROR within
>
> src/webapp/WEB-INF/log4j.xconf
>
> because quite a lot of messages which can be very helpful during runtime
> are being missed, whereas on the other hand there aren't that many WARNINGS
> generated, so it shouldn't be a performance problem.
you might be right that lenya has not too many warnings, but what about
cocoon?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org