Re: NDC in threads?

Nicko Cadell wrote: The NDC is thread local and is used to differentiate between actions happening simultaneously but on different threads. Each thread starts with a separate empty stack. Do you need something different? No, I don't think so :-) Given the semantics of use, with a static Push metho

RE: NDC in threads?

The NDC is thread local and is used to differentiate between actions happening simultaneously but on different threads. Each thread starts with a separate empty stack. Do you need something different? Nicko > -Original Message- > From: Oliver Sturm [mailto:[EMAIL PROTECTED] > Sent: 14 F

RE: Programmatically determine if DOMConfigurator.Configure() failed

This is not possible with the current implementation. This may be something that we will look to add in future. Nicko > -Original Message- > From: Thibaut Barrère [mailto:[EMAIL PROTECTED] > Sent: 14 February 2005 15:25 > To: Log4NET User > Subject: Programmatically determine if > DOMC

RE: URI formats are not supported

Configuration watching is available when configuring programmatically, just use the ConfigureAndWatch method, however you are right in that watching is only available for config loaded from a local file. When loading config from a Stream or an XmlElement the built-in file system watching cannot be

RE: URI formats are not supported

Hey Nicko, thanks for the reply. Ok, if I understand correctly the cost for loading programmatically is that the "watch" capabilities would not be available. In that a client is running the software and we want to change the root context from WARN to DEBUG, the app would have to be restarted. Is th

Programmatically determine if DOMConfigurator.Configure() failed

Hi I've read the FAQ which tells this : "However, log4net will output a single message to System.Console.Error indicating that logging can not be performed." Is there a way to programmatically (rather than visually) diagnose a log4net initialisation failure (especially through DOMConfigurator) ?

Re: log4net, UDPAppender and Chainsaw v2

--- Chris Restall <[EMAIL PROTECTED]> wrote: > Provided I keep the remoteAddress set to the loopback "127.0.0.1", I > can > view the logging information via Chainsaw on my local machine. When > I > configure the UdpAppender on another machine on the same local > network > (no firewalls up) to po

NDC in threads?

Hey, I'm wondering: is there a way to log with a specific NDC from a thread while the rest of the application uses a different NDC (or an empty stack, rather)? It seems to me like the current mechanism can only be used to differentiate sequential parts of the application, not those which might be r

RE: FileAppender's OpenFile() has mandatory call to Directory.CreateDirectory(...)

This is a bug in the FileAppender. It has been fixed in the CVS repository. You can either make a local mod to your copy of the source or pull the CVS version of log4net and use that. The fix is to add an Directory.Exists check around the Directory.CreateDirectory. Nicko > -Original Message-

RE: Logging in a Web App (Threads, Sessions and Requests)

You can override the Application_PreRequestHandlerExecute method in your Global.asax. This method is called for each request just before the handler is run, i.e. it is called just before the code in your page is executed, but after authentication, caching, session resolution etc... protected void