- logback-user - mailman3.qos.ch

Re: [logback-user] Delete log file
by pwillems66＠zonnet.nl 18 Nov '10

18 Nov '10

Hi, The prudent propertie doesn't work. Any other idea? It looks like the log file is in use. Is their a way to 'unlock' that use by code? This is what I must realize: For every test I need to create a log file. When the same test start again the previous file must be deleted (or renamed and delete thereafter) and a new one created. Also (test is not running) it must be possible to delete the log file. -Patrick pwillems66 at zonnet.nl wrote: > Maybe someone else have a (different) solution? FileAppender.setPrudent() looks promising for this purpose. However, using the example from PrudentTimeBasedRolling.xml, when I rm the file it is not recreated on the next log statement. Also, if it did work, it doesn't support your file appender, but maybe it is ok to change that. http://logback.qos.ch/codes.html#tbr_fnp_prudent_unsupported says, > prudent mode is not allowed in conjuction with a FixedWindowRollingPolicy. -Gordon

2 1

Delete log file
by pwillems66＠zonnet.nl 17 Nov '10

17 Nov '10

We think about it but I doubt it. Maybe someone else have a (different) solution? > With append=false, log a start message (e.g. "Starting"), which >will > then overwrite the file. Is that good enough for the needs? > On Tue, Nov 16, 2010 at 10:47 AM, <pwillems66 at zonnet.nl> >wrote: >> Hi, >> >> For every test we do, we need a log file. >> If the test fails, the log file can be viewed and the errors can be fixed. >> If the errors are fixed and the test runs again and there are no errors, I >> want to delete this log file. >> Is it possible to delete a log file? (While file is is use by logback!) >> If yes, how? >> >> My configuration is: >> <?xml version="1.0" encoding="UTF-8" ?> >> <configuration> >> >> <appender name="RootSiftAppender" >> class="ch.qos.logback.classic.sift.SiftingAppender"> >> <append>false</append> <discriminator> >> <Key>testname</Key> >> <DefaultValue>testrun</DefaultValue> >> </discriminator> >> <sift> >> <appender name="FILE-${testname}" >> class="ch.qos.logback.core.rolling.RollingFileAppender"> >> <File>${testname}.log</File> >> <rollingPolicy >> class="ch.qos.logback.core.rolling.FixedWindowRollingPolicy"> >> <FileNamePattern>${testname}.%i.log</FileNamePattern> >> <MinIndex>1</MinIndex> >> <MaxIndex>1</MaxIndex> >> </rollingPolicy> >> <triggeringPolicy >> class="ch.qos.logback.core.rolling.SizeBasedTriggeringPolicy"> >> <MaxFileSize>5MB</MaxFileSize> >> </triggeringPolicy> >> <layout class="ch.qos.logback.classic.PatternLayout"> >> <Pattern>%d{ISO8601} - %msg%n</Pattern> >> </layout> >> </appender> >> </sift> >> </appender> >> <root level="error"> >> <appender-ref ref="RootSiftAppender" /> >> </root> >> </configuration> >> >> _______________________________________________ >> Logback-user mailing list >> Logback-user at qos.ch >> http://qos.ch/mailman/listinfo/logback-user >> >>

2 1

Delete log file
by pwillems66＠zonnet.nl 17 Nov '10

17 Nov '10

Hi, For every test we do, we need a log file. If the test fails, the log file can be viewed and the errors can be fixed. If the errors are fixed and the test runs again and there are no errors, I want to delete this log file. Is it possible to delete a log file? (While file is is use by logback!) If yes, how? My configuration is: <?xml version="1.0" encoding="UTF-8" ?> <configuration> <appender name="RootSiftAppender" class="ch.qos.logback.classic.sift.SiftingAppender"> <append>false</append> <discriminator> <Key>testname</Key> <DefaultValue>testrun</DefaultValue> </discriminator> <sift> <appender name="FILE-${testname}" class="ch.qos.logback.core.rolling.RollingFileAppender"> <File>${testname}.log</File> <rollingPolicy class="ch.qos.logback.core.rolling.FixedWindowRollingPolicy"> <FileNamePattern>${testname}.%i.log</FileNamePattern> <MinIndex>1</MinIndex> <MaxIndex>1</MaxIndex> </rollingPolicy> <triggeringPolicy class="ch.qos.logback.core.rolling.SizeBasedTriggeringPolicy"> <MaxFileSize>5MB</MaxFileSize> </triggeringPolicy> <layout class="ch.qos.logback.classic.PatternLayout"> <Pattern>%d{ISO8601} - %msg%n</Pattern> </layout> </appender> </sift> </appender> <root level="error"> <appender-ref ref="RootSiftAppender" /> </root> </configuration>

2 1

Unable to see ch.qos.logback.classic.jmx.Configurator folder within JConsole?
by Joshua White 15 Nov '10

15 Nov '10

Hello, I am attempting to configure logback to use JMX. I have used the "<jmxConfigurator />" within my xml file and I see the following in the log: 09:02:16,991 |-INFO in ch.qos.logback.classic.LoggerContext[mycompany-portal] - Could NOT find resource [logback-test.xml] 09:02:17,022 |-INFO in ch.qos.logback.classic.LoggerContext[mycompany-portal] - Found resource [logback.xml] at [file:/C:/source/mycompany/mycompany-core-jar/bin/logback.xml] 09:02:17,179 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - Setting ReconfigureOnChangeFilter scanning period to 15 minutes 09:02:17,179 |-INFO in ch.qos.logback.classic.turbo.ReconfigureOnChangeFilter@18661866 - Will scan for changes in file [C:\source\mycompany\mycompany-core-jar\bin\logback.xml] every 900 seconds. 09:02:17,179 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - Adding ReconfigureOnChangeFilter as a turbo filter 09:02:17,179 |-INFO in ch.qos.logback.classic.joran.action.ContextNameAction - Setting logger context name as [mycompany-portal] *09:02:17,179 |-INFO in ch.qos.logback.classic.joran.action.JMXConfiguratorAction - begin* 09:02:17,647 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.FileAppender] 09:02:17,647 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [FILE] 09:02:17,679 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property 09:02:17,679 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Pushing component [encoder] on top of the object stack. 09:02:17,757 |-INFO in ch.qos.logback.core.FileAppender[FILE] - File property is set to [c:/temp/oep/mycompany-portal.log] 09:02:17,757 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [com.mycompany] to DEBUG 09:02:17,757 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting additivity of logger [com.mycompany] to true 09:02:17,757 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [org.springframework] to INFO 09:02:17,757 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting additivity of logger [org.springframework] to true 09:02:17,757 |-INFO in ch.qos.logback.classic.joran.action.RootLoggerAction - Setting level of ROOT logger to INFO 09:02:17,757 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [FILE] to Logger[ROOT] 09:02:17,757 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - End of configuration. When I start JConsole (IBM's version...) I only see two folders. I would expect to see a folder for "ch.qos.logback.classic.jmx.Configurator". Here is what I see: Shouldn't the logback folder be in root with these two folders? JMImplementation WebSphere Here is what I am using: Logback 0.9.24 Websphere 6.1 Any thoughts or recommendations?

2 2

Lilith 0.9.40 has been released! (supporting log4j & jul, too!)
by Joern Huxhorn 11 Nov '10

11 Nov '10

http://lilith.huxhorn.de Release Notes - Color-Schemes (as used by saved conditions, for example) can now be defined partially, i.e. one condition can set a border while the text-color might be defined by a different condition. - Maps, e.g. MDC, are now sorted by key-value in the details view. This was suggested by Joe. - Added preferences to check for pre-release versions in addition to release versions. Off by default. - Added -T/--print-timestamp command line argument that prints the timestamp and date of build. - If the used version is a SNAPSHOT, Lilith will always check for a new SNAPSHOT pre-release regardless of the "Check for updates on startup." settings. - Enhanced "Check for update" functionality. No more false update warnings in case of SNAPSHOT pre-releases. A new release takes precedence over a new pre-release. - SNAPSHOT pre-releases will now contain the date and time of the build in the window title. - Added support for java.util.logging SocketHandler. Lilith is listening on port 11020 for incoming connections. I'd still recommend to switch to SLF4J/Logback, though! (Ticket 35) - Added JSON-Appenders and JSON-Receivers. Lilith is listening for message-based JSON-Events on port 10030 (uncompressed) and 10031 (compressed). Zero-delimited JSON-Events are consumed on port 11010. Check out the expected JSON data at http://sourceforge.net/apps/trac/lilith/wiki/LilithJsonFormat - Replaced Commons-CLI with JCommander. Very nice replacement. I'd like to take this opportunity to thank Cedric Beust for his great (and fast!) support! You should seriously check JCommander out if your application is handling command line arguments at all. - Added support for Log4j SocketAppender. Lilith is listening on port 4445 for incoming connections. I'd still recommend to switch to SLF4J/Logback, though! (Ticket 32) - Fixed glitch in case of "Find next"/"Find prev" while search is already running. Additional searches are now ignored. - Added "Find previous active" (*command* T) and "Find next active" (*command* shift T) functionality to quickly jump to events that match any active condition. (Ticket 93) - Added "Export" functionality which exports the currently selected view into a Lilith file. (Ticket 92) - Added default condition name to preferences. It's preselected for every new view. This was suggested by Lothar Cezanne. - Polling events every 100ms instead of every 2s. This results in less congestion and a much snappier feeling. - Added --export-preferences <file> and --import-preferences <file> commandline options to be able to export and import all preferences. This was requested by Gareth Doutch (gdoutch). (Ticket 81) - Added an additional executable lilith-all.jar containing all dependencies as another download option. This was requested by Adrien Sales. - Added ability to define a sound for WARN-level events, but without any assigned default sound. This was requested by Adrien Sales. - Added F1 as shortcut for Help. This was requested by Adrien Sales. - Fixed several issues in case of log files that are recreated by <append>false<append> in FileAppender. Those were all raised by Jeff Jensen (jeffjensen). Thank you very much! (Ticket 84, 88, 90) - Fixed the regression that the internal Lilith log wouldn't show up in the menu anymore. (Ticket #85) - Changed update interval of opened files from 5 seconds to 1 second. - Spring 3.0.5.RELEASE - Groovy 1.7.5 - SLF4J 1.6.1 - Logback 0.9.26 Known Issues - Selection in the HTML view is currently somewhat buggy, especially in case of scaled view. This is a limitation of Flying Saucer that's used as the XHTML renderer. - cat and tail are currently still experimental features. AccessEvent isn't (and can't be) supported yet. LoggingEvent isn't fully supported, either. And finally: Sulky and Lilith builds have been switched from Maven to Gradle. pom files are still maintained but mainly because of Sonar. I'd like to take this opportunity and thank the great Gradle community from the #gradle channel on irc.codehaus.org, especially - but not exclusively! - adam (Adam Murdoch), xlson (Leonard Axelsson) and sebersole (Steve Ebersole). Thank you very much! If you haven't taken a look at Gradle yet you should definitely do so now or in the near future... Cheers, Joern.

1 0

How to reference file one level above the web context
by Dawson Mossman 09 Nov '10

09 Nov '10

I am trying to use the <property file="logback.properties" /> tag in my logback.xml file to reference an external settings file. I want to use a relative path and specify the file one level above my application context. For example: <web server root>/apps/myapplication/web-inf/classes/logback.xml I want to put the logback.properties file at <web server root>/apps/. Do you know what relative path I need to use to do this? I've tried everything I can think of, including the following, but they did not work: <property file="../logback.properties" /> <property file="../../../logback.properties" /> <property file="/logback.properties" /> <property file="./logback.properties" /> Please help ... there has to be a way without using an absolute path! Dawson

3 6

JaninoEventEvaluator Expression
by Roberts, David 08 Nov '10

08 Nov '10

Is it possible to have an expression with multiple criteria? For example: <filter class="ch.qos.logback.core.filter.EvaluatorFilter"> <evaluator class="ch.qos.logback.classic.boolex.JaninoEventEvaluator"> <expression>(logger.equals("mylogger") && message.contains("my message"))</expression> </evaluator> <OnMismatch>NEUTRAL</OnMismatch> <OnMatch>DENY</OnMatch> </filter> I have tried encoding the && and using CDATA but logback still doesn't accept it or perform correctly. Dave

2 3

Query re. LOGBack, Spring & SLF4J
by Seamus Hannan 08 Nov '10

08 Nov '10

Hi, I have a question concerning getting LOGBack working with Spring using Maven. According to the Spring Documentation Spring needs to be forced to work iwth SLF4J. (sample code below) My question is how do I get LOGBack to work with this configuration (instead of log4j)? The Spring documentation indicates that you need to use jcl-over-slf4j, but it is not clear how to configure LOGBack to work with Spring and SLF4J. My code, including the example code below builds for me intermiitently from the command line, indicating that there is some classloading issue. Any advice will be much appreciated. Thanks. Seamus Hannan <dependencies> <dependency> <groupId>org.springframework</groupId> <artifactId>spring-context</artifactId> <version>3.0.0.RELEASE</version> <scope>runtime</scope> <exclusions> <exclusion> <groupId>commons-logging</groupId> <artifactId>commons-logging</artifactId> </exclusion> </exclusions> </dependency> </dependencies> <dependencies> <dependency> <groupId>org.springframework</groupId> <artifactId>spring-context</artifactId> <version>3.0.0.RELEASE</version> <scope>runtime</scope> <exclusions> <exclusion> <groupId>commons-logging</groupId> <artifactId>commons-logging</artifactId> </exclusion> </exclusions> </dependency>  <dependency> <groupId>ch.qos.logback</groupId> <artifactId>logback-classic</artifactId> <version>0.9.26</version> </dependency> <dependency> <groupId>org.slf4j</groupId> <artifactId>jcl-over-slf4j</artifactId> <version>1.5.8</version> <scope>runtime</scope> </dependency> <dependency> <groupId>org.slf4j</groupId> <artifactId>slf4j-api</artifactId> <version>1.5.8</version> <scope>runtime</scope> </dependency> <dependency> <groupId>org.slf4j</groupId> <artifactId>slf4j-log4j12</artifactId> <version>1.5.8</version> <scope>runtime</scope> </dependency> <dependency> <groupId>log4j</groupId> <artifactId>log4j</artifactId> <version>1.2.14</version> <scope>runtime</scope> </dependency> </dependencies>

2 2

Backlog, SLF4J and jars using other logging frameworks
by Ali Salehi 07 Nov '10

07 Nov '10

Hi all, I have a dependency to a jar file which is using java.util.logging. My code uses Logback/slf4j framework. As I understood, slf4j will proxy other logging frameworks. I created the error using the following code: logger = org.slf4j.LoggerFactory.getLogger("test1"); jdkLogger = java.util.logging.Logger.getLogger("test2"); logger.debug("Backlog logs ...") jdkLogger.info("JDK Logs ...") and my backlog.xml <?xml version="1.0" encoding="UTF-8"?> <configuration scan="false" debug="false" > <appender name="stdout" class="ch.qos.logback.core.ConsoleAppender"> <encoder> <pattern>[%4p] [%d{ISO8601}] [%t] %c{1}: %m%n</pattern> </encoder> </appender> <root level="WARN"> <appender-ref ref="stdout"/> </root> </configuration> When I execute the code, I see a log output from test2 while test1 gets filtered by backlog. I was expecting that both messages to get filtered by SLF4J/Backlog. I have slf4j-api-1.6.1.jar, logback-classic-0.9.24.jar and logback-core-0.9.24.jar files in my classpath. I appreciate your comments, -A

5 6

Groovy configuration of SizeAndTimeBasedFNATP
by Jeff Skjonsby 05 Nov '10

05 Nov '10

I have been trying to convert our logging configuration to the groovy based configuration and have run into an issue with setting the SizeAndTimeBasedFNATP up. I used the converter tool to convert our configuration and have also tried the examples in the documentation: import ch.qos.logback.classic.encoder.PatternLayoutEncoder import ch.qos.logback.core.rolling.RollingFileAppender import ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP import ch.qos.logback.core.rolling.TimeBasedRollingPolicy import static ch.qos.logback.classic.Level.DEBUG appender("ROLLING", RollingFileAppender) { file = "mylog.txt" rollingPolicy(TimeBasedRollingPolicy) { fileNamePattern = "mylog-%d{yyyy-MM-dd}.%i.txt" timeBasedFileNamingAndTriggeringPolicy(SizeAndTimeBasedFNATP) { maxFileSize = "100MB" } } encoder(PatternLayoutEncoder) { pattern = "%msg%n" } } root(DEBUG, ["ROLLING"]) Everything I've tried has resulted in this exception: java.lang.NullPointerException at ch.qos.logback.core.rolling.TimeBasedFileNamingAndTriggeringPolicyBase.start(TimeBasedFileNamingAndTriggeringPolicyBase.java:46) at ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP.start(SizeAndTimeBasedFNATP.java:36) ... If I step through the configuration process it appears that on line 46 in TimeBasedFileNamingAndTriggeringPolicyBase the tbrp member variable is null here. Any ideas?

2 2