Re: [logback-user] RE: [logback-user] logback initialization "à la" Spring
blakesys at yahoo.com
Thu Sep 27 19:11:04 CEST 2007
Not necessarily, the reload check could be done before the OFF check...
----- Original Message ----
From: Tom Leccese <tleccese at cybershift.com>
To: logback users list <logback-user at qos.ch>
Sent: Thursday, September 27, 2007 12:57:36 PM
Subject: [logback-user] RE: [logback-user] logback initialization "à la" Spring
snafu, perhaps. If all your loggers in your current config are turned
OFF, then a message would never get generated, and it would never check to
see if the config file has changed.
From: logback-user-bounces at qos.ch
[mailto:logback-user-bounces at qos.ch]On Behalf Of Arthur
Sent: Thursday, September 27, 2007 12:45 PM
logback users list
Subject: Re: [logback-user] logback
initialization "à la" Spring
used automatic reloading in the past in log4j and it certainly can be a very
nice and convenient feature--
There are various issues that come up in
the complexity of implementing it -- normally it's done with a separate Thread
that runs and wakes up every so often to check if the file timestamp on the
config file has changed.
Thats a bit of a clunky and complex way to do
I have been mentally toying with an idea for a new way to
accomplish this, without having to have a separate thread-- The check could be
done at the point where each log message is generated-- system
Since you already know the timestamp of the message generated,
you could just compare that to the timestamp of the last time the log config
file was reloaded-- and if a certain amount of time has elapsed since the last
time the file was checked, you kick off the code that checks to see if the
file time stamp has changed, and if so, reload it (that part could be done
asynchronously as well so as not to slow down other threads writing out log
It's simple, fast and it would have the very nice benefit of
not having to have a separate Thread-- furthermore, you avoid the overhead of
periodically checking the modification file stamp, over long periods when
there is no log activity (such as idle periods when a server might not be
getting any activity)
Has anyone thought of implementing it this
Original Message ----
From: Jorg Heymans
<jorg.heymans at gmail.com>
To: logback users list
<logback-user at qos.ch>
Sent: Thursday, September 27, 2007 10:23:07
Subject: Re: [logback-user] logback initialization "à la"
On 9/27/07, Davide Baroncelli
<baroncelli at yahoo.com> wrote:
let me express my disagreement for logback and sl4j not
neither the FATAL logging level nor automatic reloading of
+1 for automatic reloading !
Catch up on fall's
hot new shows on Yahoo! TV. Watch previews, get listings, and more!
This e-mail and any attachments may contain confidential and privileged information. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this e-mail and destroy any copies. Any dissemination or use of this information by a person other than the intended recipient is unauthorized and may be illegal.
Building a website is a piece of cake. Yahoo! Small Business gives you all the tools to get online.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Logback-user