DO NOT REPLY [Bug 14997] New: - High Throughput, High Threads, Log File not Rollingover

[bu...@apache.org]

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=14997>.
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=14997

High Throughput, High Threads, Log File not Rollingover

           Summary: High Throughput, High Threads, Log File not Rollingover
           Product: Log4j
           Version: 1.2
          Platform: Sun
        OS/Version: Solaris
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Other
        AssignedTo: log4j-dev@jakarta.apache.org
        ReportedBy: scott.c.pollack@wellsfargo.com


I'm using a normal log4j configuration:

log4j.rootCategory=INFO, A1
log4j.appender.A1=org.apache.log4j.RollingFileAppender 
log4j.appender.A1.File=/var/imPceWraper.log
log4j.appender.A1.MaxFileSize=10KB
log4j.appender.A1.MaxBackupIndex=10
log4j.appender.A1.Append=false
log4j.appender.A1.layout=org.apache.log4j.PatternLayout
log4j.appender.A1.layout.ConversionPattern=%d [%t] %-5p %c - %m%n

for logging in my JVM.  I have a single class threaded n times, (currently 10), 
each of which logs to the same file (shown above).  It seems that when I'm 
doing significant throughput with a low logging level (doesn't seem to happen 
in DEBUG) my log file fails to rollover, instead the new file overwrites the 
old.  Does this have something to do with a threaded class retaining a handle 
on the file, thus not allowing the old file to be moved so when the new file 
starts it just overwrites the old?

pls advise.

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