You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Juan Gonzalez (Jira)" <ji...@apache.org> on 2019/10/14 12:30:00 UTC

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

    [ https://issues.apache.org/jira/browse/LOG4NET-602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16950968#comment-16950968 ] 

Juan Gonzalez commented on LOG4NET-602:
---------------------------------------

[~nachbarslumpi] - I have been tasked to see how we can address this issue as well as a high CPU usage issue we have encountered on our systems when using log4net.  As part of this research, I am trying to build a log4net source with the old key (1b44e1d426115821).  It appears that the 2.0.8 "old" key binary that is downloadable has the new key (669e0ddf0bb1aa2a).  I was wondering if you could provide me with a method that I can build log4net using the old key.

NOTE:  The reason that I am asking is because our system implements a plugin structure.  We have 100's of plugins that all make use of the old key log4net and really would have no way to rebuild them all to make use of the new key.

I would really appreciate any assistance that you can provide.

 

cc:  [~lnmdz]

 

> 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)