http://blog.gmane.org/gmane.comp.apache.logging.log4net.devel hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://comments.gmane.org/gmane.comp.apache.logging.log4net.devel/2385 <pre>Hi, I am application developer team supporting.NET project in Michaels Stores. We have been using log4net.dll version 1.2.10.0 for application logs for our project. The application is implemented in .NET , C# with 3.5 framework. Recently we have faced System.OutOfMemoryException exception thrown by the application. We have opened case with Microsoft. Microsoft analyzed and said memory consumption is due to FileSystemWatcher objects used by log4net.Config.XmlConfigurator+ConfigureAndWatchHandler which are still alive and pinned objects. From the memory dump, They found &gt;2000 instances of log4net.Config.XmlConfigurator+ConfigureAndWatchHandler and the FileSystemWatcher objects created that contributed this issue. The issue is happening due to the fragmentation of Gen2 Heap. The reason for the fragmentation is the pinned System.IO.Overlapped objects used by FileSystemWatcher objects. To resolve the memory issue, we need to get rid of the fragmentation caused by pinned objects used by FileSystemWatcher obj</pre> Yuvraj Raj 2013-05-23T18:26:50 http://comments.gmane.org/gmane.comp.apache.logging.log4net.devel/2267 <pre>Hi there, Andrew Arnott posted that he is interested in nightly builds of log4net. Therefore I am hereby raising a poll to see if also the community is interested. Please post back with your opinion by placing a cross and optionally a small comment. Just like this: </pre> Dominik Psenner 2013-02-26T09:11:52 http://comments.gmane.org/gmane.comp.apache.logging.log4net.devel/2237 <pre>I pasted the patched files into a series of patches and bomb them to the mailing list for eassier review. </pre> Dominik Psenner 2013-01-22T13:41:04 http://comments.gmane.org/gmane.comp.apache.logging.log4net.devel/2185 <pre>This is a console C# 4.0 application app.config: &lt;log4net&gt; &lt;appender name="RollingLogFileAppender" type="log4net.Appender.RollingFileAppender"&gt; &lt;file type="log4net.Util.PatternString" value="F:\logs\CPDMonitor"/&gt; &lt;appendToFile value="true"/&gt; &lt;rollingStyle value="Date"/&gt; &lt;datePattern value="_yyyyMMdd_hh_mm_ss_sss'.log'"/&gt; &lt;maximumFileSize value="20MB"/&gt; &lt;staticLogFileName value="false"/&gt; &lt;maxSizeRollBackups value="20"/&gt; &lt;layout type="log4net.Layout.PatternLayout"&gt; &lt;conversionPattern value="%date [%thread] %-5level %logger - %message%newline"/&gt; &lt;/layout&gt; &lt;/appender&gt; &lt;logger name="RollingLogFileAppender"&gt; &lt;level value="DEBUG" /&gt; &lt;appender-ref ref="RollingLogFileAppender" /&gt; &lt;/logger&gt; &lt;/log4net&gt; In main I did: XmlConfigurator.Configure(); log = LogManager.GetLogger(typeof(Program)); To add an entry I used: log.DebugFormat("Sending eMail " + DateTime.Now.ToString("yyyyMMdd hh:mm:ss") + " with " + alList.Co</pre> skifreak 2012-12-17T13:48:41 http://comments.gmane.org/gmane.comp.apache.logging.log4net.devel/2182 <pre> [ https://issues.apache.org/jira/browse/LOG4NET-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&amp;focusedCommentId=13508623#comment-13508623 ] Dominik Psenner edited comment on LOG4NET-27 at 12/3/12 10:16 AM: ------------------------------------------------------------------ Hi Jochen. I just copied your RollingFileAppender.cs over the latest in SVN and see lots of differences. For example the DateTimeStrategy property is missing and some other things don't look sensible. Like this I cannot apply your file as it would break other things. But if you could integrate your patch into the latest trunk I gladly review it. was (Author: nachbarslumpi): Hi Jochen. I just copied your RollingFileAppender.cs over the latest in SVN and see lots of differences. For example the DateTiemStrategy property is missing and some other things don't look sensible. Like this I cannot apply your file as it would break other things. But if you could integrate your patch into t</pre> Dominik Psenner (JIRA 2012-12-03T10:18:00 http://comments.gmane.org/gmane.comp.apache.logging.log4net.devel/2181 <pre> [ https://issues.apache.org/jira/browse/LOG4NET-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&amp;focusedCommentId=13508623#comment-13508623 ] Dominik Psenner edited comment on LOG4NET-27 at 12/3/12 10:16 AM: ------------------------------------------------------------------ Hi Jochen. I just copied your RollingFileAppender.cs over the latest in SVN and see lots of differences. For example the DateTiemStrategy property is missing and some other things don't look sensible. Like this I cannot apply your file as it would break other things. But if you could integrate your patch into the latest trunk I gladly review it. was (Author: nachbarslumpi): Hi Jochen. I just copied your RollingFileAppender.cs over the latest in SVN and see lots of differences. For example the DateTiemStrategy property is missing and some other things that don't look sensible. Like this I cannot apply your file as it would break other things. But if you could integrate your patch i</pre> Dominik Psenner (JIRA 2012-12-03T10:17:58 http://comments.gmane.org/gmane.comp.apache.logging.log4net.devel/2180 <pre> [ https://issues.apache.org/jira/browse/LOG4NET-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&amp;focusedCommentId=13508623#comment-13508623 ] Dominik Psenner commented on LOG4NET-27: ---------------------------------------- Hi Jochen. I just copied your RollingFileAppender.cs over the latest in SVN and see lots of differences. For example the DateTiemStrategy property is missing and some other things that don't look sensible. Like this I cannot apply your file as it would break other things. But if you could integrate your patch into the latest trunk I gladly review it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> Dominik Psenner (JIRA 2012-12-03T10:11:58 http://comments.gmane.org/gmane.comp.apache.logging.log4net.devel/2179 <pre> [ https://issues.apache.org/jira/browse/LOG4NET-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&amp;focusedCommentId=13508619#comment-13508619 ] Jochen Kühner commented on LOG4NET-27: -------------------------------------- I use my Patched Version of Log4Net on 5 Costomers now for over 6 Moth without any Problem. Is this patch now in the Main Branch? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> Jochen Kühner (JIRA 2012-12-03T09:59:59 http://comments.gmane.org/gmane.comp.apache.logging.log4net.devel/2169 <pre> [ https://issues.apache.org/jira/browse/LOG4NET-178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&amp;focusedCommentId=13506313#comment-13506313 ] Dominik Psenner edited comment on LOG4NET-178 at 11/29/12 8:13 AM: ------------------------------------------------------------------- The general agreement is that this issue is better solved with workarounds. Therefore I just commited a new FAQ entry to the website as revision 839974: http://logging.apache.org/log4net/release/faq.html#trouble-webapp-stops-logging If you run into this issue please follow the steps there. If those do not solve your problem or you think there is something missing in the FAQ entry or you know a log4net-only solution that works feel free to reopen the bug and post a patch. was (Author: nachbarslumpi): The general agreement is that this issue is better solved with workarounds. Therefore I just commited a new FAQ entry to the website as revision 839974: http://logging.apache.org</pre> Dominik Psenner (JIRA 2012-11-29T08:15:00 http://comments.gmane.org/gmane.comp.apache.logging.log4net.devel/2168 <pre> [ https://issues.apache.org/jira/browse/LOG4NET-178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominik Psenner resolved LOG4NET-178. ------------------------------------- Resolution: Invalid The general agreement is that this issue is better solved with workarounds. Therefore I just commited a new FAQ entry to the website as revision 839974: http://logging.apache.org/log4net/release/faq.html#trouble-webapp-stops-logging If you run into this issue please follow the steps there. If those do not solve your problem or you think there is something missing in the FAQ entry feel free to reopen this issue or you know a log4net-only solution that works feel free to reopen the bug and post a patch. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> Dominik Psenner (JIRA 2012-11-29T08:13:00 http://comments.gmane.org/gmane.comp.apache.logging.log4net.devel/2157 <pre>Hi, Yesterday I posted this message on log4net-dev but maybe noone noticed. :-) Is there someone around that knows how the publishing of the log4net website works? Cheers, D. </pre> Dominik Psenner 2012-11-28T07:20:48 http://comments.gmane.org/gmane.comp.apache.logging.log4net.devel/2156 <pre> [ https://issues.apache.org/jira/browse/LOG4NET-178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&amp;focusedCommentId=13504804#comment-13504804 ] Matthew Schneider commented on LOG4NET-178: ------------------------------------------- Dominik: 1] This definitely happens in IIS 6.0 as well as 7.5, I can't speak to 8.0. 2] This is likely true, it probably has something to do with the fact that IIS runs a (shadow?) copy of the deployed code, not the code itself. Thus it might be starting a new instance (copy) while a previous instance (different copy) is terminating. 3] I've not had any luck with Ilpo's approach, but perhaps with another attempt, I might... (I just don't have the time at the moment). 4] I don't know that I agree that this is not solvable in log4net itself. I might agree that it is cheaper or easier to work around the issue (and that might be the best thing to do), but I suspect there is a way to cope with this if the right domain expert were to understand the pro</pre> Matthew Schneider (JIRA 2012-11-27T18:09:59 http://comments.gmane.org/gmane.comp.apache.logging.log4net.devel/2155 <pre>Hi, I gotta question about adding a new FAQ entry. I don't know how the build system works behind the scenes but I believe it should be enough to update: src\site\xdoc\release\faq.xml and commit. The website should then update itself, doesn't it? Cheers, D. </pre> Dominik Psenner 2012-11-27T12:19:25 http://comments.gmane.org/gmane.comp.apache.logging.log4net.devel/2154 <pre> [ https://issues.apache.org/jira/browse/LOG4NET-178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&amp;focusedCommentId=13504501#comment-13504501 ] Lazy Developer commented on LOG4NET-178: ---------------------------------------- We tested it in these environments (and it's working): DEV/INT: Windows 2008 R2, IIS 7.5, SQL 2008 R2 UAT/LIVE: Azure Cloud Services (Windows 2012, IIS 8), SQL Azure - it should be working the normal IIS as well. All I can suggest is turning on the log4net debugging features and fix all ERROR (in our case it was incorrect configuration). If there's no ERROR shows in the log4net debug log then it should be working. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> Lazy Developer (JIRA 2012-11-27T10:21:58 http://comments.gmane.org/gmane.comp.apache.logging.log4net.devel/2153 <pre> [ https://issues.apache.org/jira/browse/LOG4NET-178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominik Psenner updated LOG4NET-178: ------------------------------------ Summary: Log4Net stops logging after appdomain recycle of ASP.NET2.0 application (was: Log4Net stops logging after appdomain recycle of aps.net2.0 application) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> Dominik Psenner (JIRA 2012-11-27T10:11:59 http://comments.gmane.org/gmane.comp.apache.logging.log4net.devel/2152 <pre> [ https://issues.apache.org/jira/browse/LOG4NET-178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&amp;focusedCommentId=13504496#comment-13504496 ] Dominik Psenner edited comment on LOG4NET-178 at 11/27/12 10:06 AM: -------------------------------------------------------------------- So the general consensus is that the issue is: 1] IIS (7.5?) specific 2] a timing problem caused by misplaced shutdown / start events 3] solvable with a "manual" reconfiguration of log4net in the right spot 4] not solvable in log4net itself since log4net has to handle events when they are raised If these conditions are met I would close this issue with resolution "invalid" and add a new FAQ entry at http://logging.apache.org/log4net/release/faq.html describing the issue and a rather detailed description how it can be fixed. To be able to do that, would one of you guys please write down an answer to the question: "Why does my IIS hosted web application stop logging after some time?" By the way: has </pre> Dominik Psenner (JIRA 2012-11-27T10:07:58 http://comments.gmane.org/gmane.comp.apache.logging.log4net.devel/2151 <pre> [ https://issues.apache.org/jira/browse/LOG4NET-178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominik Psenner reassigned LOG4NET-178: --------------------------------------- Assignee: Dominik Psenner -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> Dominik Psenner (JIRA 2012-11-27T10:01:59 http://comments.gmane.org/gmane.comp.apache.logging.log4net.devel/2150 <pre> [ https://issues.apache.org/jira/browse/LOG4NET-178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&amp;focusedCommentId=13504496#comment-13504496 ] Dominik Psenner commented on LOG4NET-178: ----------------------------------------- So the general consensus is that the issue is: 1] IIS (7.5?) specific 2] a timing problem caused by misplaced shutdown / start events 3] solvable with a "manual" reconfiguration of log4net in the right spot 4] not solvable in log4net itself since log4net has to handle events when they are raised If these conditions are met I would close this issue with resolution "invalid" and add a new FAQ entry at http://logging.apache.org/log4net/release/faq.html describing the issue and a rather detailed description how it can be fixed. To be able to do that, would one of you guys please write down an answer to the question: "Why does my IIS hosted web application stop logging after some time?" -- This message is automatically generated by JIRA. </pre> Dominik Psenner (JIRA 2012-11-27T09:57:59 http://comments.gmane.org/gmane.comp.apache.logging.log4net.devel/2149 <pre> [ https://issues.apache.org/jira/browse/LOG4NET-178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&amp;focusedCommentId=13504485#comment-13504485 ] Ilpo Juvander commented on LOG4NET-178: --------------------------------------- Above configuration is not the whole truth. What we originally had was exactly like it is for desktop application, using this [assembly: log4net.Config.XmlConfigurator(ConfigFile = "log4net.config", Watch = true)]. It does not really matter what the file name is, logging just ends at some point when IIS is recycling application pools. There is some timing issue how this configuration/shutdown is handled. Application start seems to happen before previous shutdown is called thus even new instance gets logging shutdown. Using configuration call from class constructor is *late* enough so that it really does the initialization for new instance and does not get this shutdown call from previous application pool. We have used this method now for years in hundreds </pre> Ilpo Juvander (JIRA 2012-11-27T09:35:59 http://comments.gmane.org/gmane.comp.apache.logging.log4net.devel/2148 <pre> [ https://issues.apache.org/jira/browse/LOG4NET-178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&amp;focusedCommentId=13504422#comment-13504422 ] Dominik Psenner commented on LOG4NET-178: ----------------------------------------- Glad to hear you were able to sort out this nasty problem. Can this bug therefore be closed? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> Dominik Psenner (JIRA 2012-11-27T07:39:57 http://comments.gmane.org/gmane.comp.apache.logging.log4net.devel/2147 <pre> [ https://issues.apache.org/jira/browse/LOG4NET-178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&amp;focusedCommentId=13504094#comment-13504094 ] Lazy Developer commented on LOG4NET-178: ---------------------------------------- Hi Everyone, Thanks the tip from Dominik, he's right, it's completely about CONFIGURATION. We turned on the log4net internal logging (log4net.Internal.Debug=true...etc.) for more details. The root of our problem is about forgetting this code log4net.Config.XmlConfigurator.Configure() in Global.asax.cs (Application_Start). REMOVE IT! We have separate log4net.config from web.config and in the AssemblyInfo.cs we've already have this code [assembly: log4net.Config.XmlConfigurator(ConfigFile = "log4net.config", Watch = true)]. It must be enough. When the recycle occured (Application_Start is activated) the log4net tried to looking for its configuration in web.config instead of log4net.config (because of the mentioned code log4net.Config.XmlConfigurator.Co</pre> Lazy Developer (JIRA 2012-11-26T21:06:58 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.apache.logging.log4net.devel