[prev in list] [next in list] [prev in thread] [next in thread] 

List:       log4j-user
Subject:    RE: Is PropertyConfigurator.configureAndWatch() expensive?
From:       Mark Womack <mwomack () bevocal ! com>
Date:       2002-08-28 16:52:13
[Download RAW message or body]

configureAndWatch() creates a thread that will sleep most the time except
for the period of time you have configured it to "wake up" and check for
changes.  The check itself is fairly simple and not very intensive, and the
reconfiguration is no different than normal configuration calls.

Besides the creation of a thread, I'd say that it is non-intensive resource
wise, and even a thread is not that big of a deal nowadays.  Especially one
that sleeps most of the time.

-Mark

> -----Original Message-----
> From: Denis McCarthy [mailto:dmccarthy@omnipaygroup.com]
> Sent: Wednesday, August 28, 2002 6:32 AM
> To: Log4J Users List
> Subject: Is PropertyConfigurator.configureAndWatch() expensive?
> 
> 
> Hi there,
> I'm thinking of making my log4j.properties file dynamically 
> configurable by
> using configureAndWatch() in my application
> configuration. Prior to this I would like to ensure that it 
> does not hog
> system resources in any way. Can anyone confirm that using
> configureAndWatch() does not lead to any appreciable system 
> slowdown? Thanks
> Denis McCarthy
> 
> 
> 
> --
> To unsubscribe, e-mail:   
> <mailto:log4j-user-unsubscribe@jakarta.apache.org>
> For additional commands, e-mail: 
> <mailto:log4j-user-help@jakarta.apache.org>
> 

--
To unsubscribe, e-mail:   <mailto:log4j-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:log4j-user-help@jakarta.apache.org>

[prev in list] [next in list] [prev in thread] [next in thread]