Hello,
Check out if the following meets your needs:
https://log4netremotelogging.codeplex.com/ .
Best regards,
Svante
On Fri, Nov 21, 2014 at 12:29 PM, Wim Sturkenboom <
wim.sturkenb...@hambisana.com> wrote:
> Hello all
>
>
>
> Let me start saying that I know about nothing about log4net (even
Hello,
There is a known issue with log4net when you have mulitple sites logging to
the same file causing this exact situation (among other issues). Please
ensure this is not the case in your configuration. Just guessing, but I
might also guess that you'd risk seeing the same problem under heavy lo
There's the UDP appender and the fine listener here:
http://logview4net.com/ .
Also, as mentioned the RemotingAppender and a fine listener (if I may say
so myself) here: log4netremotelogging.codeplex.
Svante
On Thu, Dec 22, 2011 at 11:56 AM, Pascal ROZE wrote:
> Hello
>
> And the RemotingAppe
You are probably logging from several AppDomains to the same log file. This
is not really supported by Log4Net, not even with the 'minimal' locking
style. Try the http://log4netremotelogging.codeplex.com/ which solves this
and other issues whith several log sources.
Svante
On Tue, May 3, 2011 at
The log4net remote logging service
http://log4netremotelogging.codeplex.com/ solves
this issue, and some others too.
Svante
Hello,
I've published a convenience wrapper around the log4net remoting receiver
plug-in RemoteLoggingServerPlugin, in the form of an installer for a Windows
Service.
This makes it easy to make use of the RemoteAppender to send logs to a
single location for consolidation etc.
It also resolves a
