June 2014 - logback-user - mailman3.qos.ch

How to get rollingfileappender to roll over based on log size
by Jeremy Kane 28 Jul '14

28 Jul '14

I've been trying to get the rollinglogfileappender to roll-over at a certain file size, but I've had no luck. I can get it to roll over at midnight each night, but I still would prefer to either combine them or have it just be file-size limited. My config is such: // Rolling Log Appender String fileDirectory = KanetikApplication.getFileDirectory(context); RollingFileAppender<ILoggingEvent> rollingFileAppender = new RollingFileAppender<ILoggingEvent>(); rollingFileAppender.setContext(loggerContext); rollingFileAppender.setAppend(true); rollingFileAppender.setFile(fileDirectory + "/log.txt"); TimeBasedRollingPolicy<ILoggingEvent> rollingPolicy = new TimeBasedRollingPolicy<ILoggingEvent>(); rollingPolicy.setMaxHistory(2); rollingPolicy.setFileNamePattern(fileDirectory + "/log.%d.txt"); rollingPolicy.setParent(rollingFileAppender); rollingPolicy.setContext(loggerContext); rollingPolicy.start(); rollingFileAppender.setRollingPolicy(rollingPolicy); PatternLayoutEncoder fileEncoder = new PatternLayoutEncoder(); fileEncoder.setContext(loggerContext); fileEncoder.setPattern("%d{h:mm:ss} %level - %msg%n"); fileEncoder.start(); rollingFileAppender.setEncoder(fileEncoder); rollingFileAppender.start(); // LogCat Appender PatternLayoutEncoder logcatEncoder = new PatternLayoutEncoder(); logcatEncoder.setContext(loggerContext); logcatEncoder.setPattern("%msg%n"); logcatEncoder.start(); PatternLayoutEncoder tagEncode = new PatternLayoutEncoder(); tagEncode.setContext(loggerContext); tagEncode.setPattern(tag); tagEncode.start(); LogcatAppender logcatAppender = new LogcatAppender(); logcatAppender.setContext(loggerContext); logcatAppender.setEncoder(logcatEncoder); logcatAppender.setTagEncoder(tagEncode); logcatAppender.start(); // add the newly created appenders to the root logger; // qualify Logger to disambiguate from org.slf4j.Logger ch.qos.logback.classic.Logger root = (ch.qos.logback.classic.Logger) LoggerFactory.getLogger(Logger.ROOT_LOGGER_NAME); root.setLevel(level); root.addAppender(rollingFileAppender); root.addAppender(logcatAppender); Can anyone tell me why it's not working? Thanks! J

3 3

Logback contrib and json/jackson layout
by Ricardo Borillo 08 Jul '14

08 Jul '14

Hi all, I'm trying to use logback-contrib JSON layout: https://github.com/qos-ch/logback-contrib The problem is that seems to be defined for logback-core 1.0.9 and we are using 1.1.1 currently in our application. Is there any possibility to upgrade? Do you guys want me to issue a pull request? --- Salut, ==================================== Ricardo Borillo Domenech ~ @borillo http://xml-utils.com

2 1

Stopping LoggerContext while using AsyncAppender
by Paresh 27 Jun '14

27 Jun '14

I am trying to use AsyncAppender in a standalone application which currently uses RollingFileAppender. AsyncAppender documentation mentions that , Upon application shutdown or redeploy, AsyncAppender must be stopped in order to stop and reclaim the worker thread and to flush the logging events from the queue. This can be achieved by stopping the LoggerContext which will close all appenders, including any AsyncAppender instances. At the time of stoping the application, we use 'kill' command. Had it been a web application, i could have written code to stop the LoggerContext from within contextDestroyed() of ServletContextListener. So,i would like to know, 1. Is it necessary to stop the LoggerContext while using AsyncAppender. 2. Wont stopping the application, stop the worker thread and flush logging events in queue 3. Any other way it can be performed.

2 1

Web View of Log Entries
by Chris DaMour 20 Jun '14

20 Jun '14

Anyone ever come across a library that would work something like a servlet i can drop into my web app that exposes a /logging or some like path to view the last N log messages? Open to ideas..but NOT looking to send my logs to a third party service (ala splunk)

2 1

logback-access and %I for thread name
by Wolfey 20 Jun '14

20 Jun '14

Hi, I would like to migrate from org.apache.catalina.valves.AccessLogValve with pattern %h %l %u %t '%r' %s %b %I %D to ch.qos.logback.access.tomcat.LogbackValve. I couldn't find support for %I for logging the thread name in logback-access. Am I missing something or is this not possible? Regards, Wolfey

2 2

How to format (mask certain strings) when using SyslogAppender
by Kumar Pandey 19 Jun '14

19 Jun '14

All I extend ch.qos.logback.classic.PatternLayout and override doLayout() to mask certain things like credit card number using reg-ex. This works great with FileAppender and ConsoleAppender. However while configuring SyslogAppender I found out that we can only use suffixPattern to format the content and PatternLayout cannot be specified. Here is the explanation on Logback site -- Given that the format of a syslog request follows strict rules, you cannot freely specify the layout to be used with SyslogAppender. However, you can use SuffixPattern option instead to influence the contents of the message sent to the syslog daemon. So what are my options to change the string content before its sent to SyslogAppender ? I'm on logback version 1.0.3 . Thanks Kumar

1 0

IllegalStateException caused by logback 1.1.2
by Gena Makhomed 19 Jun '14

19 Jun '14

Hello, All! to prevent "AsynAppender thread leak" as described in http://jira.qos.ch/browse/LOGBACK-867 I use recommended in documentation http://logback.qos.ch/manual/appenders.html#AsyncAppender approach: public class LogbackShutdownHook implements ServletContextListener { // ... @Override public void contextDestroyed(ServletContextEvent sce) { logger.info("******* stop logger *******"); LoggerContext loggerContext = (LoggerContext) LoggerFactory.getILoggerFactory(); loggerContext.stop(); } } web.xml: <listener> <listener-class>com.pb.ivrcgate.util.servlet.LogbackShutdownHook</listener-class> </listener> but this causes IllegalStateException in tomcat log: May 28, 2014 3:36:36 PM org.apache.catalina.loader.WebappClassLoader loadClass INFO: Illegal access: this web application instance has been stopped already. Could not load ch.qos.logback.core.status.WarnStatus. The eventual following java.lang.IllegalStateException at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1612) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1571) at ch.qos.logback.classic.LoggerContext.noAppenderDefinedWarning(LoggerContext.java:175) at ch.qos.logback.classic.Logger.callAppenders(Logger.java:267) at ch.qos.logback.classic.Logger.buildLoggingEventAndAppend(Logger.java:442) at ch.qos.logback.classic.Logger.filterAndLog_0_Or3Plus(Logger.java:396) at ch.qos.logback.classic.Logger.log(Logger.java:788) at org.apache.commons.logging.impl.SLF4JLocationAwareLog.debug(SLF4JLocationAwareLog.java:133) at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.shutdown(PoolingHttpClientConnectionManager.java:345) at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.finalize(PoolingHttpClientConnectionManager.java:168) at java.lang.ref.Finalizer.invokeFinalizeMethod(Native Method) at java.lang.ref.Finalizer.runFinalizer(Finalizer.java:101) at java.lang.ref.Finalizer.access$100(Finalizer.java:32) at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:190) in my webapp org.apache.httpcomponents:httpclient:4.3.3 used. sourse PoolingHttpClientConnectionManager.java line #345 is: this.log.debug("Connection manager is shutting down"); ============================================================== how to prevent IllegalStateException in tomcat log? I am doing something wrong, or this is bug in logback code? 1) may be method shutdown() should be added to logback, and after shutdown - all events and messages should be silently ignored? 2) or better add to logback new "fallback mode" - in this mode all async appenders should be stopped and all buffers disabled, all events written to logs and flushed immediately, without delays. "fallback mode" can be used in contextDestroyed() methods or in low memory conditions, before near OutOfMemoryError to prevent any logging events lost in buffers and queues. 3) ................................... something else? -- Best regards, Gena

2 1

Unable to use ASyncAppender
by Hemana Gouda 19 Jun '14

19 Jun '14

Hi, In logback.xml, I am trying to use "AsyncAppender" as below. But I see empty system.log file. When I directly use "RollingFileAppender" I see log entries in system.log file. ------------- <appender name="ASYNC" class="ch.qos.logback.classic.AsyncAppender" queueSize="512"> <discardingThreshold>0</discardingThreshold> <appender-ref ref="LOGFILE" /> </appender> <appender name="LOGFILE" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>${data.dir:-..}/logs/system.log</file> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">  <fileNamePattern>${data.dir:-..}/logs/system-%d{yyyy-MM-dd}.%i.log.gz</fileNamePattern>  <maxHistory>10</maxHistory> <timeBasedFileNamingAndTriggeringPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP">  <maxFileSize>50MB</maxFileSize> </timeBasedFileNamingAndTriggeringPolicy> </rollingPolicy> <encoder> <pattern>%d org:%X{orgName} env:%X{envName} %thread %-5level %logger{25} - %C{0}.%M : %msg%n</pattern> </encoder> </appender> <root level="${log.level:-DEBUG}"> <appender-ref ref="ASYNC"/>  </root> ------------------------------------ Why is ASyncAppender not flushing log evenst to log file used by RollingFileAppender? I am using "logback v 1.1.2". Thanks, Hemana -- Thanks, Hemana +918147706075 skype: hemana.gouda

2 2

Re: [logback-user] Logback suddenly stopped logging
by Andreas Dejung 19 Jun '14

19 Jun '14

I had the same problem and I think I know why J Solaris does interrupt IO blocked thread which then causes the OutputStreamAppender to catch the IOException in line 218 (version 0.9.24). I actually run version 0.9.18 but this part has not change so I guess it will behave the same way. If we look at http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4385444 InterruptedIOException should not be required by platform specification (sol) And log4j https://issues.apache.org/bugzilla/show_bug.cgi?id=44157 InterruptedIOException ignored by log4j I think it should be solved the same why } catch (InterruptedIOException iioe){ //give the thread a changes to act on interruption and then carry on Thread.currentThread().interrupt(); } catch (IOException ioe) { // as soon as an exception occurs, move to non-started state // and add a single ErrorStatus to the SM. this.started = false; addStatus(new ErrorStatus("IO failure in appender", this, ioe)); } I could not find the jira entry mentioned in this thread therefore I write it here J BTY the jvm option -XX:-UseVMInterruptibleIO does prevent the interruption by solaris but that's only a workaround and not solving the problem ;) Cheers Andy

8 16

logback skipping log files on AWS EC2
by Bob Sandiford 19 Jun '14

19 Jun '14

I'm using logback for logging from an app deployed in Tomcat, with a fairly simple setup (see code fragments). We use a RollingFileAppender, with TimeBasedRollingPolicy, set for daily rollover. When running locally, everything appears to be fine. When running in AWS in an EC2 instance, I'm seeing that some log files are missing. I wrote a really simple app that does nothing but log once per second with a counter, and then a logback config that rolls every minute. For this particular test, we're seeing every third log file is missing. So, for example, we'll get: -rw-r--r-- 1 tomcat tomcat 891 May 13 18:46 logtest_tomcat.2014-05-13_1845.0.log.gz -rw-r--r-- 1 tomcat tomcat 499 May 13 18:47 logtest_tomcat.2014-05-13_1846.0.log.gz -rw-r--r-- 1 tomcat tomcat 541 May 13 18:49 logtest_tomcat.2014-05-13_1848.0.log.gz -rw-r--r-- 1 tomcat tomcat 519 May 13 18:50 logtest_tomcat.2014-05-13_1849.0.log.gz -rw-r--r-- 1 tomcat tomcat 532 May 13 18:52 logtest_tomcat.2014-05-13_1851.0.log.gz -rw-r--r-- 1 tomcat tomcat 510 May 13 18:53 logtest_tomcat.2014-05-13_1852.0.log.gz -rw-r--r-- 1 tomcat tomcat 536 May 13 18:55 logtest_tomcat.2014-05-13_1854.0.log.gz -rw-r--r-- 1 tomcat tomcat 1226 May 13 18:56 logtest_tomcat.2014-05-13_1855.0.log.gz -rw-r--r-- 1 tomcat tomcat 531 May 13 18:58 logtest_tomcat.2014-05-13_1857.0.log.gz -rw-r--r-- 1 tomcat tomcat 496 May 13 18:59 logtest_tomcat.2014-05-13_1858.0.log.gz -rw-r--r-- 1 tomcat tomcat 1244 May 13 19:01 logtest_tomcat.2014-05-13_1900.0.log.gz -rw-r--r-- 1 tomcat tomcat 496 May 13 19:02 logtest_tomcat.2014-05-13_1901.0.log.gz -rw-r--r-- 1 tomcat tomcat 514 May 13 19:04 logtest_tomcat.2014-05-13_1903.0.log.gz -rw-r--r-- 1 tomcat tomcat 500 May 13 19:05 logtest_tomcat.2014-05-13_1904.0.log.gz -rw-r--r-- 1 tomcat tomcat 522 May 13 19:07 logtest_tomcat.2014-05-13_1906.0.log.gz The file format is yyyy-mm-dd_HHmm - so you can see that 1847, 1850, 1853, 1856, 1859, 1902, 1905 are all missing. I've checked the contents - the sequential numbering on the log statements jumps by 60 for the missing logs - so it's not that multiple minutes are being collapsed into a single rolled over log. We also thought it might be due to our Splunk forwarder - we ran the test both with and without the Splunk forwarder running, and got the same results - every third log file is missing. Here's the logback appender for this test: <appender name="daily" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>${bc.logs.home}/logtest_tomcat.log</file> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">  <fileNamePattern>${bc.logs.home}/logtest_tomcat.%d{yyyy-MM-dd_HHmm}.%i.log.gz</fileNamePattern> <timeBasedFileNamingAndTriggeringPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP">  <maxFileSize>250MB</maxFileSize> </timeBasedFileNamingAndTriggeringPolicy> <maxHistory>60</maxHistory> </rollingPolicy> <append>true</append> <encoder> <pattern>%d{"yyyy-MM-dd HH:mm:ss,SSS z", UTC} [%thread] %-5level %logger{36} - %msg%n</pattern> </encoder> </appender> And here's my little driver class (the 'BCLog' is a simple wrapper around slf4j logging, instantiated by Logger log = LoggerFactory.getLogger(clazz); ) package com.sirsidynix.logtest.biz.svc.impl; import com.sirsidynix.bccommon.util.BCLog; import com.sirsidynix.bccommon.util.BCLogFactory; import org.springframework.beans.factory.DisposableBean; import org.springframework.beans.factory.InitializingBean; public class JustLogIt implements InitializingBean, DisposableBean { private static final BCLog LOG = BCLogFactory.getLog(JustLogIt.class); private Thread thread; @Override public void afterPropertiesSet() throws Exception { LOG.info("Firing up JustLogIt thread"); thread = new Thread(){ @Override public void run() { long iteration = 0; while (true) { try { Thread.sleep(1000); iteration++; LOG.info("Logging Iteration " + iteration); } catch (InterruptedException e) { LOG.info("LogIt thread sleep interrupted!!!"); } } } }; thread.start(); } @Override public void destroy() throws Exception { LOG.info("Shutting down JustLogIt thread"); thread.interrupt(); } } Any ideas? Thanks! Bob Sandiford | Principal Engineer | SirsiDynix P: 800.288.8020 X6943 | Bob.Sandiford(a)sirsidynix.com<mailto:Bob.Sandiford@sirsidynix.com> www.sirsidynix.com<http://www.sirsidynix.com/> Join the conversation: Like us on Facebook!<http://www.facebook.com/SirsiDynix> Follow us on Twitter!<http://twitter.com/SirsiDynix>

2 2