On 7/29/05, Joe Bohn <[EMAIL PROTECTED]> wrote:
> When we set the log level on the Log4jService helper class it is set in
> the cached object (the Logger) but is never reflected in the physical
> log file itself (***-log4j.properties). Since the service refreshes the
> Logger object from the file on a set interval (I suspect to make it more
> dynamic so that it can be modified without recycle) the "new" level that
> was set in the cache via the api is overridden by the level specified in
> the file.
>
> Is this WAD? It seems that we should update the setting in the file
> when it is updated via the cache object. This presents more of a
> problem when interacting with clients that expect to be influencing the
> behavior of the system (such as the web console or a command line
> api). This seems strange and not intuitive to me. If I set the value
> via the API I expect that to take effect either 1) forever or 2 ) At
> least until I change it again or recycle the server. What is the
> common consensus? It seems like we can eliminate the file refresh
> processing once we have a web console and/or command line interface to
> alter the setting. Should I open an issue?
AFAICR, allowing a programmatic call to take precedence over the
.properties/.xml file can *only* take place programmatically.
Facilitating such a change might be possible by changing the way that
the log level is configured. But stopping the polling of a log file is
probably also not a good idea because someone may change this to
affect the log level *after* a programmatic call.
Bruce
--
perl -e 'print unpack("u30","D0G)[EMAIL
PROTECTED]&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'
The Castor Project
http://www.castor.org/
Apache Geronimo
http://geronimo.apache.org/
