logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 44700] New: Log4J locks rolled log files
Date Fri, 28 Mar 2008 09:06:54 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=44700

           Summary: Log4J locks rolled log files
           Product: Log4j
           Version: 1.2
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Appender
        AssignedTo: log4j-dev@logging.apache.org
        ReportedBy: jethro.bakker@ordina.nl


Hello,

Currently I am facing the following problem with Log4J (v1.2.8 but also in
v1.2.15). We use the DailyRollingFileAppender. Most of the log files are rolled
once a day, but a few once an hour. The rolling proces seems ok, new files are
created and the data in the files looks good. 

The problem is that the applicationserver (WAS 6) holds a lock on the rolled
files. We can not delete those files from the filesystem.
With the unix command fuser we can see which process is holding which log file.
For example:

common.log:  1302780 
common.log.2008-03-25-11: 
common.log.2008-03-26-13: 
common.log.2008-03-26-19: 
common.log.2008-03-26-20: 
common.log.2008-03-26-21:  1302780 

The latest log file: common.log.2008-03-26-21 should not be locked! We have a
workaround by using the touch command on the log4j.xml. The log configuration
is (re)initialized and releases all the locks.

What can we do about this problem?


-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


Mime
View raw message