Open torndar opened 9 years ago
@rcollette any ideas on this one before I dig into it?
Not off the top of my head. I will not have time to look at it at until at least this weekend.
This is due to the Fix
property being set to FixFlags.Partial
in AsyncForwardingAppenderBase
. Partial does not include FixFlags.LocationInfo
which is what is used for the caller info fields such as method which caused the problem described. This is the same issue as #15. Setting the property to FixFlags.All
or FixFlags.Partial | FixFlags.LocationInfo
seems to fix the problem. Unfortunately I don't seem to be able to set it via XML config.
Hi @coryflucas, thanks for the information! We should look at providing a way to set this from the config. If I remember correctly, isn't there a perfoamnce hit for using FixFlags.All?
Yes, there is a performance hit because the LocationInfo items are using reflection I believe. An option to override the default would give the user the option to allow the fields to be passed if they were ok with the performance hit.
When I log directly to the RollingLogFileAppender I get output like this:
But when I log through ParallelForwardingAppender I seem to lose the last portion of each message. It seems to lose the
%-18.18M - %message %newline
portion of the conversion pattern (including the newline so all the below really does show up as one line).The appender configuration is: