You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4net-user@logging.apache.org by Todd Bradley <To...@nirvanix.com> on 2013/08/28 15:49:47 UTC

Chainsaw

Years ago I when I first learned Apache Logging, it was with log4j. And later, the Chainsaw GUI app came along, which was very useful. Now I'm using log4net, and decided that Chainsaw might be a good way to monitor my application's logging in real time. But I was surprised to see that the most recent build is from early 2006, well over 7 years ago. Am I looking in the right place?

http://logging.apache.org/chainsaw/download.html

It seems hard to believe that Chainsaw hasn't advanced since then. It starts up on my Windows 7 desktop, but the GUI behavior is a bit weird so far. So I'm wondering if the app is really compatible with current Java versions. Do any of you use Chainsaw with log4net, and - if so - is this the correct build for me to use?


Thanks,
Todd.

Re: Chainsaw

Posted by Christian Grobmeier <gr...@gmail.com>.
Thats right, Chainsaw is discussed on log4j-(user|dev).

That said, there is an updated client on Scotts people server somewhere.
The official release is blocked by the release of the extras dependency.
Once resolved, Chainsaw will see a new version

If you ping log4j-dev/user, Scott will surely point you to the right
snapshot version

Am 28.08.13 16:22, schrieb Dominik Psenner:
>
> Hi Todd,
>
>  
>
> You happen to be on the wrong list. This is the log4net mailing list.
>
>  
>
> Cheers
>
>  
>
> *Von:* Todd Bradley [mailto:Todd.Bradley@nirvanix.com]
> *Gesendet:* Mittwoch, 28. August 2013 15:50
> *An:* log4net-user@logging.apache.org
> *Betreff:* Chainsaw
>
>  
>
> Years ago I when I first learned Apache Logging, it was with log4j.
> And later, the Chainsaw GUI app came along, which was very useful. Now
> I'm using log4net, and decided that Chainsaw might be a good way to
> monitor my application's logging in real time. But I was surprised to
> see that the most recent build is from early 2006, well over 7 years
> ago. Am I looking in the right place?
>
>  
>
> http://logging.apache.org/chainsaw/download.html
>
>  
>
> It seems hard to believe that Chainsaw hasn't advanced since then. It
> starts up on my Windows 7 desktop, but the GUI behavior is a bit weird
> so far. So I'm wondering if the app is really compatible with current
> Java versions. Do any of you use Chainsaw with log4net, and -- if so
> -- is this the correct build for me to use?
>
>  
>
>  
>
> Thanks,
>
> Todd.
>

AW: Chainsaw

Posted by Dominik Psenner <dp...@gmail.com>.
Hi Todd,

 

You happen to be on the wrong list. This is the log4net mailing list.

 

Cheers

 

Von: Todd Bradley [mailto:Todd.Bradley@nirvanix.com] 
Gesendet: Mittwoch, 28. August 2013 15:50
An: log4net-user@logging.apache.org
Betreff: Chainsaw

 

Years ago I when I first learned Apache Logging, it was with log4j. And
later, the Chainsaw GUI app came along, which was very useful. Now I'm using
log4net, and decided that Chainsaw might be a good way to monitor my
application's logging in real time. But I was surprised to see that the most
recent build is from early 2006, well over 7 years ago. Am I looking in the
right place?

 

http://logging.apache.org/chainsaw/download.html

 

It seems hard to believe that Chainsaw hasn't advanced since then. It starts
up on my Windows 7 desktop, but the GUI behavior is a bit weird so far. So
I'm wondering if the app is really compatible with current Java versions. Do
any of you use Chainsaw with log4net, and - if so - is this the correct
build for me to use?

 

 

Thanks,

Todd.

Re: Chainsaw

Posted by Christian Grobmeier <gr...@gmail.com>.
Todd,

Am 29.08.13 18:43, schrieb Todd Bradley:
>
> Thanks to Dominik, Christian, and Scott for your replies.  It's great
> to have so much help, even if some of it contradicts each other. As
> far as which list is right, I assumed this would be the place to go
> for help using Chainsaw and log4net together. Dominik and Christian
> say that's wrong, Scott says that's possibly right. Oh well.
>
when it comes to Chainsaw, Scott is your expert. Chainsaw itself is
usually discussed on log4j-*.. I was not sure if Scott would read
log4-net lists, but it seems he does and so what he says counts again.
So feel free to keep on asking here.

>  I did download the Chainsaw snapshot from Scott's site and it's
> working great with my log4net app -- way better than the older version
> I originally tried. I think this combination will catch on where I
> work as a useful tool for both Development and QA.
>
Thats great to hear! Thanks for the feedback!

Cheers
Christian
>
>  
>
>  
>
> Cheers,
>
> Todd.
>
>  
>
>  
>
> *From:*Scott Deboy [mailto:scott.deboy@gmail.com]
> *Sent:* Wednesday, August 28, 2013 8:41 AM
> *To:* Log4NET User
> *Subject:* Re: Chainsaw
>
>  
>
> There is a developer snapshot of Chainsaw which includes a lot of new
> features and an improved UI.
>
> It's available here: http://people.apache.org/~sdeboy
> <http://people.apache.org/%7Esdeboy>
>
> With this version of Chainsaw you can use the Udp appender support in
> log4net (specify the log4j xml layout) with a Udp receiver.
>
> You can also have Chainsaw tail a regular text log file.
>
> The Chainsaw config screen will walk you through settings needed to
> tail a local file and will define a VFSLogFilePatternReceiver.
>
> Tailing a log file on a remote windows machine requires downloading
> the NFS support from the Apache Commons VFS project and installing it
> next to the other Chainsaw jars.
>
> Feel free to send any Chainsaw questions to this list or the log4j list.
>
> Scott
>
> On Aug 28, 2013 6:50 AM, "Todd Bradley" <Todd.Bradley@nirvanix.com
> <ma...@nirvanix.com>> wrote:
>
> Years ago I when I first learned Apache Logging, it was with log4j.
> And later, the Chainsaw GUI app came along, which was very useful. Now
> I'm using log4net, and decided that Chainsaw might be a good way to
> monitor my application's logging in real time. But I was surprised to
> see that the most recent build is from early 2006, well over 7 years
> ago. Am I looking in the right place?
>
>  
>
> http://logging.apache.org/chainsaw/download.html
>
>  
>
> It seems hard to believe that Chainsaw hasn't advanced since then. It
> starts up on my Windows 7 desktop, but the GUI behavior is a bit weird
> so far. So I'm wondering if the app is really compatible with current
> Java versions. Do any of you use Chainsaw with log4net, and -- if so
> -- is this the correct build for me to use?
>
>  
>
>  
>
> Thanks,
>
> Todd.
>

AW: Thread Safety in Log

Posted by Dominik Psenner <dp...@gmail.com>.
At this point I usually quote Hector Correa:

 

 <http://hectorcorrea.com/blog/log4net-thread-safe-but-not-process-safe>
http://hectorcorrea.com/blog/log4net-thread-safe-but-not-process-safe

 

You can verify that log4net is indeed thread safe with a 3 liner console
application. However,  most people confuse thread safety with process
safety. log4net is – like many other programs - not process safe and that
has been written down in the FAQ several years ago:

 

 <http://logging.apache.org/log4net/release/faq.html#single-file>
http://logging.apache.org/log4net/release/faq.html#single-file

 

If log4net does not what you want it to do, then you’re probably using it in
a way it was not intended to be used.

 

Von: Rafael Thome Guimaraes [mailto:p-rguimaraes@bvmf.com.br] 
Gesendet: Freitag, 6. September 2013 00:52
An: Bill Sorensen; Log4NET User
Betreff: RE: Thread Safety in Log

 

Hi Bill!

 

Thanks for your answer!

 

My case is exactly the one of the l4ndash link you passed. I am using
“RollingFileAppender” through the ILog interface.

 

“

[…]

 

//Class field

private static ILog log =
LogManager.GetLogger(typeof(RSFNMessageBatchService));

 

[…]

 

//In the class constructor

log4net.GlobalContext.Properties["LogName"] =
AppSettings.GetValue("logFileName");

log4net.Config.XmlConfigurator.ConfigureAndWatch(new
System.IO.FileInfo(AppSettings.GetValue("log4NetConfigFile")));

log.Logger.Repository.Configured = true;

 

[…]

 

//Log call

log.Debug(mensagemLog);

 

[…]

 

”

 

In another file I just got, The trimmed message and the trimming message
came from the same thread! That eliminates the Thread Safety hypothesis.

 

Any ideas?

 

Thanks,

Rafael Thomé Guimarães

Analista-Programador

DO-CBCN / DI-CRAD - MIDDLEWARE

' +55 11 2565-7006

* p-rguimaraes@bvmf.com.br <ma...@bvmf.com.br> 



 

www.bmfbovespa.com.br <http://www.bmfbovespa.com.br/> 

 

 

Evite imprimir. Colabore com o Meio Ambiente!

 

 

 

From: Bill Sorensen [mailto:bsorensen@idtdna.com] 
Sent: quinta-feira, 5 de setembro de 2013 19:16
To: Rafael Thome Guimaraes; Log4NET User
Subject: RE: Thread Safety in Log

 

One of our developers (Eric Borman) researched this recently, so I’ll quote
him:

 

The short answer is that log4net is thread safe, the appenders are not.
log4net takes this into account and ensures proper serialization of logging
events. So as long as you use the logging API and don’t access the appender
directly you are safe.

 

http://stackoverflow.com/questions/1519211/multithread-safe-logging

http://www.l4ndash.com/Log4NetMailArchive%2Ftabid%2F70%2Fforumid%2F1%2Fposti
d%2F17279%2Fview%2Ftopic%2FDefault.aspx

 

However,

That does not make them process safe. So using a web garden will cause
collisions. 

 

http://hectorcorrea.com/blog/log4net-thread-safe-but-not-process-safe

 

Thanks,

_________________________________

Bill Sorensen

Patterns, Platforms and Practices

Integrated DNA Technologies

www.idtdna.com <http://www.idtdna.com> 

 

From: Rafael Thome Guimaraes [mailto:p-rguimaraes@bvmf.com.br] 
Sent: Thursday, September 05, 2013 3:49 PM
To: Log4NET User
Subject: Thread Safety in Log

 

Hi all!

 

Anyone knows if Log4Net is Thread Safe or I need to put locks in the calls?

 

Tks,

Rafael Thomé Guimarães

 

  _____  


Esta mensagem pode conter informação confidencial e/ou privilegiada. Se você
não for o destinatário ou a pessoa autorizada a receber esta mensagem, não
deverá utilizar, copiar, alterar, divulgar a informação nela contida ou
tomar qualquer ação baseada nessas informações. Se você recebeu esta
mensagem por engano, por favor avise imediatamente o remetente, respondendo
o e-mail e em seguida apague-o. Agradecemos sua cooperação.

This message may contain confidential and/or privileged information. If you
are not the addressee or authorized to receive this for the addressee, you
must not use, copy, disclose, change, take any action based on this message
or any information herein. If you have received this message in error,
please advise the sender immediately by reply e-mail and delete this
message. Thank you for your cooperation.

RE: Thread Safety in Log

Posted by Rafael Thome Guimaraes <p-...@bvmf.com.br>.
Hi Bill!

Thanks for your answer!

My case is exactly the one of the l4ndash link you passed. I am using "RollingFileAppender" through the ILog interface.

"
[...]

//Class field
private static ILog log = LogManager.GetLogger(typeof(RSFNMessageBatchService));

[...]

//In the class constructor
log4net.GlobalContext.Properties["LogName"] = AppSettings.GetValue("logFileName");
log4net.Config.XmlConfigurator.ConfigureAndWatch(new System.IO.FileInfo(AppSettings.GetValue("log4NetConfigFile")));
log.Logger.Repository.Configured = true;

[...]

//Log call
log.Debug(mensagemLog);

[...]

"

In another file I just got, The trimmed message and the trimming message came from the same thread! That eliminates the Thread Safety hypothesis.

Any ideas?

Thanks,
Rafael Thomé Guimarães
Analista-Programador
DO-CBCN / DI-CRAD - MIDDLEWARE
' +55 11 2565-7006
* p-rguimaraes@bvmf.com.br<ma...@bvmf.com.br>
[cid:image001.gif@01C9D55A.E5179270]

www.bmfbovespa.com.br<http://www.bmfbovespa.com.br/>


[cid:image003.gif@01CBD760.1C45F490]Evite imprimir. Colabore com o Meio Ambiente!



From: Bill Sorensen [mailto:bsorensen@idtdna.com]
Sent: quinta-feira, 5 de setembro de 2013 19:16
To: Rafael Thome Guimaraes; Log4NET User
Subject: RE: Thread Safety in Log

One of our developers (Eric Borman) researched this recently, so I'll quote him:

The short answer is that log4net is thread safe, the appenders are not. log4net takes this into account and ensures proper serialization of logging events. So as long as you use the logging API and don't access the appender directly you are safe.

http://stackoverflow.com/questions/1519211/multithread-safe-logging
http://www.l4ndash.com/Log4NetMailArchive%2Ftabid%2F70%2Fforumid%2F1%2Fpostid%2F17279%2Fview%2Ftopic%2FDefault.aspx

However,
That does not make them process safe. So using a web garden will cause collisions.

http://hectorcorrea.com/blog/log4net-thread-safe-but-not-process-safe

Thanks,
_________________________________
Bill Sorensen
Patterns, Platforms and Practices
Integrated DNA Technologies
www.idtdna.com<http://www.idtdna.com>

From: Rafael Thome Guimaraes [mailto:p-rguimaraes@bvmf.com.br]
Sent: Thursday, September 05, 2013 3:49 PM
To: Log4NET User
Subject: Thread Safety in Log

Hi all!

Anyone knows if Log4Net is Thread Safe or I need to put locks in the calls?

Tks,
Rafael Thomé Guimarães

________________________________

Esta mensagem pode conter informação confidencial e/ou privilegiada. Se você não for o destinatário ou a pessoa autorizada a receber esta mensagem, não deverá utilizar, copiar, alterar, divulgar a informação nela contida ou tomar qualquer ação baseada nessas informações. Se você recebeu esta mensagem por engano, por favor avise imediatamente o remetente, respondendo o e-mail e em seguida apague-o. Agradecemos sua cooperação.

This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, change, take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation.

RE: Thread Safety in Log

Posted by Bill Sorensen <bs...@idtdna.com>.
One of our developers (Eric Borman) researched this recently, so I'll quote him:

The short answer is that log4net is thread safe, the appenders are not. log4net takes this into account and ensures proper serialization of logging events. So as long as you use the logging API and don't access the appender directly you are safe.

http://stackoverflow.com/questions/1519211/multithread-safe-logging
http://www.l4ndash.com/Log4NetMailArchive%2Ftabid%2F70%2Fforumid%2F1%2Fpostid%2F17279%2Fview%2Ftopic%2FDefault.aspx

However,
That does not make them process safe. So using a web garden will cause collisions.

http://hectorcorrea.com/blog/log4net-thread-safe-but-not-process-safe

Thanks,
_________________________________
Bill Sorensen
Patterns, Platforms and Practices
Integrated DNA Technologies
www.idtdna.com

From: Rafael Thome Guimaraes [mailto:p-rguimaraes@bvmf.com.br]
Sent: Thursday, September 05, 2013 3:49 PM
To: Log4NET User
Subject: Thread Safety in Log

Hi all!

Anyone knows if Log4Net is Thread Safe or I need to put locks in the calls?

Tks,
Rafael Thomé Guimarães

RE: Thread Safety in Log

Posted by Rafael Thome Guimaraes <p-...@bvmf.com.br>.
One correction: I am using RollingFileAppender


Rafael Thomé Guimarães
Analista-Programador
DO-CBCN / DI-CRAD - MIDDLEWARE
' +55 11 2565-7006
* p-rguimaraes@bvmf.com.br<ma...@bvmf.com.br>
[cid:image001.gif@01C9D55A.E5179270]

www.bmfbovespa.com.br<http://www.bmfbovespa.com.br/>


[cid:image003.gif@01CBD760.1C45F490]Evite imprimir. Colabore com o Meio Ambiente!



From: Rafael Thome Guimaraes [mailto:p-rguimaraes@bvmf.com.br]
Sent: quinta-feira, 5 de setembro de 2013 19:33
To: Log4NET User
Subject: RE: Thread Safety in Log

Very Convenient in deed. Thank you very much, Todd!

But I am asking because I am running into a disturbing issue (at least for me).
I have a Pattern layout appender that, in some cases, is trimming the message.

At first I thought I was reaching some kind of buffer limit, but than I noticed I have longer messages logged OK in the same file.

Than, since the logger application is a per call instancing multiple concurrency WCF service, I supposed if log4net was not Thread Safe, the rest of the trimmed message could be somewhere behind in the file and other threads messages colud be in the middle. Being very big messages I was not able to find it.

But If log4net is thread safe, what can be happaning?

Can someone help me?

The pattern I am using is: "%-20.20level %-30.30date{dd/MM/yyyy HH:mm:ss,fff}        %username [Thread: %thread]        (%logger - %file:%line)        %message%newline"

Attached I am sending a file where it happened at line 9.

Note that %message is carrying a very long message with its particular layouT, wich is being generated trough c# code.

Thank you in advance,
Rafael Thomé Guimarães
Analista-Programador
DO-CBCN / DI-CRAD - MIDDLEWARE
' +55 11 2565-7006
* p-rguimaraes@bvmf.com.br<ma...@bvmf.com.br>
[cid:image001.gif@01C9D55A.E5179270]

www.bmfbovespa.com.br<http://www.bmfbovespa.com.br/>


[cid:image003.gif@01CBD760.1C45F490]Evite imprimir. Colabore com o Meio Ambiente!



From: Todd Bradley [mailto:Todd.Bradley@nirvanix.com]
Sent: quinta-feira, 5 de setembro de 2013 19:03
To: Log4NET User
Subject: RE: Thread Safety in Log

Let me direct you to the very convenient log4net FAQ:

http://log4net.sourceforge.net/release/1.2.0.30316/doc/manual/faq.html#thread-safety



From: Rafael Thome Guimaraes [mailto:p-rguimaraes@bvmf.com.br]
Sent: Thursday, September 05, 2013 2:49 PM
To: Log4NET User
Subject: Thread Safety in Log

Hi all!

Anyone knows if Log4Net is Thread Safe or I need to put locks in the calls?

Tks,
Rafael Thomé Guimarães
Analista-Programador
DO-CBCN / DI-CRAD - MIDDLEWARE
' +55 11 2565-7006
* p-rguimaraes@bvmf.com.br<ma...@bvmf.com.br>
[cid:image001.gif@01C9D55A.E5179270]

www.bmfbovespa.com.br<http://www.bmfbovespa.com.br/>


[cid:image003.gif@01CBD760.1C45F490]Evite imprimir. Colabore com o Meio Ambiente!

________________________________

Esta mensagem pode conter informação confidencial e/ou privilegiada. Se você não for o destinatário ou a pessoa autorizada a receber esta mensagem, não deverá utilizar, copiar, alterar, divulgar a informação nela contida ou tomar qualquer ação baseada nessas informações. Se você recebeu esta mensagem por engano, por favor avise imediatamente o remetente, respondendo o e-mail e em seguida apague-o. Agradecemos sua cooperação.

This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, change, take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation.

________________________________

Esta mensagem pode conter informação confidencial e/ou privilegiada. Se você não for o destinatário ou a pessoa autorizada a receber esta mensagem, não deverá utilizar, copiar, alterar, divulgar a informação nela contida ou tomar qualquer ação baseada nessas informações. Se você recebeu esta mensagem por engano, por favor avise imediatamente o remetente, respondendo o e-mail e em seguida apague-o. Agradecemos sua cooperação.

This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, change, take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation.

________________________________

Esta mensagem pode conter informação confidencial e/ou privilegiada. Se você não for o destinatário ou a pessoa autorizada a receber esta mensagem, não deverá utilizar, copiar, alterar, divulgar a informação nela contida ou tomar qualquer ação baseada nessas informações. Se você recebeu esta mensagem por engano, por favor avise imediatamente o remetente, respondendo o e-mail e em seguida apague-o. Agradecemos sua cooperação.

This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, change, take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation.

RE: Thread Safety in Log

Posted by Rafael Thome Guimaraes <p-...@bvmf.com.br>.
Very Convenient in deed. Thank you very much, Todd!

But I am asking because I am running into a disturbing issue (at least for me).
I have a Pattern layout appender that, in some cases, is trimming the message.

At first I thought I was reaching some kind of buffer limit, but than I noticed I have longer messages logged OK in the same file.

Than, since the logger application is a per call instancing multiple concurrency WCF service, I supposed if log4net was not Thread Safe, the rest of the trimmed message could be somewhere behind in the file and other threads messages colud be in the middle. Being very big messages I was not able to find it.

But If log4net is thread safe, what can be happaning?

Can someone help me?

The pattern I am using is: "%-20.20level %-30.30date{dd/MM/yyyy HH:mm:ss,fff}        %username [Thread: %thread]        (%logger - %file:%line)        %message%newline"

Attached I am sending a file where it happened at line 9.

Note that %message is carrying a very long message with its particular layouT, wich is being generated trough c# code.

Thank you in advance,
Rafael Thomé Guimarães
Analista-Programador
DO-CBCN / DI-CRAD - MIDDLEWARE
' +55 11 2565-7006
* p-rguimaraes@bvmf.com.br<ma...@bvmf.com.br>
[cid:image001.gif@01C9D55A.E5179270]

www.bmfbovespa.com.br<http://www.bmfbovespa.com.br/>


[cid:image003.gif@01CBD760.1C45F490]Evite imprimir. Colabore com o Meio Ambiente!



From: Todd Bradley [mailto:Todd.Bradley@nirvanix.com]
Sent: quinta-feira, 5 de setembro de 2013 19:03
To: Log4NET User
Subject: RE: Thread Safety in Log

Let me direct you to the very convenient log4net FAQ:

http://log4net.sourceforge.net/release/1.2.0.30316/doc/manual/faq.html#thread-safety



From: Rafael Thome Guimaraes [mailto:p-rguimaraes@bvmf.com.br]
Sent: Thursday, September 05, 2013 2:49 PM
To: Log4NET User
Subject: Thread Safety in Log

Hi all!

Anyone knows if Log4Net is Thread Safe or I need to put locks in the calls?

Tks,
Rafael Thomé Guimarães
Analista-Programador
DO-CBCN / DI-CRAD - MIDDLEWARE
' +55 11 2565-7006
* p-rguimaraes@bvmf.com.br<ma...@bvmf.com.br>
[cid:image001.gif@01C9D55A.E5179270]

www.bmfbovespa.com.br<http://www.bmfbovespa.com.br/>


[cid:image003.gif@01CBD760.1C45F490]Evite imprimir. Colabore com o Meio Ambiente!

________________________________

Esta mensagem pode conter informação confidencial e/ou privilegiada. Se você não for o destinatário ou a pessoa autorizada a receber esta mensagem, não deverá utilizar, copiar, alterar, divulgar a informação nela contida ou tomar qualquer ação baseada nessas informações. Se você recebeu esta mensagem por engano, por favor avise imediatamente o remetente, respondendo o e-mail e em seguida apague-o. Agradecemos sua cooperação.

This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, change, take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation.

________________________________

Esta mensagem pode conter informação confidencial e/ou privilegiada. Se você não for o destinatário ou a pessoa autorizada a receber esta mensagem, não deverá utilizar, copiar, alterar, divulgar a informação nela contida ou tomar qualquer ação baseada nessas informações. Se você recebeu esta mensagem por engano, por favor avise imediatamente o remetente, respondendo o e-mail e em seguida apague-o. Agradecemos sua cooperação.

This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, change, take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation.

RE: Thread Safety in Log

Posted by Todd Bradley <To...@nirvanix.com>.
Let me direct you to the very convenient log4net FAQ:

http://log4net.sourceforge.net/release/1.2.0.30316/doc/manual/faq.html#thread-safety



From: Rafael Thome Guimaraes [mailto:p-rguimaraes@bvmf.com.br]
Sent: Thursday, September 05, 2013 2:49 PM
To: Log4NET User
Subject: Thread Safety in Log

Hi all!

Anyone knows if Log4Net is Thread Safe or I need to put locks in the calls?

Tks,
Rafael Thomé Guimarães
Analista-Programador
DO-CBCN / DI-CRAD - MIDDLEWARE
' +55 11 2565-7006
* p-rguimaraes@bvmf.com.br<ma...@bvmf.com.br>
[cid:image001.gif@01C9D55A.E5179270]

www.bmfbovespa.com.br<http://www.bmfbovespa.com.br/>


[cid:image003.gif@01CBD760.1C45F490]Evite imprimir. Colabore com o Meio Ambiente!

________________________________

Esta mensagem pode conter informação confidencial e/ou privilegiada. Se você não for o destinatário ou a pessoa autorizada a receber esta mensagem, não deverá utilizar, copiar, alterar, divulgar a informação nela contida ou tomar qualquer ação baseada nessas informações. Se você recebeu esta mensagem por engano, por favor avise imediatamente o remetente, respondendo o e-mail e em seguida apague-o. Agradecemos sua cooperação.

This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, change, take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation.

Thread Safety in Log

Posted by Rafael Thome Guimaraes <p-...@bvmf.com.br>.
Hi all!

Anyone knows if Log4Net is Thread Safe or I need to put locks in the calls?

Tks,
Rafael Thomé Guimarães
Analista-Programador
DO-CBCN / DI-CRAD - MIDDLEWARE
' +55 11 2565-7006
* p-rguimaraes@bvmf.com.br<ma...@bvmf.com.br>
[cid:image001.gif@01C9D55A.E5179270]

www.bmfbovespa.com.br<http://www.bmfbovespa.com.br/>


[cid:image003.gif@01CBD760.1C45F490]Evite imprimir. Colabore com o Meio Ambiente!

________________________________

Esta mensagem pode conter informação confidencial e/ou privilegiada. Se você não for o destinatário ou a pessoa autorizada a receber esta mensagem, não deverá utilizar, copiar, alterar, divulgar a informação nela contida ou tomar qualquer ação baseada nessas informações. Se você recebeu esta mensagem por engano, por favor avise imediatamente o remetente, respondendo o e-mail e em seguida apague-o. Agradecemos sua cooperação.

This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, change, take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation.

RE: Chainsaw

Posted by Todd Bradley <To...@nirvanix.com>.
Thanks to Dominik, Christian, and Scott for your replies.  It's great to have so much help, even if some of it contradicts each other. As far as which list is right, I assumed this would be the place to go for help using Chainsaw and log4net together. Dominik and Christian say that's wrong, Scott says that's possibly right. Oh well.

I did download the Chainsaw snapshot from Scott's site and it's working great with my log4net app - way better than the older version I originally tried. I think this combination will catch on where I work as a useful tool for both Development and QA.


Cheers,
Todd.


From: Scott Deboy [mailto:scott.deboy@gmail.com]
Sent: Wednesday, August 28, 2013 8:41 AM
To: Log4NET User
Subject: Re: Chainsaw


There is a developer snapshot of Chainsaw which includes a lot of new features and an improved UI.

It's available here: http://people.apache.org/~sdeboy

With this version of Chainsaw you can use the Udp appender support in log4net (specify the log4j xml layout) with a Udp receiver.

You can also have Chainsaw tail a regular text log file.

The Chainsaw config screen will walk you through settings needed to tail a local file and will define a VFSLogFilePatternReceiver.

Tailing a log file on a remote windows machine requires downloading the NFS support from the Apache Commons VFS project and installing it next to the other Chainsaw jars.

Feel free to send any Chainsaw questions to this list or the log4j list.

Scott
On Aug 28, 2013 6:50 AM, "Todd Bradley" <To...@nirvanix.com>> wrote:
Years ago I when I first learned Apache Logging, it was with log4j. And later, the Chainsaw GUI app came along, which was very useful. Now I'm using log4net, and decided that Chainsaw might be a good way to monitor my application's logging in real time. But I was surprised to see that the most recent build is from early 2006, well over 7 years ago. Am I looking in the right place?

http://logging.apache.org/chainsaw/download.html

It seems hard to believe that Chainsaw hasn't advanced since then. It starts up on my Windows 7 desktop, but the GUI behavior is a bit weird so far. So I'm wondering if the app is really compatible with current Java versions. Do any of you use Chainsaw with log4net, and - if so - is this the correct build for me to use?


Thanks,
Todd.

Re: Chainsaw

Posted by Scott Deboy <sc...@gmail.com>.
There is a developer snapshot of Chainsaw which includes a lot of new
features and an improved UI.

It's available here: http://people.apache.org/~sdeboy

With this version of Chainsaw you can use the Udp appender support in
log4net (specify the log4j xml layout) with a Udp receiver.

You can also have Chainsaw tail a regular text log file.

The Chainsaw config screen will walk you through settings needed to tail a
local file and will define a VFSLogFilePatternReceiver.

Tailing a log file on a remote windows machine requires downloading the NFS
support from the Apache Commons VFS project and installing it next to the
other Chainsaw jars.

Feel free to send any Chainsaw questions to this list or the log4j list.

Scott
 On Aug 28, 2013 6:50 AM, "Todd Bradley" <To...@nirvanix.com> wrote:

>  Years ago I when I first learned Apache Logging, it was with log4j. And
> later, the Chainsaw GUI app came along, which was very useful. Now I’m
> using log4net, and decided that Chainsaw might be a good way to monitor my
> application’s logging in real time. But I was surprised to see that the
> most recent build is from early 2006, well over 7 years ago. Am I looking
> in the right place?****
>
> ** **
>
> http://logging.apache.org/chainsaw/download.html****
>
> ** **
>
> It seems hard to believe that Chainsaw hasn’t advanced since then. It
> starts up on my Windows 7 desktop, but the GUI behavior is a bit weird so
> far. So I’m wondering if the app is really compatible with current Java
> versions. Do any of you use Chainsaw with log4net, and – if so – is this
> the correct build for me to use?****
>
> ** **
>
> ** **
>
> Thanks,****
>
> Todd.****
>