DO NOT REPLY [Bug 31458] - DailyRollingFileAppender fails with mult load-balancing JVMs under WAS

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=31458>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=31458





------- Additional Comments From maqito@msn.com  2005-03-08 20:41 -------
I ran into this problem as well. We are running WebSphere 4 on an AIX server 
and we have logging in both the Web Container and EJB container writing to the 
same log files and one JVM would roll over and the other would continue to log 
to the old file because the file handle was still open to the original file 
even though it had been renamed. 

We got around the problem by overriding the DailyRollingFileAppender with our 
own that includes a check in the rollover method to check if the 
scheduledFilename file already exists.  If it does then close the file and 
reset the file 

this.closeFile();
this.setFile(fileName, true, false, this.bufferSize);
scheduledFilename = datedFilename;
return;	  

We've been running like this for 1.5 years and no issues.


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

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