cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Crossley <cross...@apache.org>
Subject Re: dealing with log messages from ehcache
Date Wed, 07 Dec 2005 05:08:02 GMT
Carsten Ziegeler wrote:
> Cocoon 2.2 uses "running modes" for resolving properties. In the
> WEB-INF/properties directory, you'll find two modes"prod" and "dev". By
> default, 2.2 is running in dev mode which overrides all log levels
> defined in the logkit config and sets them to DEBUG.
> 
> You can either set the running mode to "prod" by setting the system
> property -Dorg.apache.cocoon.mode=prod on startup, or you can remove the
> org.apache.cocoon.override.loglevel=DEBUG from the core.properties file
> in the "dev" directory.
> 
> Note, that "dev" and "prod" are not predefined. So you can create a
> "forrest-dev" directory underneath the properties directory and set the
> running mode to "forrest-dev" etc.
> 
> HTH
> Carsten

That certainly does help to explain the difference
in log-levels. Thanks Carsten.

Someone should document that :-)

The original problem still remains. How does Cocoon
manage to get logkit to handle the ehcache messages,
whereas with Forrest they come to the console?

-David

> David Crossley wrote:
> > Can anyone explain the following difference ...
> > 
> > Doing 'cocoon.sh' with 2.2 trunk at my local working copy,
> > with all default blocks. The logfile is filling up with
> > EHCache debug messages into the logfile at
> > build/webapp/WEB-INF/logs/cocoon.log
> > 
> > At cocoon.zones.apache.org i cannot find any mention
> > of ehcache in the logs of the trunk demo.
> > 
> > Why is it so?
> > 
> > -David
> > 
> > David Crossley wrote:
> > 
> >>As you know, at Apache Forrest we use Cocoon 2.2 trunk.
> >>
> >>A few months ago we upgraded our packaged Cocoon.
> >>Now we get messages from EHCache coming to stdout
> >>when we use our Jetty demo webapp.
> >>
> >>Of course tweaking WEB-INF/logkit.xconf has no effect
> >>because they are coming to the console.
> >>
> >>However, when going to Cocoon trunk and using
> >>'./cocoon.sh servlet' the ehcache messages are
> >>properly handled by logkit.xconf
> >>
> >>So what is the difference? Are we missing some
> >>configuration?
> >>
> >>Another issue is that in both Cocoon trunk and
> >>at Forrest, the loglevel for these cache messages
> >>are at DEBUG, so the logs fill up rapidly. How can
> >>we set its loglevel to something else?
> >>
> >>-David

Mime
View raw message