james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Harmeet Bedi" <hb...@yahoo.com>
Subject Manual steps in Avalon Framework. Was: Logging levels being ignored
Date Sat, 21 Apr 2001 21:59:46 GMT
There are a few places in Avalon that require same name.
For example to add a block one needs to enter interrelated informaion in
- .xinfo file
- Manifest.mf
- server.xml for logging
- assembly.xml.

There seems to be some duplication and getting one or more of these wrong
can eat up a lot of time. Would it make sense to have code generators
automate some of these. One could specify information only once and have an
Ant target or a tool generate the correct files.

I wrote a python script to read assembly.xml and generate the block
dependent part of server.xml. Attaching it. Automating part of server.xml
removed logging issues in James. Maybe this, or something better should be
added to Avalon. I was thinking that having templates, data file and an Ant
Target would make things nicer.
In the meantime maybe a few python scripts could help. :-)

Harmeet

----- Original Message -----
From: "Peter Donald" <donaldp@apache.org>
Subject: Re: Logging levels being ignored
>

> At 10:15  20/4/01 -0400, Bob Johnson wrote:
> >As distributed, JAMES's logging "level" is set to DEBUG (the most
verbose).
> >I attempted (w/o success) to reduce this level by editing the
JAMES.xml.conf
> >line from
> >
> >  <channel name="default"      loglevel="DEBUG"  logwriter="default"/>
> >to
> >  <channel name="default"      loglevel="EMERGENCY"
logwriter="default"/>
> >
> >This attempt to go from one verbose extreme to the opposite is having NO
> >affect.  All the DEBUG level msgs still appear in the logfiles (I did
this
> >to all the channels).  I'm assuming that the loglevel strings are the
names
> >of the static int field names defined in the Logger interface.
> >
> >Is this a bug with logging, or cockpit-error on my part?
>
> It could be either. At one stage there was a bug in logging. Which version
> are you using? Another possibility is that the categories in config file
> may no longer line up with categories used in code.
> Cheers,
>
> Pete


Mime
View raw message