At 11:48 PM 12/7/2004 -0600, you wrote: >At 08:29 PM 12/7/2004 +0100, you wrote: > >At 08:30 AM 12/4/2004, Jacob Kjome wrote: > > > >>I'm not completely clear on what should be happening, but it seems to me > >>that... > >> > >>1. The rolling shouldn't be happening every time I restart the > >>server. I'm using a size based triggering policy with size set to > >>1000. That's kbytes, not bytes, right? This code should simply not be > >>being called until the active file hits 1000 kbytes, right? > > > >No, it's bytes. For KB, you have to write > > > > <param name="maxFileSize" value="1000KB"/> > > or > > <param name="maxFileSize" value="1MB"/> > > > >See page 102 of the complete manual. > >
LOG4J-INTERNAL: 2004-12-09 00:33:37,328 WARN [Thread-1] org.apache.log4j.config.PropertySetter#setProperty:179)- Failed to set property [maxFileSize] to value "1000KB".
Ceki, this was true for Log4j-1.2.x, but I don't think it is true for Log4j-1.3.
public void setMaxFileSize(long l) {
maxFileSize = l;
}It takes a long, not a String, so how could "KB" be in there?
Did you plan on not keeping parity with Log4j-1.2.x's file size param settings, or was this an oversight?
I changed it to <param name="maxFileSize" value="100000"/> and all is well (after locally fixing FixedWindowRollingPolicy to not bomb out as I describe in my other email).
Jake
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
