Re: logging log4net exceptions to event log

2005-06-09 Thread hbmlists
Thanks for the reply Nicko. First I would clarify that I meant internal errors within log4net framework. My requirement is that if there is any internal error within log4net then that should be logged to event log. I am aware of the log4net.internal.debug setting but that logs not only errors

Chainsaw - SQLServer please help

2005-06-09 Thread Roland.Kofler
Hello everybody, Sorry if it is a little off topic, since Chainsaw - SQLServer interaction is not directly connected to log4net. But I hope that you in this list have the most experiences with this topic. I wanted to read my db logs with Chainsaw, so i configured a chainsaw.config http://jaka

Where are the DB Recievers?

2005-06-09 Thread Roland.Kofler
Hi, As my Chainsaw Log gave me Failed to locate Receiver class:org.apache.log4j.db.DBReceiver Failed to locate Receiver class:org.apache.log4j.db.CustomSQLDBReceiver I searched them in the CVS. Hum Hum, cant find em... Why, where, how??? Thank you a lot

Re: log4net.Config.XmlConfigurator.ConfigureAndWatch()

2005-06-09 Thread Ron Grabowski
log4net should never raise an exception. Its been designed to not interfere with your application. If you do not call Configure, log4net will not configure itself. --- [EMAIL PROTECTED] wrote: > > Hi > > I would like to know what will happen if I get a logger using > LogManager and > make a l

Re: Chainsaw - SQLServer please help

2005-06-09 Thread Ron Grabowski
Have you verified that com.microsoft.jdbc.sqlserver.SQLServerDriver is in your class path? Scott Deboy on the log4j list is the Chainsaw guru. Here is one of his example reciever files for SQL Server: http://tinyurl.com/99uf5 http://www.mail-archive.com/log4j-user%40logging.apache.org/msg03466.htm

Re: log4net.Config.XmlConfigurator.ConfigureAndWatch()

2005-06-09 Thread hbmlists
Ron, I agree that log4net should never raise an exception. But my suggestion is that it should atleast log some message to signal that Configure has not been called. Thanks, Hemant Ron Grabowski writes: log4net should never raise an exception. Its been designed to not interfere with you

error log truncated

2005-06-09 Thread hbmlists
Hi, My web.config contains following setting.. My log4net.config file was not well formed and hence got following error in the log4net.log file... "log4net: log4net assembly [log4net, Version=1.2.9.0, Culture=neutral, PublicKeyToken=b32731d11ce58905]. Loaded

file appender in web apps

2005-06-09 Thread hbmlists
Hi, I am using log4net 1.2.9 and .Net 1.1 I am planning to use a file appender to log Debug messages for a web application. Are there any drawbacks/limitations in using file appender for a web app given the fact that there will be many concurrent users. Also ideally what should be the locki

Re: error log truncated

2005-06-09 Thread Ron Grabowski
According to the documentation for the TraceListener class: http://tinyurl.com/93pbk http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfsystemdiagnosticstracelistenerclasstopic.asp You may need to set the autoflush property to true: --- [EMAIL PROTECTED] wrote:

Re: file appender in web apps

2005-06-09 Thread Ron Grabowski
I've been using log4net's FileAppender to record debug messages in web apps for several months and have not noticed any issues. The ideal lock is Exclusive so the file does not need to be re-opened then closed for every log message. The lock is released when the app is shut down or it re-cycles (i.

Re: error log truncated

2005-06-09 Thread Ron Grabowski
doh! --- Ron Grabowski <[EMAIL PROTECTED]> wrote: > According to the documentation for the TraceListener class: > > http://tinyurl.com/93pbk > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfsystemdiagnosticstracelistenerclasstopic.asp > > You may need to set

Re: logging log4net exceptions to event log

2005-06-09 Thread Ron Grabowski
You could write your own EventLogTraceListener (System.Diagnostics.EventLogTraceListener is sealed) that looks for trace messages beginning with the following prefixes: log4net: log4net:WARN log4net:ERROR And logs those messages to the Event Log accordingly. Here is an example that shows how

AW: Chainsaw - SQLServer please help

2005-06-09 Thread Roland.Kofler
Thank you i will send my problem to the log4j list -Ursprüngliche Nachricht- Von: Ron Grabowski [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 09. Juni 2005 15:10 An: Log4NET User Betreff: Re: Chainsaw - SQLServer please help Have you verified that com.microsoft.jdbc.sqlserver.SQLServe

Re: log4net.Config.XmlConfigurator.ConfigureAndWatch()

2005-06-09 Thread Surya Jakhotia
Is this what you are looking for?   http://logging.apache.org/log4net/release/manual/faq.html#internalDebug   Thanks, Surya  On 6/9/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: Ron,I agree that log4net should never raise an exception. But my suggestion isthat it should atleast log some message