- logback-user - mailman3.qos.ch

Logging binary data
by Shirahatti, Nikhil 21 Feb '12

21 Feb '12

Being a first time user, can logback be used to log binary data? This was not possible in log4j without writing custom appenders but still the message was always a string. Nikhil

3 2

Reconfiguring a sifting appender
by Mayfield, Rich 20 Feb '12

20 Feb '12

Our application includes the ability to change certain logging parameters – e.g. Alter the size of each log file, the number of backup files in a rolling appender, the file name, etc. I can do this with FileAppender and RollingFileAppender, and I can do this with appenders already created with a SiftingAppender as SiftingAppender provides access to any live appenders. What I cannot seem to do is reconfigure a SiftingAppender so that any new appenders it creates will have the new configuration. SiftingAppender stores a list of SAXEvent objects representing the appender configuration in the AppenderFactory, however access to the factory and configuration appears to be private. Am I missing something? Other than re-implementing a more open, re-configurable SiftingAppender is there a better way? Thanks much for your help.

1 0

logback in endorsed dir
by Ale Sarco 15 Feb '12

15 Feb '12

I have a webapp, running on Tomcat 7, which uses Corba to communicate with a backend. For performance issues, we use Jacorb instead of the Corba libraries included in the JDK (this is a similar situation as when wanting to use different libraries for XML), so we've put jacorb.jar in Tomcat's endorsed dir. So far so good, but Jacorb has a dependency to slf4j, so slf4j jars have to be in the endorsed directory as well, and since I want to migrate from log4j to logback, I had to put a copy of logback jars in endorsed as well. Now, the problem is logback can't find the logback.xml file which is in the classpath of the webapp (which is a child of the endorsed classpath), and therefore falling back to BasicConfigurator, which it's of no use in this case. I could always add a copy of logback.xml in endorsed, but that will cause a problem since we need to deploy to a few different environments, with different logback.xml in each case. It'll be quite difficult to change the deployment scripts automatically to put logback.xml in endorsed (it is not under my control), so I would prefer any other way to solve this problem. Any ideas? Thanks, Alex. -- View this message in context: http://old.nabble.com/logback-in-endorsed-dir-tp33329513p33329513.html Sent from the Logback User mailing list archive at Nabble.com.

1 0

Create a header line for my log file
by JavierL 15 Feb '12

15 Feb '12

Hi I am writen a special log for my application that ist a kind of cvs file. I would like to add a header line with the columns name at the top of the file. One and just one line at the top. Is it possible to configure logback to do that? Regards -- View this message in context: http://old.nabble.com/Create-a-header-line-for-my-log-file-tp33265695p33265… Sent from the Logback User mailing list archive at Nabble.com.

2 2

Re: [logback-user] Compiler selecting wrong Logger method
by Stein, Eric 13 Feb '12

13 Feb '12

<sigh/> I'm a nitwit. I got confused because at my last job we used a wrapper around slf4j, and the signature of the method was debug(String, Object...). Out of curiosity, is there a reason why that format wasn't used? The compiler should be smart enough to call the more specific debug(String, Object, Object) when appropriate. Changing from Object[] to Object... should also be backwards-compatible... Thanks, Marco! Eric -----Original Message----- From: logback-user-bounces(a)qos.ch [mailto:logback-user-bounces@qos.ch] On Behalf Of BRESCIANI, MARCO (MARCO) Sent: Monday, February 06, 2012 8:12 AM To: logback users list Subject: Re: [logback-user] Compiler selecting wrong Logger method If I'm not wrong, using - Object[] - or the variable list - Object... - is a bit different and in order to have the correct method, you should write this: LOGGER.debug("Hi {} {} {}", new Object[] { arg1, arg2, arg3 }); MARCO BRESCIANI ALCATEL-LUCENT SENIOR SW CRAFT TERMINAL DEVELOPMENT ENG NETWORKS - IP DIVISION WT PRODUCT UNIT via Trento, 30 - 20059 Vimercate (MB) - Italy Phone: +39 039 686 6279 Fax: +39 039 686 5600 Marco.Bresciani(a)alcatel-lucent.com -----Original Message----- From: logback-user-bounces(a)qos.ch [mailto:logback-user-bounces@qos.ch] On Behalf Of Stein, Eric Sent: Monday, February 06, 2012 1:59 PM To: logback-user(a)qos.ch Subject: [logback-user] Compiler selecting wrong Logger method I'm seeing a funny error when trying to write to logback. import org.slf4j.Logger; import org.slf4j.LoggerFactory; final String arg1 = "arg1"; final String arg2 = "arg2"; final String arg3 = "arg3"; LOGGER.debug("Hi {} {}", arg1, arg2); LOGGER.debug("Hi {} {} {}", new String[] { arg1, arg2, arg3 }); LOGGER.debug("Hi {} {} {}", arg1, arg2, arg3); The last line is giving this error message: The method debug(Marker, String, Object, Object) in the type Logger is not applicable for the arguments (String, String, String, String) I don't see why it isn't using the method whose signature is debug(String, Object[]), especially given that I'm not using a Marker. I'm running in Eclipse Indigo, and my classpath looks like this: logback-classic-1.0.0.jar logback-core-1.0.0.jar slf4j-api-1.6.4.jar Does anybody know why the compiler is using the wrong method? Thanks, Eric Stein _________________________________________________ Don't gamble with your environmental information. Learn how the world's largest on-demand environmental information management system can help you mitigate your operating risk: www.locustec.com. _______________________________________________ Logback-user mailing list Logback-user(a)qos.ch http://mailman.qos.ch/mailman/listinfo/logback-user _________________________________________________ Don't gamble with your environmental information. Learn how the world's largest on-demand environmental information management system can help you mitigate your operating risk: www.locustec.com.

5 12

Overriding the logback file in an application via a system property
by Michael McCarthy 13 Feb '12

13 Feb '12

I'm an application developer currently working with our sysops team around logging. Their problem is that everyone who writes an app logs in entirely their own way, often to the filesystem with no consideration for a standardised logging format. I've been looking into logback and so far so good...my idea is that when a developer deploys to the container, the container overrides the logback.xml file via the system property with it's own one, that then logs via gelf to something like graylog. I've been trying this locally and I don't seem to get any messages being sent to graylog...my suspicion is that jboss finds the application's logback file then ignores the system property. Am I correct in assuming this is right, or should the system property override the logback that is in the jar? Out of interest, does this seem a valid solution for standardised logging? Thanks Michael

2 1

Question about Socket Appenders
by George, Kenneth V [NTK] 06 Feb '12

06 Feb '12

Can you put a filter on a Socket Appender to send only events that have a specific MDC value, or do ALL events go across the socket? ________________________________ This e-mail may contain Sprint Nextel proprietary information intended for the sole use of the recipient(s). Any use by others is prohibited. If you are not the intended recipient, please contact the sender and delete all copies of the message.

1 0

Missing classfile with Filter Evaluator
by George, Kenneth V [NTK] 06 Feb '12

06 Feb '12

I am creating a filter for one of the appenders and I am getting this error: Exception in thread "main" java.lang.NoClassDefFoundError: org/codehaus/janino/ScriptEvaluator at ch.qos.logback.core.boolex.JaninoEventEvaluatorBase.start(JaninoEventEvaluatorBase.java:57) at ch.qos.logback.core.joran.action.NestedComplexPropertyIA.end(NestedComplexPropertyIA.java:167) at ch.qos.logback.core.joran.spi.Interpreter.callEndAction(Interpreter.java:318) at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:197) at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:183) at ch.qos.logback.core.joran.spi.EventPlayer.play(EventPlayer.java:62) at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:147) at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:133) at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:96) at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:73) at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:65) at ch.qos.logback.classic.net.SimpleSocketServer.configureLC(SimpleSocketServer.java:169) at ch.qos.logback.classic.net.SimpleSocketServer.main(SimpleSocketServer.java:67) Caused by: java.lang.ClassNotFoundException: org.codehaus.janino.ScriptEvaluator at java.net.URLClassLoader$1.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) ... 13 more I have attempted to look around and cannot find the class anywhere in the .jar files shipped with the product. Anyone know where it is? ________________________________ This e-mail may contain Sprint Nextel proprietary information intended for the sole use of the recipient(s). Any use by others is prohibited. If you are not the intended recipient, please contact the sender and delete all copies of the message.

4 4

Compiler selecting wrong Logger method
by Stein, Eric 06 Feb '12

06 Feb '12

I'm seeing a funny error when trying to write to logback. import org.slf4j.Logger; import org.slf4j.LoggerFactory; final String arg1 = "arg1"; final String arg2 = "arg2"; final String arg3 = "arg3"; LOGGER.debug("Hi {} {}", arg1, arg2); LOGGER.debug("Hi {} {} {}", new String[] { arg1, arg2, arg3 }); LOGGER.debug("Hi {} {} {}", arg1, arg2, arg3); The last line is giving this error message: The method debug(Marker, String, Object, Object) in the type Logger is not applicable for the arguments (String, String, String, String) I don't see why it isn't using the method whose signature is debug(String, Object[]), especially given that I'm not using a Marker. I'm running in Eclipse Indigo, and my classpath looks like this: logback-classic-1.0.0.jar logback-core-1.0.0.jar slf4j-api-1.6.4.jar Does anybody know why the compiler is using the wrong method? Thanks, Eric Stein _________________________________________________ Don't gamble with your environmental information. Learn how the world's largest on-demand environmental information management system can help you mitigate your operating risk: www.locustec.com.

2 1

logback 1.0 - pickup config change & reconfigure
by Sean Kennedy 06 Feb '12

06 Feb '12

Hi, I'm trying to get logback to read an external config xml and "scan" it for changes, I've setup an entry in web.xml and done it via an include.. All looks good when I run it, change is detected in external file , but changes to fillter logging levels are ignored, in fact if I blank the entire external file it's also ignored !! >From ready various other posts this should be possible , it was fixed in 0.9.16 but perhaps I've missed something fundamental I've changed the filter up to ERROR and I still get INFO output !! Web.xml <env-entry> <env-entry-name>logback-file</env-entry-name> <env-entry-type>java.lang.String</env-entry-type> <env-entry-value>C:/logback_properties/localhost/logon.xml</env-entry-value> </env-entry> Logback.xml <configuration scan="true" scanPeriod="10 seconds" debug="true" > <insertFromJNDI env-entry-name="java:comp/env/logback-file" as="logback-file" /> <include file="${logback-file}" /> </configuration> Logon.xml [i.e. external file] <?xml version="1.0" encoding="UTF-8"?> <included> <appender name="A1" class="ch.qos.logback.core.rolling.RollingFileAppender"> <filter class="ch.qos.logback.classic.filter.ThresholdFilter"> <level>INFO</level> </filter> <File>C:/logs/localhost/logon.log</File> <encoder> <pattern>%d{ISO8601} %-5p %c - %m%n</pattern> </encoder> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <fileNamePattern>C:/logs/localhost/logon.log.%d</fileNamePattern> <maxHistory>2</maxHistory> </rollingPolicy> </appender> <root level="DEBUG"> <appender-ref ref="A1"/> </root> </included>

2 3