[
https://issues.apache.org/jira/browse/LOG4NET-602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16568349#comment-16568349
]
Massimo Del Zotto commented on LOG4NET-602:
-------------------------------------------
I *might* have observed this *in production* while doing forensics for a
service we provided. I'd need to investigate more in detail. Luckly, the missed
messages are not critical as others imply their presence anyway. In this case
we would be talking about a windows service .NET4.5.2 framework.
I am more concerned I have a prototype server in the works and it regularly
misses a specific call. This one runs a slightly modified log4net version to
run on .NET Core on a pi so I understand it's currently less problematic for
l4n team as not officially supported but perhaps even more important for us.
I hope I have the time to investigate the next week.
> Log4Net missing messages
> ------------------------
>
> Key: LOG4NET-602
> URL: https://issues.apache.org/jira/browse/LOG4NET-602
> Project: Log4net
> Issue Type: Bug
> Components: Appenders
> Affects Versions: 2.0.8
> Reporter: Juan Gonzalez
> Priority: Blocker
> Attachments: log4net.config, log4net.zip
>
>
> I am using log4net 2.0.8 from a C# service. This service has a method that
> writes out a status message of application domains that it has loaded on a
> timer (normally every three minutes, but set to 30 seconds for testing). What
> I have found is that some of our status messages are missing. It appeared to
> me from the message, that the code is working, but no message is being
> generated.
> So, I added a Debug.WriteLine before every Log.Fatal (set to Fatal for
> testing) and ran the code.
> As you can see from the attached log4net.txt, the code logged successfully
> and then failed.
> The output should have the following messages.
> tmrLogData_Elapsed
> LogData, Enter
> LogData, appDomainUtilsLoggingList.Count
> LogData, 1
> LogData, 2
> LogData, 3
> LogData, 4
> LogData, sb.Count
> LogData - start, logDataCounter
> LogData, 5
> LogData, Exit
> You see the run that failed on lines 302786 - 302810. It has the
> Debug.WriteLine calls, but only some of the Log.Fatal calls logged anything.
> We are very concerned that log4net may be missing other critical messages.
> Please feel free to reach out to me if you need further information.
>
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
