How is log4net being initialized? It looks like something is causing it to shutdown... I'm pretty sure this message:
log4net: Logger: No appenders could be found for logger is being caused by attempts to log without first configuring log4net. ----- Original Message ---- From: Robin Shahan <[EMAIL PROTECTED]> To: Log4NET User <[email protected]> Sent: Wednesday, March 19, 2008 5:47:27 PM Subject: RE: Log4Net stopping Yes, it stops logging to both places. I'm looking at the debugging info that was output, and there's a lot of this kind of stuff: log4net: Logger: No appenders could be found for logger [GMStudio.gmPreviewForm] repository [log4net-default-repository] log4net: Logger: Please initialize the log4net system properly. log4net: Logger: Current AppDomain context information: log4net: Logger: BaseDirectory : <snip> log4net: Logger: FriendlyName : DefaultDomain log4net: Logger: DynamicDirectory: <snip> and this log4net: Hierarchy: Shutdown called on Hierarchy [log4net-default-repository] log4net: Logger: No appenders could be found for logger [GMSound.SoundUtils] repository [log4net-default-repository] log4net: Logger: Please initialize the log4net system properly. log4net: Logger: Current AppDomain context information: log4net: Logger: BaseDirectory : <snip> log4net: Logger: FriendlyName : DefaultDomain log4net: Logger: DynamicDirectory: and this has error "does not have a RepositoryAttribute specified." log4net: RollingFileAppender: Searched for existing files in [C:\Users\Jeanne\Documents\GoldMail] log4net: RollingFileAppender: curSizeRollBackups starts at [0] log4net: FileAppender: Opening file for writing [C:\Users\Jeanne\Documents\GoldMail\GoldMailLog.txt] append [True] log4net: XmlHierarchyConfigurator: Created Appender [RollingLogFileAppender] log4net: XmlHierarchyConfigurator: Adding appender named [RollingLogFileAppender] to logger [root]. log4net: XmlHierarchyConfigurator: Hierarchy Threshold [] log4net: DefaultRepositorySelector: Creating repository for assembly [GMLibrary, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null] log4net: DefaultRepositorySelector: Assembly [GMLibrary, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null] Loaded From [C:\Users\Jeanne\AppData\Local\Apps\2.0\EM6ZCA9H.ZH3\2YEVW4GX.TD1\gmst..tion_e84b302e57430172_0003.0002_8a24dc44b8cff001\GMLibrary.dll] log4net: DefaultRepositorySelector: Assembly [GMLibrary, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null] does not have a RepositoryAttribute specified. log4net: DefaultRepositorySelector: Assembly [GMLibrary, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null] using repository [log4net-default-repository] and repository type [log4net.Repository.Hierarchy.Hierarchy] log4net: DefaultRepositorySelector: repository [log4net-default-repository] already exists, using repository type [log4net.Repository.Hierarchy.Hierarchy] log4net: DefaultRepositorySelector: Creating repository for assembly [GMBusinessLogicLayer, Version=3.1.0.0, Culture=neutral, PublicKeyToken=null] Does this mean anything? Note than when I run it with the log debugging enabled, it works. Thanks, Robin From: Ron Grabowski [mailto:[EMAIL PROTECTED] Sent: Wed 3/19/2008 2:41 PM To: Log4NET User Subject: Re: Log4Net stopping Does logging stop on both the ConsoleAppender and the RollingLogFileAppender? ----- Original Message ---- From: Robin Shahan <[EMAIL PROTECTED]> To: Log4NET User <[email protected]> Sent: Wednesday, March 19, 2008 2:40:40 PM Subject: RE: Log4Net stopping font-face { font-family:Cambria Math;} font-face { font-family:Calibri;} font-face { font-family:Tahoma;} P.MsoNormal { FONT-SIZE:11pt;MARGIN:0in 0in 0pt;FONT-FAMILY:"Calibri", "sans-serif";} LI.MsoNormal { FONT-SIZE:11pt;MARGIN:0in 0in 0pt;FONT-FAMILY:"Calibri", "sans-serif";} DIV.MsoNormal { FONT-SIZE:11pt;MARGIN:0in 0in 0pt;FONT-FAMILY:"Calibri", "sans-serif";} A:link { COLOR:blue;TEXT-DECORATION:underline;} SPAN.MsoHyperlink { COLOR:blue;TEXT-DECORATION:underline;} A:visited { COLOR:purple;TEXT-DECORATION:underline;} SPAN.MsoHyperlinkFollowed { COLOR:purple;TEXT-DECORATION:underline;} P.MsoAcetate { FONT-SIZE:8pt;MARGIN:0in 0in 0pt;FONT-FAMILY:"Tahoma", "sans-serif";} LI.MsoAcetate { FONT-SIZE:8pt;MARGIN:0in 0in 0pt;FONT-FAMILY:"Tahoma", "sans-serif";} DIV.MsoAcetate { FONT-SIZE:8pt;MARGIN:0in 0in 0pt;FONT-FAMILY:"Tahoma", "sans-serif";} SPAN.BalloonTextChar { FONT-FAMILY:"Tahoma", "sans-serif";} SPAN.EmailStyle19 { COLOR:windowtext;FONT-FAMILY:"Calibri", "sans-serif";} SPAN.EmailStyle20 { COLOR:#5f497a;FONT-FAMILY:"Calibri", "sans-serif";} SPAN.EmailStyle21 { COLOR:#5f497a;FONT-FAMILY:"Calibri", "sans-serif";} .MsoChpDefault { FONT-SIZE:10pt;} DIV.Section1 { } When I turn on the internal debugging, the logging works every time. When I turn it off, it doesn't. I'm enabled this feature following the instructions in the link below. Does anybody have any ideas at all? Thanks, Robin From: Robin Shahan [mailto:[EMAIL PROTECTED] Sent: Wed 3/19/2008 10:51 AM To: Log4NET User; Log4NET User Subject: RE: Log4Net stopping The upload is spun off in a separate thread. We had another occurrence this morning where it stopped logging as soon as the user authenticated. This is not in a separate thread. I found this link, and it has some info about running internal debugging while logging; has anyone tried this? http://logging.apache.org/log4net/release/faq.html Thanks, Robin From: Dean Fiala [mailto:[EMAIL PROTECTED] Sent: Wed 3/19/2008 9:13 AM To: 'Log4NET User' Subject: RE: Log4Net stopping Hmmm, doesn't sound like you are bombarding the logger, but a few large file tests would be my next step. By large messages, I meant a couple of kilobytes, that's only really variably sized bit of the log entry. Another question. Does this file upload happen on the application's main thread, or is it spun off in a separate thread? Finally, is the rolling file log being accessed by anything else in the application? Dean From: Robin Shahan [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2008 12:01 PM To: Log4NET User Subject: RE: Log4Net stopping It uploads the file in chunks, so it prints out a log entry with each chunk. So maybe it’s not “a lot of logging” by other people’s standards, but it’s probably where the most logging occurs in our app. It depends on the size of the file. We’re testing with pretty small ones (no patience), so the last one I did was 156 lines of logging. It is just statements like “hitting the refresh code”, “posting chunk”, “chunk #23 posted”, “chunk 23 successful”. It prints the date/time and routing that logged the entry. As far as I know, we don’t have any large individual messages (how do you define large?), but I’ll see. It’s weird because as far as I know, that code hasn’t been mucked with, and it has been working just fine. Or so we think. Luckily, we use TFS, so I can tell if someone’s changed it, and if so, how. Thanks, Robin From: Dean Fiala [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2008 8:38 AM To: 'Log4NET User' Subject: RE: Log4Net stopping OK, Hard to tell how it is related without seeing what you are logging, but since that is your best guess, might as well follow up in that direction. Can you quantify "a lot of logging"? Are you attempting to log a large section of the file that is being uploaded? Or some other large individual message during the process? That's where I'd look since it seems to be appender indepenent. Dean From: Robin Shahan [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2008 11:12 AM To: Log4NET User Subject: RE: Log4Net stopping The file is being uploaded to our servers via web services. I don’t see how it can be related (it’s not a new feature), but that is the pattern we’re seeing -- logging stops for some people after they’ve uploaded. One thing to note: There is a lot of logging done during the upload process. One other thing – I remembered last night that I’ve seen this in one other case. I put some logging statements in this click event in a user control once, and it wouldn’t output the statements. I ended up putting in messageboxes to get the information I was looking for. And the other programmer who has seen this problem said the log messages don’t show up in the Output window in Visual Studio either. Here is our configuration file. I didn’t add the logging to our application, another programmer did, who is long gone. So I don’t know a whole lot about log4net, except how it’s set up in our app (it starts first thing), where the logs go, and how to write to the log. That, and it’s worked great right up to this moment. <?xml version="1.0" encoding="utf-8"?> <log4net> <appender name="ConsoleAppender" type="log4net.Appender.ConsoleAppender"> <layout type="log4net.Layout.PatternLayout"> <conversionPattern value="%date %-5level %logger (%L) [%ndc] - %message%newline" /> </layout> </appender> <appender name="RollingLogFileAppender" type="log4net.Appender.RollingFileAppender"> <file value="D:\RobinShahan\GoldMail\GoldMailLog.txt" /> <staticLogFileName value="true" /> <appendToFile value="true" /> <rollingStyle value="Size" /> <maxSizeRollBackups value="5" /> <maximumFileSize value="1MB" /> <layout type="log4net.Layout.PatternLayout"> <conversionPattern value="GMLog#%date;%-5level;%logger(%L);%message#End%newline" /> </layout> </appender> <root> <level value="DEBUG" /> <appender-ref ref="ConsoleAppender" /> <appender-ref ref="RollingLogFileAppender" /> </root> </log4net> Thanks, Robin Shahan GoldMail.com From: Dean Fiala [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2008 5:56 AM To: 'Log4NET User' Subject: RE: Log4Net stopping Robin, No answers, but some questions: Is the file being uploaded to the same directory as the log? Dose the size of the file being uploaded matter? Which appenders are you using? Regards, Dean Fiala From: Robin Shahan [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 18, 2008 8:53 PM To: [email protected] Subject: Log4Net stopping We are using log4net to do logging in a .Net 2.0 application. We have used it successfully for about 6 months. Then today, we discovered that sometimes it just stops working. It still goes through the statements to write to the log, but it doesn’t actually write anything anywhere. The users have to close our application and re-open it to start the logging off again. The action that happens right before it stops is uploading a file via web services. The file succeeds, and shortly thereafter it stops logging. I don’t know if that’s coincidence or what. We are not seeing this on all the customers, just some, and for those, some are intermittent and some are always happening. We are running the most current version (1.2.10). Any help would be greatly appreciated. Robin Shahan Sr. Software Engineer GoldMail, Inc. [EMAIL PROTECTED]
