>From what I've read, Remoting and SOAP are non-preferred. Could you just make a simple log sink Win32 service for all your processes?
-Chad -----Original Message----- From: Nicko Cadell [mailto:[EMAIL PROTECTED] Sent: Monday, May 24, 2004 2:17 AM To: 'Log4NET User' Subject: RE: Bug? Log4Net 1.1 does not allow several processes to log into the same files. Alexey, It looks like the log4j FAQ recommends using a SocketAppender to transfer logging events to a central server before writing them to a single file. http://logging.apache.org/log4j/docs/FAQ.html#many21 They only way that I know of to have a .NET remoting server autostart is to deploy it under IIS and use SOAP. http://msdn.microsoft.com/library/en-us/cpguide/html/cpconhostingremoteo bjec tsininternetinformationservicesiis.asp I think you could use a COM server to centralise the log messages but I don't think you would be able to use remoting to transfer the logging events. You would likely have to write a new appender (similar to the RemotingAppender) that called a method in your COM server to pass across the LoggingEvents. Inside your COM server you could then re-log the received logging events like the log4net.Plugin.RemoteLoggingServerPlugin does. Nicko > -----Original Message----- > From: Alexey N. Solofnenko [mailto:[EMAIL PROTECTED] > Sent: 24 May 2004 04:22 > To: Log4NET User > Subject: Re: Bug? Log4Net 1.1 does not allow several > processes to log into the same files. > > I was always wondering why it works in Java, but > RollingFileAppender seems working fine, unless there is a > hidden problem that I do not know about. Using a special > server would cause too much problems with deployment. Is > there a way to automatically start it, share between multiple > applications, and then automatically stop it? What do you > think about a COM server? > > - Alexey. > > Nicko Cadell wrote: > > >Alexey, > > > >The log4net FileAppender uses exclusive locking to write to > the file. > >This means that the file can only be opened from one > FileAppender. This > >is the same behaviour as in log4j. > > > >The current suggestion is to use a remoting server to centralise the > >log messages before writing them into the file. > >http://logging.apache.org/log4net/release/manual/faq.html#HC-30836417 > > > >This is a common issue and we are evaluating the possibility > of using > >different locking models for the FileAppender. > > > >Nicko > > > > > > > >>-----Original Message----- > >>From: Alexey N. Solofnenko [mailto:[EMAIL PROTECTED] > >>Sent: 21 May 2004 16:48 > >>To: Log4NET User > >>Subject: Bug? Log4Net 1.1 does not allow several processes > to log into > >>the same files. > >> > >>Hello, > >> > >> Log4J works fine, but Log4Net does not. If it cannot work at all, > >>what is the recommended way of handling it? > >> > >>- Alexey. > >> > >> > >> >
