SV: DO NOT REPLY [Bug 15896] - PropertyConfigurator.configureAn dWatch thread not stopping

[he...@dnb.no]

Hi

I took a look at the code here.

static
  public
  void configureAndWatch(String configFilename, long delay) {
    PropertyWatchdog pdog = new PropertyWatchdog(configFilename);
    pdog.setDelay(delay);
    pdog.start();
  }

Something that strikes me is why the method setDaemon(true) on the
thread is not used. This will force a shutdown of this tread when the
parent thread dies.

Any comments on this ?

Hermod

-----Opprinnelig melding-----
Fra: bugzilla@apache.org [mailto:bugzilla@apache.org]
Sendt: 9. januar 2003 19:23
Til: log4j-dev@jakarta.apache.org
Emne: DO NOT REPLY [Bug 15896] - PropertyConfigurator.configureAndWatch
thread not stopping


DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15896>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15896

PropertyConfigurator.configureAndWatch thread not stopping





------- Additional Comments From mwomack@apache.org  2003-01-09 18:23
-------
The whole file watchdog mechanism used in v1.2.x is going to be replaced
in 
v1.3 with new plugin functionality.  A whole class of "watchdog" plugins
will 
be implemented and available for use.  They will be configurable via 
configuration files (at least xml configuration files) and much more
control 
will be available to start/stop/restart them as needed.  They will be
shutdown 
as part of the repository shutdown process, etc.  One of the reasons
this is 
being done is because of this bug.  Until then, I don't think there is
an easy 
fix for this issue.  I would suggest not using the configureAndWatch() 
mechanism, and instead include a servlet in your application that can be

accessed via http requests to reload the log4j settings as needed.  I
would 
appreciate any feedback you might have on the new plugin architecture,
and 
watchdogs in particular.  There have been many discussion threads on the
dev 
email list about the new watchdogs, though implementing them in the new
plugin 
architecture still needs to be done.  Soon.

--
To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
For additional commands, e-mail:
<ma...@jakarta.apache.org>


* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

This email with attachments is solely for the use of the individual or
entity to whom it is addressed. Please also be aware that DnB cannot
accept any payment orders or other legally binding correspondence with
customers as a part of an email. 

This email message has been virus checked by the virus programs used
in the DnB Group.

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>