[EMAIL PROTECTED] wrote:

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

DailyRollingFileAppender fails with mult load-balancing JVMs under WAS

          Summary: DailyRollingFileAppender fails with mult load-balancing
                   JVMs under WAS
          Product: Log4j
          Version: unspecified
         Platform: Sun
       OS/Version: Solaris
           Status: NEW
         Severity: Normal
         Priority: Other
        Component: Appender
       AssignedTo: [EMAIL PROTECTED]
       ReportedBy: [EMAIL PROTECTED]
               CC: [EMAIL PROTECTED]


Regarding Bugzilla Bug 24107 "DailyRollingFileAppender sharing target File in multiple EARS"


We are encountering this in a WebSphere clustered environment so that while we DO have 4 separate JVMs, they are cloned under WAS, which uses the multiple JVMs for load balancing. This bug would indicate that if you are running in a load balanced environment with multiple servers, then the DailyRollingFileAppender will not work.

Thanks for your consideration in re-opening bug 24107 or looking into this variation of that bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



are you really sure?
I think you have a condition where the different processes try to write the same file. That issue is general and not related to Log4j.
use some system property to distinguish the instances in the config file and let them write to different files ....=/var/log/{some.property}/logfile
OR
use an common socket appender which writes to the file
OR
use syslog appender which can be used by all intances and collected on a common syslogserver.



--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to