You are viewing a plain text version of this content. The canonical link for it is here.

Posted to log4j-dev@logging.apache.org by bu...@apache.org on 2006/08/31 22:54:53 UTC

DO NOT REPLY [Bug 37358] - log4j:ERROR Cannot rename file

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


carnold@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WONTFIX




------- Additional Comments From carnold@apache.org  2006-08-31 20:54 -------
If you have two distinct instances of log4j (that is in different processes or different class loaders) or two 
distinct appenders within the same instance of log4j writing to the same file, you will have problems.  
There is no attempt to support IO synchronization between appenders or between JVM's and there are not 
platform-independent services in the Java libraries that would enable doing that if we wanted.  The 
common solution to have multiple processes write to a shared log destination is to use database 
appenders or to use SocketAppenders and have a single listener write to the common log file.

-- 
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