Thank you for your help Rob. We identified that if one of the custom
properties was not set at the point in time we're about to log a message (in
our case not all log messages had a job id), that the value that was previously
set for that thread was logged. This was the cause of our inconsiste
I took a quick look at the code and as far as I can see, the ThreadContext is
taken out of the logging event when formatting the message which happens when
it is being written. Therefore, I believe that if you use any appender deriving
from the BufferingSkeletonAppender, then the ThreadContext w
Yeah we're using the log4net.Appender.AdoNetAppender.
From: Rob Prouse [mailto:rob.pro...@ivara.com]
Sent: Wednesday, September 01, 2010 11:59 AM
To: Log4NET User
Subject: RE: Custom Properties in an ASP.Net Web Application
For the common log appenders, the log is output synchronously with the lo
For the common log appenders, the log is output synchronously with the log
message, so it should be on the same thread, so it shouldn't be a problem. I am
not sure of the behavior when you use an asynchronous appender (like the ADO
appender), but it should be pulling the context out before it go
Here's our situation...
We're adding debug messages to an ASP.Net web application that allows our users
to apply for a job online. We have a custom properties and database fields
created named JobPostingId and MemberId. Here's a small code snippet of our
logging.
ILog logger = LogManager.Get
No, but when I do I get version problems and my application won't start.
I don't want to rebuild all the common logging, spring and nhibernate dll's
Any idea?
Cheers,
Marc Gerritsen
From: Karim Bourouba [mailto:kar...@hotmail.com]
Sent: maandag 30 augustus 2010 18:03
To: 'Log4NET User'
Subject
