You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Ralph Goers (Jira)" <ji...@apache.org> on 2020/04/04 22:30:06 UTC

[jira] [Updated] (LOG4NET-602) Log4Net missing messages

     [ https://issues.apache.org/jira/browse/LOG4NET-602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ralph Goers updated LOG4NET-602:
--------------------------------

LOG4NET is now dormant.  

> 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: Minor
>         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
(v8.3.4#803005)