- logback-user - mailman3.qos.ch

problems with TimeBasedRollingPolicy
by Leon Rosenberg 01 Jul '11

01 Jul '11

Hello, I have following logback rolling file appender configuration: <appender name="DWHTextToolActionLogger" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>${user.home}/data/inbound/csi/text_approval/xxx_text_approval.csv</file> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <fileNamePattern>${user.home}/data/inbound/csi/text_approval/xxx_text_approval_%d{yyyy_MM_dd}.csv.gz</fileNamePattern> <maxHistory>100</maxHistory> </rollingPolicy> <encoder> <pattern>%m%n</pattern> </encoder> </appender> <logger name="DWHTextToolActionLogger" additivity="false"> <level value="INFO" /> <appender-ref ref="DWHTextToolActionLogger" /> </logger> I would expect the log file to roll nightly, however, I only see following files: -rw-r--r-- 1 xxx xxx 236K Jun 28 14:08 xxx_text_approval.csv -rw-r--r-- 1 xxx xxx 39K Jun 22 08:21 xxx_text_approval_2011_06_21.csv.gz -rw-r--r-- 1 xxx xxx 32K Jun 23 08:18 xxx_text_approval_2011_06_22.csv.gz -rw-r--r-- 1 xxx xxx 35K Jun 24 07:52 xxx_text_approval_2011_06_23.csv.gz -rw-r--r-- 1 xxx xxx 26K Jun 25 07:43 xxx_text_approval_2011_06_24.csv.gz -rw-r--r-- 1 xxx xxx 41K Jun 26 07:50 xxx_text_approval_2011_06_25.csv.gz -rw-r--r-- 1 xxx xxx 28K Jun 27 07:44 xxx_text_approval_2011_06_26.csv.gz -rw-r--r-- 1 xxx xxx 57K Jun 28 08:12 xxx_text_approval_2011_06_27.csv.gz Is it misconfigured, or does the rolling actually happens at the first log message in the morning? If it's action based, how can i configure rolling to be triggered @midnight no matter how empty or full the log is? regards Leon p.s. version: <groupId>ch.qos.logback</groupId> <artifactId>logback-classic</artifactId> <version>0.9.28</version>

4 9

DBAppender database viewer / GUI
by Christian Migowski 30 Jun '11

30 Jun '11

Greetings, does anyone know if there is a viewer / GUI application (could also be web based) for examing the entries that the logback-classic DBAppender writes to the database? I know the requirements for such a tool could vary quite a lot, but I was thinking maybe something simple which is able to display related contents of the three tables together exists already. thanks in advance & best regards, christian

1 0

How to get the pattern of an appender of logback.xml
by Noah Rebmann 24 Jun '11

24 Jun '11

Hello, It seems to be possible to read the pattern of an appender out of the logback.xml-file. But I don't know how exactly. We use the followin Code to get the the filepath form the appender (found somwhere in this mailinglist): String path = ""; LoggerContext ctx = (LoggerContext)LoggerFactory.getILoggerFactory(); for (Logger l : ctx.getLoggerList()) { ch.qos.logback.classic.Logger log =(ch.qos.logback.classic.Logger) l; Iterator<Appender<ILoggingEvent>> it = log.iteratorForAppenders(); while (it.hasNext()) { Appender<ILoggingEvent> ap = it.next(); if (ap instanceof FileAppender<?> || ap instanceof RollingFileAppender<?>) { FileAppender<?> fileAppender = (FileAppender<?>)ap; path = fileAppender.getFile(); } } } return path; } Is it possible to implement a method which also gets the pattern of the appender out of the file? I tried different ways but somehow I don't get it. Thanks in advance! Regards, Noah

1 0

RollingFileAppender for logs with headers
by Chris Dolan 15 Jun '11

15 Jun '11

I use an XML-based Layout for one of my appenders. This Layout makes use of the getFileHeader() to output "<?xml...?>" and getPresentationHeader/Footer() methods to output "<log><header>...</header>" and "</log>. I want a daily rolling log that additionally rolls at a specific file size. So: <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">  <fileNamePattern>${log.out.dir}/Foo-${log.host}-%d{yyyy-MM-dd}.%i.xml.zip</fileNamePattern> <maxHistory>365</maxHistory> <timeBasedFileNamingAndTriggeringPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP">  <maxFileSize>5MB</maxFileSize> </timeBasedFileNamingAndTriggeringPolicy> </rollingPolicy> The problem with this configuration is that on application reboot, I get log files like this: <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <log xmlns="[snip]"> <header> <tz>America/Chicago</tz> <tzoffset>-21600000</tzoffset> </header> <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <log xmlns="[snip]"> <header> <tz>America/Chicago</tz> <tzoffset>-21600000</tzoffset> </header> That is, the new run emits another header appended into the existing log file. I've tried to work around it by making a subclassed appender that looks like the following, but it fails with a NullPointerException because the rolling filename hasn't been set up yet... public class RollingXmlFileAppender<E> extends RollingFileAppender<E> { @Override public void openFile(String fileName) throws IOException { File file = new File(fileName); if (file.exists()) { try { getRollingPolicy().rollover(); } catch (RolloverFailure rolloverFailure) { // ... } } super.openFile(fileName); } } Surely other people use log files with headers? How do you roll those files? It would seem that the trigger should always be checked on start(). If so, I could probably make a TriggeringPolicy that always returns true on its first invocation. Chris

1 0

Bug in include tag
by Amit A Gadkari 15 Jun '11

15 Jun '11

We are having ear project with multiple web modules and ejb module. Logback is in shared library (websphere shared library which is loaded by different class loader) We have logback configuration files for each module. We have but all common appenders, logger in common included file which is in Java shared project which is used by all web modules and ejb modules in ear project. This included file we are including in logback configuration file for each module. Now logback is not able to find this included file. Reason: Logback.xml file of each module is loaded by classloader of web module While loading include file instead of using classloader of web module, it uses classloader of shared library. (Logback internally uses class loader of Loader.class) <include resource="common-configuration.xml" /> I think that this is bug as classloader which loaded logback.xml file of each module, should be used for loading included file also. Is there any workaround for this issue? -- View this message in context: http://old.nabble.com/Bug-in-include-tag-tp31840099p31840099.html Sent from the Logback User mailing list archive at Nabble.com.

2 2

Tomcat and webapp logging to same file with rollingFileAppender
by Roy McMorran 14 Jun '11

14 Jun '11

Greetings, We're currently using Logback for Tomcat logging via the method described at : https://github.com/grgrzybek/tomcat-slf4j-logback#readme There are two separate logback.xml files, one for Tomcat logging at $CATALINA_HOME/conf and another in the application WEB-INF/classes directory. Both use rollingFileAppender with TimeBasedRollingPolicy to roll over nightly. Both appenders write to the same file - $CATALINA_HOME/logs/tomcat.log . The contents of the logback.xml files can be viewed at http://pastebin.com/UHzy4AZe and http://pastebin.com/pEQAga4r This seems to work well until it is time for the log to roll over. After midnight the tomcat.log file is renamed to tomcat.yyyy-MM-dd.log as expected. Tomcat begins logging to a new tomcat.log file, as expected. However, the application is now logging to the tomcat.yyyy-MM-dd.log , which is not what we want. The lsof command tells me that the Tomcat process (jsvc) still has both files open. Can anyone suggest where we may have went wrong in the configuration? Thanks! PS: Tomcat 6.0.29, logback 0.9.26 -- Roy McMorran Systems Administrator MDI Biological Laboratory mcmorran(a)mdibl.org

1 0

What controls API version?
by Christopher Paulicka 13 Jun '11

13 Jun '11

Hello, Is there a way to control the logback version? If I create the following Gradle script: apply plugin: 'java' apply plugin: 'maven' repositories { mavenCentral() } dependencies { compile group: 'ch.qos.logback', name: 'logback-classic', version: '0.9.28' compile group: 'org.slf4j', name: 'slf4j-api', version: '1.5.8' } Then run 'gradle dependencies', my 'slf4j-api' version is now '1.6.1'. How does this happen? And how can I keep it at '1.5.8'? Strayph P.S. I found (by iterating) that '0.9.17' stays with '1.5.8', but that is a cheesy hack.

2 1

Java 7 automatic resource management and suppressed exceptions
by Christopher BROWN 13 Jun '11

13 Jun '11

Hello, I just read this article: http://www.oracle.com/technetwork/articles/java/trywithresources-401775.html I was aware of auto-close in Java 7, but have just seen (here) an example of "suppressed exceptions", which appear in stacktraces. Will this have an impact/be supported with logback? For reference, this example: MyException: Exception in work() at AutoClose.work(AutoClose.java:11) at AutoClose.runWithoutMasking(AutoClose.java:27) at AutoClose.main(AutoClose.java:58) Suppressed: java.lang.RuntimeException: Exception in close() at AutoClose.close(AutoClose.java:6) at AutoClose.runWithoutMasking(AutoClose.java:34) ... 1 more Thanks, Christopher

2 4

How to direct calls to another API into Logback classic
by Christopher BROWN 10 Jun '11

10 Jun '11

Hello, I'm using Logback classic via the SLF4J API, in a big application where other log APIs (some standard, such as OSGI logging, and other proprietary in-house historical APIs) are present. I would like to re-implement these APIs to "redirect" onto Logback classic, but to get to the point: it's a big API and I'm lost. If I reimplement said APIs with a naive implementation that just calls into SLF4J or logback using the "user" API, I'll incur an extra stack frame in stack traces and generally hide the origin of calls. What's the best, cleanest way of doing this (given SLF4J and the choice of logback classic) ? I will add the Log4J API implementation to address some cases (the SLF4J implementation of Log4J APIs) but for the other stuff, I'm a bit stuck. Thanks, Christopher

2 2

Release of logback v0.9.29
by Ceki Gülcü 10 Jun '11

10 Jun '11

Hello all, I am happy to announce the release of logback version 0.9.29. Please refer to the news page for precise details. http://logback.qos.ch/news.html You can download logback, including full source code, class files and documentation on our download page, shown below. http://logback.qos.ch/download.html You can receive logback related announcements by subscribing to the QOS.ch announce mailing list. To subscribe to QOS.ch announce list, please visit the following URL. http://www.qos.ch/mailman/listinfo/announce Enjoy, -- Ceki

2 1