2008/5/19 Senaka Fernando <[EMAIL PROTECTED]>: > This is my thought on continuing the polling mechanism. When we read the > log4j.xml at startup, if this issue is likely to crop-up we should initiate > a controlled shutdown after logging the warning.
Yes, this is the straightforward case - if someone has a bad file on startup just log it and die. > If, this happens during > operation the warning must be logged once, and we will continue with the > previous known values. OK. The question is whether you can do this without modifying log4j? > If the error is corrected, this property that withheld the > warning will be reset and, a debug message will be logged explaining that > the problem was corrected. Do you meant that you will try to detect which particular property is invalid? In general, is that not impossible? RG
