[
https://issues.apache.org/jira/browse/LOG4NET-602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16538641#comment-16538641
]
Dominik Psenner commented on LOG4NET-602:
-----------------------------------------
Happy to help. I hope you'll find during your investigation that there's
something else than the logging framework what's causing the observed issue.
Note however that log4net is not intended for auditing purposes and therefore
it is not designed be
[reliable|http://logging.apache.org/log4net/release/faq.html#reliability] but
is a best-effort and fail-stop logging system. While it can be (ab)used for
auditing purposes, whoever (ab)uses it like that must have a deep understanding
of how the framework and all the used components like event filters, event
buffers and all the configured appenders along with the involved logging sinks
(like databases or the filesystem) work together. It is typically advisable to
implement auditing requirements as a key feature of a product instead.
> 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)
