Some Feedback from using Chainsaw V2 ...
Hi folks, I started to use Chainsaw V2 in production and would like to provide some feedback ... very politely of course and hoping I didn't miss something VERY obvious :-) +) it would be helpful to use command line parameters, i.e. to open chainsaw with XML logfile defined on the command line +) I think it would be also useful to have a reload button when looking at a XML logfile when not using Chainsaw Appender +) how can I close a tab?! +) is there a way to get rid of Welcome and chainsaw-log - our sysadmins are slightly confused +) Chainsaw provides a few predefined filter, e.g LEVEL == INFO - I think LEVEL INFO would be more intuitive for a user I hope this was helpful and not offending ;-) Cheers, Siegfried Goeschl - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Desperate - please help - only thing stopping us from going live
Hi David, I feel with you but it is a little bit difficult to help since I'm not an expert but I just created log4j.properties for a project +) the normal log message are going to console, file and xml +) I need the logs from yaafi.performance and yaafi.tracing be stored in a seperate logfiles since this is diagnostic stuff and would flood the normal logfile. Furthermore I'm using a diferent layout since these are CSV files +) at the very end I supress most messaged from log4j.logger.yaafi logger I think this is pretty much what you would need .. Have fun and don't forget to post a success story ... Siegfried Goeschl # # create three appenders # log4j.rootLogger=INFO, stdout, file, xml # # custom logfiles # log4j.category.yaafi.tracing = DEBUG, tracing log4j.additivity.yaafi.tracing = false log4j.category.yaafi.performance = DEBUG, performance log4j.additivity.yaafi.performance = false # # configure the stdout appender to go to the console # log4j.appender.stdout=org.apache.log4j.ConsoleAppender log4j.appender.stdout.layout=org.apache.log4j.PatternLayout log4j.appender.stdout.layout.ConversionPattern=%d [%t] %-5p %c %x - %m%n # # File Appender # log4j.appender.file=org.apache.log4j.RollingFileAppender log4j.appender.file.File=./temp/it20one-signature-service.log log4j.appender.file.MaxFileSize=1000KB log4j.appender.file.MaxBackupIndex=2 log4j.appender.file.layout=org.apache.log4j.PatternLayout log4j.appender.file.layout.ConversionPattern=%d [%t] %-5p %c %x - %m%n # # XML Layout # log4j.appender.xml=org.apache.log4j.FileAppender log4j.appender.xml.file=./temp/it20one-signature-service.log.xml log4j.appender.xml.layout=org.apache.log4j.xml.XMLLayout log4j.appender.xml.append=false # # Tracing Appender # log4j.appender.tracing = org.apache.log4j.RollingFileAppender log4j.appender.tracing.file = ./temp/tracing.csv log4j.appender.tracing.MaxFileSize=2000KB log4j.appender.tracing.layout=org.apache.log4j.PatternLayout log4j.appender.tracing.layout.conversionPattern=%d;%t;%m%n log4j.appender.tracing.threshold=DEBUG log4j.appender.tracing.append = true # # Performance Appender # log4j.appender.performance = org.apache.log4j.RollingFileAppender log4j.appender.performance.file = ./temp/performance.csv log4j.appender.performance.MaxFileSize=2000KB log4j.appender.performance.layout = org.apache.log4j.PatternLayout log4j.appender.performance.layout.conversionPattern = %d;%t;%m%n log4j.appender.performance.threshold=DEBUG log4j.appender.performance.append = true # # Additional settings for supressing unwanted logging # log4j.logger.yaafi=WARN David Thielen wrote: Hi; We're stuck on our logging properties (and I'm getting beat on a lot). And everything I have tried has not worked. Rather than show what I have tried, I figure it is easier to just list what we need. * This is on Tomcat so it must be a text (not xml) properties file. There is a bug in Tomcat that has problems with the xml file. * Three output destinations - console, tomcat.log, and windward.log. * Console - error on server. On dev boxes also need info for org.apache.catalina * tomcat.log - warn. If possible, nothing from net.windward * windward.log - info from net.windward This is driving me nuts because it is pretty simple and there has to be a simple way to do it. But everything I have tried has failed. If anyone could help, I would really appreciate it. Thanks - dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problems to use Chainsaw V2 using SocketAppenders
Hi Scott, that did the trick ... :-) One quick question - if I would use 1.3alpha6 than the location info does work? Thanks in advance Siegfried Goeschl Scott Deboy wrote: set locationInfo=false Log4j 1.2.x socketappender - Chainsaw V2 SocketReceiver can't read events that contain location info or MDC until we make the LoggingEvent fully serial-compatible between log4j 1.2.x and log4j 1.3 Also, if you use SocketAppender with other appenders (particularly fileAppender), make sure the socketappender is referenced first in the list of appenders - because %L, %M, patterns in a fileAppender layout will create location info automatically - the logging event is then handed off to the SocketAppender, but it already contains location info, and can't be serialized. If you need location info in Chainsaw V2, use a FileAppender with the %F, %L, %M patterns in the layout, and configure Chainsaw V2 with a LogFilePatternReceiver. Scott -Original Message- From: Siegfried Goeschl [mailto:[EMAIL PROTECTED] Sent: Tue 9/6/2005 10:43 AM To: log4j-user@logging.apache.org Subject: Problems to use Chainsaw V2 using SocketAppenders Hi folks, I came across the Chainsaw V2 and thought it would save my day but I'm unable to get it running +) I updated to log4j 1.2.11 since 1.3alpha6 breaks my code +) I can use the old chainsaw with no problem +) I never get any logging event using Chainsaw 2.0alpha Any ideas what went wrong Thanks in advance Siegfried Goeschl CHAINSAW CONFIG = ?xml version=1.0 encoding=UTF-8 ? !DOCTYPE log4j:configuration log4j:configuration xmlns:log4j=http://jakarta.apache.org/log4j/; debug=true plugin name=SocketReceiver class=org.apache.log4j.net.SocketReceiver param name=Port value=4445/ /plugin root level value=debug/ /root /log4j:configuration LOG4J PROPERTIES = og4j.appender.chainsaw=org.apache.log4j.net.SocketAppender log4j.appender.chainsaw.remoteHost=localhost log4j.appender.chainsaw.port=4445 log4j.appender.chainsaw.locationInfo=true - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problems to use Chainsaw V2 using SocketAppenders
Hi Scott, since my day is already saved I got it working with 1.3alpha-6 (even at 9pm in Old Europe). Another quick question since I'm not too familiar with the new version - I get the following exception Testcase: [EMAIL PROTECTED]:Caused an ERROR (class: org/apache/avalon/framework/logger/Log4JLogger, method: isFatalErrorEnabled signature: ()Z) Incompatible argument to function java.lang.VerifyError: (class: org/apache/avalon/framework/logger/Log4JLogger, method: isFatalErrorEnabled signature: ()Z) Incompatible argument to function at at.it20one.eprocurement.service.signature.SignatureServiceTestSetup.initialize(SignatureServiceTestSetup.java:87) at at.it20one.eprocurement.service.signature.SignatureServiceTestSetup.access$000(SignatureServiceTestSetup.java:22) at at.it20one.eprocurement.service.signature.SignatureServiceTestSetup$1.setUp(SignatureServiceTestSetup.java:55) at junit.extensions.TestSetup$1.protect(TestSetup.java:18) at junit.extensions.TestSetup.run(TestSetup.java:23) The avalon-framework-impl-4.2.0-jar and the new avalon-framework-impl-4.3-jar uses Log4JLogger.isFatalErrorEnabled () ... I assume that the method was long depracted and gone for ages ... :-) Cheers, Siegfried Goeschl Scott Deboy wrote: Yes, you can process events containing MDC and location info if the SocketAppender being used is from the latest log4j 1.3alpha jar. Scott -Original Message- From: Siegfried Goeschl [mailto:[EMAIL PROTECTED] Sent: Tue 9/6/2005 11:15 AM To: Log4J Users List Subject: Re: Problems to use Chainsaw V2 using SocketAppenders Hi Scott, that did the trick ... :-) One quick question - if I would use 1.3alpha6 than the location info does work? Thanks in advance Siegfried Goeschl Scott Deboy wrote: set locationInfo=false Log4j 1.2.x socketappender - Chainsaw V2 SocketReceiver can't read events that contain location info or MDC until we make the LoggingEvent fully serial-compatible between log4j 1.2.x and log4j 1.3 Also, if you use SocketAppender with other appenders (particularly fileAppender), make sure the socketappender is referenced first in the list of appenders - because %L, %M, patterns in a fileAppender layout will create location info automatically - the logging event is then handed off to the SocketAppender, but it already contains location info, and can't be serialized. If you need location info in Chainsaw V2, use a FileAppender with the %F, %L, %M patterns in the layout, and configure Chainsaw V2 with a LogFilePatternReceiver. Scott -Original Message- From: Siegfried Goeschl [mailto:[EMAIL PROTECTED] Sent: Tue 9/6/2005 10:43 AM To: log4j-user@logging.apache.org Subject: Problems to use Chainsaw V2 using SocketAppenders Hi folks, I came across the Chainsaw V2 and thought it would save my day but I'm unable to get it running +) I updated to log4j 1.2.11 since 1.3alpha6 breaks my code +) I can use the old chainsaw with no problem +) I never get any logging event using Chainsaw 2.0alpha Any ideas what went wrong Thanks in advance Siegfried Goeschl CHAINSAW CONFIG = ?xml version=1.0 encoding=UTF-8 ? !DOCTYPE log4j:configuration log4j:configuration xmlns:log4j=http://jakarta.apache.org/log4j/; debug=true plugin name=SocketReceiver class=org.apache.log4j.net.SocketReceiver param name=Port value=4445/ /plugin root level value=debug/ /root /log4j:configuration LOG4J PROPERTIES = og4j.appender.chainsaw=org.apache.log4j.net.SocketAppender log4j.appender.chainsaw.remoteHost=localhost log4j.appender.chainsaw.port=4445 log4j.appender.chainsaw.locationInfo=true - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
