Re: error XmlConfigurator: Failed to parse config file.

suedeuno — 2008-12-04T00:35:17

It seems that using the XmlConfigurator attribute in assemblyinfo works with default .config files but the fluent XmlConfigurator does not. Consequently, using the fluent configuration with non-default config files works as long as I have the path correct. Seems strange to me. One question, does XmlConfigurator have to be called in every project that will use logging? I created a wrapper aroung log4net and would like to just call XmlConfigurator within the wrapper class only but that doesn't seem to work for me. It won't log unless I have XmlConfigurator called in every project using log4net. Any help would be appreciated. Seems configuring log4net is not as easy as the few tutorials online seem to claim. Freddy Gómez wrote:

Re: error XmlConfigurator: Failed to parse config file.

Freddy Gómez — 2008-12-03T21:15:03

If you add to the config file the section: you will get in the output window of Visual Studio debug information from log4net. On Wed, Dec 3, 2008 at 2:12 PM, suedeuno yahoo.com> wrote:

error XmlConfigurator: Failed to parse config file.

suedeuno — 2008-12-03T18:42:06

I'm getting this error when running a unit test. It does complete the logging in spite of this error. I need to resolve this so that the automated build process does not fail. Any ideas?: log4net : error XmlConfigurator: Failed to parse config file. Is the specified as:

app.config:

In code: log4net.Config.XmlConfigurator.Configure(); log = LogManager.GetLogger(System.Reflection.MethodBase.GetCurrentMethod().DeclaringType); log.Error("message);

logging into different logfiles depending on parameter

Edwin — 2008-12-02T14:14:19

Hello, I'm trying to log in separate logfiles, depending on a parameter in my application. Until now I'm unable to. I have read about filters and what I tried is : in my app : log4net.GlobalContext.Properties["myparam"] = "xyz"; log.Info("message 1"); log4net.GlobalContext.Properties["myparam"] = "abc"; log.Info("message 2"); I'd like to have the 2 messages in different files. The filter I used is : The result is that all messages are logged in all logfiles. How should/can I solve this ? Thanks, Edwin

Re: Best Way to Set Up Massive Number of Loggers

Loren Keagle — 2008-12-02T07:19:47

This is the only way I know how to do this in log4net. We do this to handle remote logging from embedded controllers. We use .NET remoting appenders in this case, so we get the HostName property of each remote host logging to the sink. But if you're local you could do the same thing with a string filter or other property filter. This gives you individual layout control over each appender, and hence each log source. If only log4net would add in a layout-ref tag so we wouldn't have to repeat ourselves 75 times...

Re: Best Way to Set Up Massive Number of Loggers

Eric Marthinsen — 2008-12-02T00:48:46

Hi Walden- I like the grep idea. The motivation for the multiple log files is twofold. First, they get really big really quickly. I realize I can roll them on size, but it's nice to have a daily log file. Second, we have some utilities that can take a log file and replay previous transactions (we are logging a lot of data in custom formats). These are still programmer tools (and QA). -Eric On Mon, Dec 1, 2008 at 7:39 PM, Walden H. Leverich techsoftinc.com>wrote:

RE: Best Way to Set Up Massive Number of Loggers

Walden H. Leverich — 2008-12-02T00:39:55

Since you're asking for thoughts... bad idea. To me log4net is plumbing, that is it's programmer based stuff. Sounds to me like you're attempting to use it to satisfy a user requirement. I think you'd be better off adding the logging as part of the business processing. Now, having said that, there are still times when it's nice to know which trading partner you're dealing with on a log message. In that case I'd push the partner id into the NDC at the start of the process, and pop it at the end. That way you'll have it in the log (if you format it correctly). You'll have a single log file, but you can always fgrep it. We do something similar with several levels of NDC and can quickly come up with a issue-specific logfile using grep. -Walden

Best Way to Set Up Massive Number of Loggers

Eric Marthinsen — 2008-12-02T00:31:12

Hello- I'm working on an app that coordinates data transfers among multiple trading partners. I want to create a log file for each trading partner. I had a few ideas of how to do this, but am not sure which would be considered the optimal way. The expected number of trading partners is likely to be around 100, but could be higher. Here are my thoughts: 1. Add a bunch of named loggers to my log4net.config file 2. Do programmatic configuration of the loggers on application start 3. Write my own appender that is based on the RollingFileAppender Do any of these scream out as being a good or bad solution? Is there a better approach that I might be missing? Thanks in advance. Regards, Eric

Re: Logging issue, Repository count is 1

suedeuno — 2008-12-01T22:55:47

I had to call XmlConfigurator.Configure(); within the global.asax file for it to work due to StructureMap. Didn't have the problem with Unity.

RE: configuration problems, not logging

suedeuno — 2008-12-01T17:05:22

Actually that section is present in the web.config. Strangely if I remove the attribute from assembly.info no logging occurs, but if I replace the attribute back to the assembly.info then logging works. Is there an issue with log4net and .Net 3.5 framework? Radovan Raszka wrote:

Logging issue, Repository count is 1

suedeuno — 2008-12-01T16:32:06

I have two projects setup, one uses Unity depencency injection and the other uses StructureMap. The project using Unity will log both from unit tests and from the web. The StructureMap project will only log from the unit test. As a note, when I call 'log = LogManager.GetLogger(System.Reflection.MethodBase.GetCurrentMethod().DeclaringType);' from the Unity project the LogManager Repository count is 0. When I call the same line from the StructureMap project unit test the repository count is also 0, but from the Structure Map web the repository count is 1 with 59 values. I'm assuming this is a key to why it's not working within the web of the structure map project. Can anyone provide any help in debugging/fixing this issue?

Re: Strong Name Key

Scott Alexander — 2008-12-01T16:16:38

correction - (1.2.10.0 signed by the log4net key) On Mon, Dec 1, 2008 at 8:16 AM, Scott Alexander gmail.com> wrote:

Re: Strong Name Key

Scott Alexander — 2008-12-01T16:16:00

NHibernate is compiled against the strong named version of log4net so yes, it requires a specific version (1.2.10.9 signed by the log4net key) of log4net. Scott On Mon, Dec 1, 2008 at 8:11 AM, Walden H. Leverich techsoftinc.com> wrote:

RE: Strong Name Key

Walden H. Leverich — 2008-12-01T16:11:09

Does NHibernate require a signed version of the assembly? Why not just drop you modified version, unsigned, into the bin directory and let NHibernate use it. -Walden

Strong Name Key

Scott Alexander — 2008-12-01T15:43:52

Just curious if there is any new information regarding the availability of = the log4net private key. I have a project that uses log4net but requires a minor modification to the= code (RollingFileAppender RollFile method marked as virtual). This is a p= roblem b/c I also use some other assemblies (i.e. NHibernate) that use log4= net. Now I have two log4net assemblies signed w/ different keys... In order to get this to almost work (without using the GAC) I have to copy = both assemblies to my bin directory (bin/log4net.dll and bin/log4net/log4ne= t.dll), then use a element in the application config file to ove= rride the assembly binding. This almost works, w/ the exception of the majo= r problem that I now have two log4net assemblies instantiated and cannot re= ceive log messages from both using a single appender. This would be a trivial problem if I had access to the private key... any a= dvice? Thanks Scott Alexander P.S. love the project!

Re: Log4net.dll reference copy-local=true not behaving as expected

boombox boy — 2008-11-27T09:44:08

The thing is MyLogWrapper is built as a release library as it is used throughout all my different projects and therefore I do not want to have a project reference. I tried removing log4net.dll from the GAC and now it seems to get copied locally as expected. Maybe someone could clarify on why this is the case? BB 2008/11/26 Radovan Raszka hasam.cz>

RE: configuration problems, not logging

Radovan Raszka — 2008-11-27T09:17:50

You probably missing these lines in your web.config / app.config

See http://logging.apache.org/log4net/release/manual/configuration.html, .config Files paragraph Radovan -----Původní zpráva----- Od: suedeuno [mailto:suedeuno< at >yahoo.com] Odesláno: 26. listopadu 2008 18:45 Komu: log4net-user< at >logging.apache.org Předmět: Re: configuration problems, not logging I created a unit test and got some debug info back finally but I'm unclear why it's happening. I'm calling Configure in my utility class -> public LogUtility() { log4net.Config.XmlConfigurator.Configure(); log = LogManager.GetLogger(System.Reflection.MethodBase.GetCurrentMethod().DeclaringType); } LogUtilityTests.LoggerIsSuccessful : Passedlog4net: log4net assembly [log4net, Version=1.2.10.0, Culture=neutral, PublicKeyToken=1b44e1d426115821]. Loaded from [Global Ass

Re: configuration problems, not logging

suedeuno — 2008-11-26T22:50:01

I got it to work. I removed a named logger in the config file and that seemed to make it work. Still not sure why I had to use attributes in the assemblyinfo files though, I was calling log4net.Config.XmlConfigurator.Configure(); in my logger class. Ron Grabowski wrote:

Re: configuration problems, not logging

Ron Grabowski — 2008-11-26T22:45:44

What happens when you make the buffer size 1? ----- Original Message ---- From: suedeuno yahoo.com> To: log4net-user< at >logging.apache.org Sent: Tuesday, November 25, 2008 3:05:29 PM Subject: configuration problems, not logging What's missing here? Using profiler, the database never receives the call. web.config: [snip]

Re: configuration problems, not logging

suedeuno — 2008-11-26T21:54:35

Ok, I added [assembly: XmlConfigurator()] to the AssemblyInfo files and the unit tests log the messages successfully however I still am unable to log from the web project. Ideas anyone?

Re: configuration problems, not logging

suedeuno — 2008-11-26T17:44:48

I created a unit test and got some debug info back finally but I'm unclear why it's happening. I'm calling Configure in my utility class -> public LogUtility() { log4net.Config.XmlConfigurator.Configure(); log = LogManager.GetLogger(System.Reflection.MethodBase.GetCurrentMethod().DeclaringType); } LogUtilityTests.LoggerIsSuccessful : Passedlog4net: log4net assembly [log4net, Version=1.2.10.0, Culture=neutral, PublicKeyToken=1b44e1d426115821]. Loaded from [Global Assembly Cache]. (.NET Runtime [2.0.50727.3053] on Microsoft Windows NT 5.1.2600 Service Pack 2) log4net: log4net assembly [log4net, Version=1.2.10.0, Culture=neutral, PublicKeyToken=1b44e1d426115821]. Loaded from [Global Assembly Cache]. (.NET Runtime [2.0.50727.3053] on Microsoft Windows NT 5.1.2600 Service Pack 2) log4net: DefaultRepositorySelector: defaultRepositoryType [log4net.Repository.Hierarchy.Hierarchy] log4net: DefaultRepositorySelector: defaultRepositoryType [log4net.Repository.Hi

gmane.comp.log.log4net.user

Re: error XmlConfigurator: Failed to parse config file.

Re: error XmlConfigurator: Failed to parse config file.

error XmlConfigurator: Failed to parse config file.

logging into different logfiles depending on parameter

Re: Best Way to Set Up Massive Number of Loggers

Re: Best Way to Set Up Massive Number of Loggers

RE: Best Way to Set Up Massive Number of Loggers

Best Way to Set Up Massive Number of Loggers

Re: Logging issue, Repository count is 1

RE: configuration problems, not logging

Logging issue, Repository count is 1

Re: Strong Name Key

Re: Strong Name Key

RE: Strong Name Key

Strong Name Key

Re: Log4net.dll reference copy-local=true not behaving as expected

RE: configuration problems, not logging

Re: configuration problems, not logging

Re: configuration problems, not logging

Re: configuration problems, not logging

Re: configuration problems, not logging