DO NOT REPLY [Bug 15283] New: - RollingFileAppender catches the CPU

[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=15283>.
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=15283

RollingFileAppender catches the CPU

           Summary: RollingFileAppender catches the CPU
           Product: Log4j
           Version: 1.2
          Platform: All
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Major
          Priority: Other
         Component: Appender
        AssignedTo: log4j-dev@jakarta.apache.org
        ReportedBy: daniel.or@emblaze.com


I use log4j1.2.7 .
JDK - 1.3.1

Suddenly, I noticed my app hangs and takes more than 90% of the cpu.
After a short investigation I found it happened on the first 
logging call.

Further investigation showed that after removing the RollingFileAppender
from my appenders list solved the problem.

another thing that solved the problem was removing the log file.

by the way, the log file was almost rolling size.

Details:

-----------------------------------------------------------
Roller configuration -
log4j.appender.roller=org.apache.log4j.RollingFileAppender
log4j.appender.roller.MaxFileSize=1048576
log4j.appender.roller.File=emblaze/logs/NG.log
log4j.appender.roller.MaxBackupIndex=200000
# a custom layout
log4j.appender.roller.layout=com.blz.util.logging.BLZLayout
-----------------------------------------------------------


rolled file size when the bug appears: 1051674 bytes.

I cannot attach the log file to this report, but, if you'll contact me
I'll be able to reproduce the whole data.

Daniel Or

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