Thanks for the answer, The socket appender is a good option, but i read this article http://www.jroller.com/oburn/date/200601 and was concerned about possible problems (deadlocks).
the first problem would arise if thd JVM receiving the logs goes down or even goes into a deadlock. I need a way to bring the socket appender up in another JVM as failover mechanism. Another problem is if the file gets locked, I can't do anything until the JVM is restarted and this is definitely not a good failover. Does someone have experience with this kind of multiple jvm logging architectures? Bye, Thomas On 7/31/07, James Stauffer <[EMAIL PROTECTED]> wrote: > > You can have each JVM send the events to a single separate JVM with > SocketAppenders. That single separate JVM would receive events from > all of the other JVMs and write them to a file. > > On 7/31/07, Thomas michelbach <[EMAIL PROTECTED]> wrote: > > Hello, > > > > I'm using log4j in an environment with multiple jvms. I know that the > best > > option for a central logging output, would be a database, but in this > > environment I don't have one. Now I use a different file for each jvm, > but I > > need to consolidate them in one file. > > > > The best case would be to have the same appender in each JVM and they > would > > have a buffer to protect the file and control the I/O. Is there any > sample > > how to do this in log4j? Is it supported? > > > > Bye, > > Thomas > > > > > -- > James Stauffer http://www.geocities.com/stauffer_james/ > Are you good? Take the test at http://www.livingwaters.com/good/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Thomas Michelbach
