November 2011 - logback-user

Custom appender and layout issue
by Adam Gordon 10 Nov '11

10 Nov '11

I'm trying to port my log4j appender and layout over to logback but am running into some issues. My log4j appender colorizes the timestamp printed in the logs and the layout colorizes the log messages based on level - at least, in theory. I think I've correctly configured everything in the XML but my classes are not quite correct. I'm getting the colored timestamp and I'm partially getting the colorized log messages, but am not getting the pattern I've specified in my XML and the log messages are all smushed together back to back. I suspect I'm not overriding the right methods or not calling them in the right order or place. Here's my appender XML: <appender name="foouilog" class="com.foo.logging.FooRollingFileAppender"> <file>/usr/local/tomcat/logs/fooui.log</file> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">  <fileNamePattern>/usr/local/tomcat/logs/fooui-%d{yyyy-MM-dd}.%i.gz</fileNamePattern> <maxHistory>10</maxHistory> <timeBasedFileNamingAndTriggeringPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP"> <maxFileSize>25MB</maxFileSize> </timeBasedFileNamingAndTriggeringPolicy> </rollingPolicy> <encoder class="ch.qos.logback.core.encoder.LayoutWrappingEncoder"> <layout class="com.foo.logging.AnsiColorLayout"/> <pattern>%date{ISO8601} %p [%logger{5}.%method:%line] - %msg%n%rEx</pattern> </encoder> </appender> And here's the relevant Java code: Appender: public class FooRollingFileAppender extends RollingFileAppender<ILoggingEvent> { *** snip *** public void append(ILoggingEvent eventObject) { OutputStream os = this.getOutputStream(); // code to write out color formatted timestamp os.flush(); super.append(eventObject); } *** snip *** } Layout: public class AnsiColorLayout extends LayoutBase<ILoggingEvent> { *** snip *** public String doLayout(ILoggingEvent event) { return this.format(event); } private String format(ILoggingEvent event) { StringBuilder sb = new StringBuilder(); switch (event.getLevel().toInt()) { *** snip *** } sb.append(event.getFormattedMessage()); sb.append(COLOR_DEFAULT); return sb.toString(); } *** snip *** } Thanks, --adam http://gordonizer.com

2 9

Building logback when tests fail
by Thorbjørn Ravn Andersen 10 Nov '11

10 Nov '11

Hi. I am trying to set up Logback for development in order to write a JDK14Appender (based on the bridge) and my cloned source fails in testing with [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.6:test (default-test) on project logback-classic: There are test failures. so I cannot run the "mvn package" command listed on the documentation page. Running mvn -Dmaven.test.skip=true package gives me [ERROR] Failed to execute goal on project logback-classic: Could not resolve dependencies for project ch.qos.logback:logback-classic:jar:0.9.30-SNAPSHOT: Could not find artifact ch.qos.logback:logback -core:jar:tests:0.9.30-SNAPSHOT -> [Help 1] instead. I'd like to get this up and running in Eclipse but it is not quite easy even with both egit and Eclipse Maven plugins. What would you suggest me to do to get up and running? Thanks /Thorbjørn

3 11

logback.groovy configuration throws errors
by Tompi Mat 09 Nov '11

09 Nov '11

Hi, I am trying to use logback.groovy instead of logback.xml in my groovy project but I might be missing something: $ cat HelloWorld.groovy @Grab('org.slf4j:slf4j-api:1.6.1') @Grab('ch.qos.logback:logback-core:1.0.0') @Grab('ch.qos.logback:logback-classic:1.0.0') @Grab('ch.qos.logback:logback-examples:1.0.0') import org.slf4j.Logger import org.slf4j.LoggerFactory public class HelloWorld1 { public static void main(String[] args) { Logger logger = LoggerFactory.getLogger( "HelloWorld1" ) logger.warn("Hello world.") } } If I put the first example from http://logback.qos.ch/manual/configuration.html of sample0.xml as logback.xml, it seems to work perfect. If I put the logback.groovy equivalent instead, I get various errors, like : $ groovy HelloWorld.groovy Failed to instantiate [ch.qos.logback.classic.LoggerContext] Reported exception: org.codehaus.groovy.runtime.typehandling.GroovyCastException: Cannot cast object 'ch.qos.logback.core.ConsoleAppender[null]' with class 'ch.qos.logback.core.ConsoleAppender' to class 'ch.qos.logback.core.Appender' at org.codehaus.groovy.runtime.typehandling.DefaultTypeTransformation.castToType(DefaultTypeTransformation.java:331) If I only go with the simplest: root(DEBUG) then I get groovy.lang.MissingMethodException: No signature of method: Script1.root() is applicable for argument types: (ch.qos.logback.classic.Level) values: [DEBUG] Possible solutions: wait(), run(), run(), wait(long), print(java.lang.Object), print(java.lang.Object) Below is logback.groovy, could you enlighten me what I am doing wrong? Thanks, Tamas ============================ @Grab('ch.qos.logback:logback-core:1.0.0') @Grab('ch.qos.logback:logback-classic:1.0.0') @Grab('ch.qos.logback:logback-examples:1.0.0') import ch.qos.logback.classic.encoder.PatternLayoutEncoder import ch.qos.logback.core.ConsoleAppender import static ch.qos.logback.classic.Level.DEBUG //appender("STDOUT", ConsoleAppender) { // encoder(PatternLayoutEncoder) { // pattern = "%d{HH:mm:ss.SSS} XXX [%thread] %-5level %logger{36} - %msg%n" // } //} root(DEBUG) <http://logback.qos.ch/manual/configuration.html>

3 10

re ading variables from jdbc.properties file
by Jordan Blay 07 Nov '11

07 Nov '11

Hi! I have the following appender: <connectionSource class="ch.qos.logback.core.db.DataSourceConnectionSource"> <dataSource class="com.mchange.v2.c3p0.ComboPooledDataSource"> <driverClass>com.mysql.jdbc.Driver</driverClass> <jdbcUrl>${connection.url}</jdbcUrl> <user>${connection.username}</user> <password>${connection.username}</password> </dataSource> </connectionSource> I also have the following: <property resource="jdbc.properties" /> The file is located under src - classpath and includes the variables However, I get error messages when I try to start tomcat unless I change the variables to static text. I also tried <property file="src/jdbc.properties /> but with no success What is wrong? -- View this message in context: http://old.nabble.com/reading-variables-from-jdbc.properties-file-tp3278873… Sent from the Logback User mailing list archive at Nabble.com.

3 6

RollingFileAppender With Crontab Configuration
by Andrew Bourgeois 07 Nov '11

07 Nov '11

Hello did anyone here develop some RollingFileAppender for LOGBack that works with a cron? The customer I work for has an old bugged appender for LOG4J that tries to do that and has the following configuration: log4j.appender.RollingFileCron=com.removed.log4j.RollingFileAppender log4j.appender.RollingFileCron.File=/var/log/removed/error.log log4j.appender.RollingFileCron.layout=org.apache.removed.PatternLayout log4j.appender.RollingFileCron.layout.ConversionPattern=%d{yyyy-MM-dd HH:mm:ss.SSS} %m%n log4j.appender.RollingFileCron.DatePattern='.'yyyy-MM-dd_HH-mm log4j.appender.RollingFileCron.CronPattern=*/5 * * * * I’m not allowed use the library in my personal “test” projects, and it’s bugged... Key points are: - It can roll files every 5 minutes, not just what the SimpleDateFormat offers. - It’ll roll even without logging activity (even empty files are rolled, to prove that the app’s logging is still working) ! If there’s anything that does that, please let me know, thank you very much. Best regards Andrew Bourgeois

1 0

SecurityManager issue using logback
by Andrew Bourgeois 06 Nov '11

06 Nov '11

Hello Ceki said my “bug” report isn’t actually a bug, but didn’t have the tell to tell me what’s wrong: http://jira.qos.ch/browse/LBCLASSIC-304 Can anyone here help? In short: package be.removed.fun.removed; import java.rmi.RMISecurityManager; import org.slf4j.Logger; import org.slf4j.LoggerFactory; public class TestMain { private static final Logger logger = LoggerFactory.getLogger(TestMain.class); public static void main(String[] args) throws Exception { System.setProperty("java.security.policy", "./src/main/config/java.policy"); logger.debug("Policy location: {}", System.getProperty("java.security.policy")); if (System.getSecurityManager() == null) { System.setSecurityManager(new RMISecurityManager()); } System.setProperty("java.security.policy", "./src/main/config/java.policy"); } } ...runs fine using log4j: <dependency> <groupId>org.slf4j</groupId> <artifactId>slf4j-api</artifactId> <version>1.6.0</version> </dependency> <dependency> <groupId>log4j</groupId> <artifactId>log4j</artifactId> <version>1.2.16</version> </dependency> <dependency> <groupId>org.slf4j</groupId> <artifactId>slf4j-log4j12</artifactId> <version>1.6.0</version> </dependency> ...and gives an exception when switching to logback: <dependency> <groupId>org.slf4j</groupId> <artifactId>slf4j-api</artifactId> <version>1.6.0</version> </dependency> <dependency> <groupId>ch.qos.logback</groupId> <artifactId>logback-core</artifactId> <version>1.0.0</version> </dependency> <dependency> <groupId>ch.qos.logback</groupId> <artifactId>logback-classic</artifactId> <version>1.0.0</version> </dependency> The exception is thrown at the last line of the main: 01:05:37.702 [main] DEBUG be.removed.fun.removed.TestMain - Policy location: ./src/main/config/java.policy Exception in thread "main" java.security.AccessControlException: access denied (java.util.PropertyPermission java.security.policy write) at java.security.AccessControlContext.checkPermission(AccessControlContext.java:323) at java.security.AccessController.checkPermission(AccessController.java:546) at java.lang.SecurityManager.checkPermission(SecurityManager.java:532) at java.lang.System.setProperty(System.java:725) at be.removed.fun.removed.TestMain.main(TestMain.java:18) The policy file is: grant { permission java.security.AllPermission; }; The problem gets fixed if I put this file into: $JAVA_HOME/jre/lib/security Thank you for your time! Best regards Andrew Bourgeois

4 13

Encoder pattern documentation?
by Andrew Bourgeois 06 Nov '11

06 Nov '11

Hello again can I find a complete documentation somewhere describing the “pattern” property of encoder? There are a few examples inside the documentation, but none of them are really exhaustive. I was surprised to see the output of: pattern = "%d{yyyy-MM-dd HH:mm:ss,SSS} [%t] %-5p - (%c) - %m%n" which wasn’t converted by the tools available (from my log4j.properties). Also... while it’s kind of obvious, I couldn’t find a sentence saying “for the Groovy configuration you need ‘groovy-1.8.3.jar’ on your classpath”. The only thing I found was: “GEventEvaluator depends on the Groovy runtime. It was tested with Groovy version 1.7.2. ” (source: http://logback.qos.ch/setup.html ). I may also have missed the page explaining it all, let me know if I did. Thank you for your time! Best regards Andrew Bourgeois

2 2

log4j to logback question
by Steve Cohen 06 Nov '11

06 Nov '11

how would I replace log4j's LoggingEvent.getLocationInformation() in logback?

3 3

Re: [logback-user] SecurityManager issue using logback
by Andrew Bourgeois 05 Nov '11

05 Nov '11

Ceki, actually, a third option is not to use System.setProperty(...) for java.security.policy, but pass it as a parameter when launching the app (-Djava.security.policy=java.policy). FYI: I only use System.setProperty(...) for small systests that I launch from my IDE. Best regards Andrew Bourgeois -----Original Message----- From: Andrew Bourgeois Sent: Saturday, November 05, 2011 5:28 PM To: logback users list Subject: Re: [logback-user] SecurityManager issue using logback Ceki, you're right, I do get the exception when executing that block of code. I have 2 workarounds for my problem: 1) Put the java.policy file into $JAVA_HOME/jre/lib/security: That's too dirty, I'll skip this one. 2) Initialize the security manager before initializing logback: @Test public void loggingAfterSecurityManager() { System.setProperty("java.security.policy", "./src/test/resources/java.policy"); if (System.getSecurityManager() == null) { System.setSecurityManager(new RMISecurityManager()); } Logger logger = LoggerFactory.getLogger(SecurityManagerTest.class); logger.debug("Policy location: {}", System.getProperty("java.security.policy")); System.setProperty("java.security.policy", "./src/test/resources/java.policy"); } The test passes because I did what I had to do before loading the logback classes. The following doesn't pass: @Test public void loggingBeforeSecurityManager() { Logger logger = LoggerFactory.getLogger(SecurityManagerTest.class); logger.debug("Policy location: {}", System.getProperty("java.security.policy")); System.setProperty("java.security.policy", "./src/test/resources/java.policy"); if (System.getSecurityManager() == null) { System.setSecurityManager(new RMISecurityManager()); } logger.debug("Policy location: {}", System.getProperty("java.security.policy")); } If I dare to initialize logback before initializing a security manager, once I do it, it all goes wrong with code that uses the SecurityManager (so the last logger.debug(...) fails!). I'm not an expert so I can't say it's bad, but it's annoying. Thank you for your help! Best regards Andrew Bourgeois -----Original Message----- From: ceki Sent: Saturday, November 05, 2011 4:25 PM To: logback users list Subject: Re: [logback-user] SecurityManager issue using logback Thanks for the sample project. I can confirm that I observe a AccessControlException when logback is present. The AccessControlException is not thrown if slf4j-nop, slf4j-simple or slf4j-log4j are used as the slf4j binding. Although logback does not install its own SecurityManager or modify the security configuration, it does attempt to determine whether it has "getClassLoader" permission. See http://goo.gl/zASBm Here is the code in question: AccessController.doPrivileged(new PrivilegedAction<Boolean>() { public Boolean run() { try { AccessController.checkPermission( new RuntimePermission("getClassLoader")); return true; } catch (AccessControlException e) { return false; } } }); If the privileged block above code is removed, then the AccessControlException goes away. The privileged block looks quite legitimate to me so I don't think it's a bug in logback. To convince yourself the the privileged block is key, you can remove all logging related calls and all logging related dependencies, add the privileged block at the beginning of the test. You should observe an AccessControlException being thrown. -- Ceki http://twitter.com/#!/ceki On 11/5/2011 1:42 PM, Andrew Bourgeois wrote: > Ceki, > > I redid the test in a clean Maven project. I don't know if attachments > will pass through, so: > > 1) pom.xml: > > <project xmlns="http://maven.apache.org/POM/4.0.0" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 > http://maven.apache.org/maven-v4_0_0.xsd"> > <modelVersion>4.0.0</modelVersion> > <name>test</name> > <groupId>be.test.fun</groupId> > <artifactId>test</artifactId> > <version>0.1.0-RC1</version> > <dependencies> > <dependency> > <groupId>org.slf4j</groupId> > <artifactId>slf4j-api</artifactId> > <version>1.6.0</version> > </dependency> > > <dependency> > <groupId>log4j</groupId> > <artifactId>log4j</artifactId> > <version>1.2.16</version> > </dependency> > <dependency> > <groupId>org.slf4j</groupId> > <artifactId>slf4j-log4j12</artifactId> > <version>1.6.0</version> > </dependency> > >  > > <dependency> > <groupId>junit</groupId> > <artifactId>junit</artifactId> > <version>4.4</version> > <scope>test</scope> > </dependency> > </dependencies> > <build> > <resources> > </resources> > <plugins> > <plugin> > <artifactId>maven-compiler-plugin</artifactId> > <configuration> > <source>1.6</source> > <target>1.6</target> > <verbose>true</verbose> > </configuration> > </plugin> > </plugins> > </build> > </project> > > 2) The JUnit test: > > package be.test.fun; > > import org.junit.Test; > import java.rmi.RMISecurityManager; > import org.slf4j.Logger; > import org.slf4j.LoggerFactory; > > public class SecurityManagerTest { > > @Test > public void securityManagerWithLogs() { > Logger logger = LoggerFactory.getLogger(SecurityManagerTest.class); > > System.setProperty("java.security.policy", > "./src/test/resources/java.policy"); > logger.debug("Policy location: {}", > System.getProperty("java.security.policy")); > if (System.getSecurityManager() == null) { > System.setSecurityManager(new RMISecurityManager()); > } > System.setProperty("java.security.policy", > "./src/test/resources/java.policy"); > } > > // @Test > // public void securityManagerWithoutLogs() { > // System.setProperty("java.security.policy", > "./src/test/resources/java.policy"); > // if (System.getSecurityManager() == null) { > // System.setSecurityManager(new RMISecurityManager()); > // } > // System.setProperty("java.security.policy", > "./src/test/resources/java.policy"); > // } > } > > 3) java.policy that you put into src/test.resources: > > grant { > permission java.security.AllPermission; > }; > > So.... if you run this: > ------------------------------------------------------- > T E S T S > ------------------------------------------------------- > Running be.test.fun.SecurityManagerTest > 2011-11-05 13:36:33,828 [main] DEBUG - (be.test.fun.SecurityManagerTest) > - Policy location: ./src/test/resources/java.policy > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.201 sec > > Results : > > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0 > > Now, comment the 2 LOG4J-related dependencies inside the POM, and > uncomment the logback ones: > ------------------------------------------------------- > T E S T S > ------------------------------------------------------- > Running be.test.fun.SecurityManagerTest > 13:38:04.222 [main] DEBUG be.test.fun.SecurityManagerTest - Policy > location: ./src/test/resources/java.policy > java.security.AccessControlException: access denied > (java.lang.RuntimePermission setContextClassLoader) > at > java.security.AccessControlContext.checkPermission(AccessControlContext.java:323) > > at > java.security.AccessController.checkPermission(AccessController.java:546) > at java.lang.SecurityManager.checkPermission(SecurityManager.java:532) > at java.lang.Thread.setContextClassLoader(Thread.java:1394) > at > org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:366) > > at > org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1021) > > [INFO] > ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] > ------------------------------------------------------------------------ > [INFO] Total time: 2.202s > > And now comment the "securityManagerWithLogs" test method, and uncomment > the "securityManagerWithoutLogs" one: > ------------------------------------------------------- > T E S T S > ------------------------------------------------------- > Running be.test.fun.SecurityManagerTest > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.105 sec > > Results : > > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0 > > Do you have the same output? > > FYI: > > [xvepak@localhost test]$ mvn -version > Apache Maven 3.0.1 (r1038046; 2010-11-23 11:58:32+0100) > Java version: 1.6.0_23 > Java home: /home/xvepak/software/jdk1.6.0_23/jre > Default locale: en_US, platform encoding: UTF-8 > OS name: "linux" version: "2.6.18-238.12.1.el5" arch: "i386" Family: > "unix" > > Thank you for trying to help out!! > > Best regards > > Andrew Bourgeois > > -----Original Message----- From: ceki > Sent: Saturday, November 05, 2011 1:03 AM > To: logback users list > Subject: Re: [logback-user] SecurityManager issue using logback > > On 05/11/2011 12:47 PM, Andrew Bourgeois wrote: > >> So to reformulate: >> The exception IS thrown when we have SLF4J code >> The exception ISN'T thrown when we remove the SLF4J. > > That's not what I observe. An exception is thrown in both cases. _______________________________________________ Logback-user mailing list Logback-user(a)qos.ch http://mailman.qos.ch/mailman/listinfo/logback-user

1 0

scanning property files that are read from configuration file
by Yoel Spotts 04 Nov '11

04 Nov '11

As described in the manual, one can set logback so that the logback config file is scanned for modifications by including the scan attribute on the <configuration> tag. However, if a property file is defined for property substitution with the <property> tag, that property file is NOT scanned for modifications. Is it possible to set up the property file to be scanned for changes? If not, can I make a feature request to add this ability - maybe add a "scan" attribute to the <property> tag which would add the property file to the Config watcher list. Thanks! Yoel Spotts | Senior Software Engineer | nexidia<http://www.nexidia.com/> | O: 404.495.7220 x4007 | [cid:image001.png@01CC9ADD.93791E20] <http://twitter.com/Nexidia> [cid:image002.png@01CC9ADD.93791E20] <http://www.linkedin.com/companies/nexidia> [cid:image003.png@01CC9ADD.93791E20] <http://www.youtube.com/user/NexidiaTV>

2 3