- logback-user - mailman3.qos.ch

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

Log rotation every 12 hrs at noon and mid night
by srinandina＠gmail.com 11 Jun '14

11 Jun '14

I have defined TimeBasedRollingPolicy using: <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">  <fileNamePattern>${log.dir}/app.log.%d{yyyy-MM-dd-a}</fileNamePattern> </rollingPolicy> But the log file is being rotated only once a day at 12 AM. Looking at the code PeriodicityType enum has an entry 'HALF_DAY' but is not present in the valid list. Is this supported by logback? Thanks, Srinivas

1 0

Recognize OSGi bundle resource in ConfigurationWatchList.convertToFile
by Ashwin Jha 10 Jun '14

10 Jun '14

Hi, The current implementation of ConfigurationWatchList.convertToFile returns null when the URL type is not file. Due to this automatic reloading on change of configuration does not work in OSGi bundles. This problem occurs even if you use a fragment. As in any case, the logback.xml file will be recognized as bundleresource type and not as file type. This is necessary as the logback.xml config file is recognized during the start up time. So, it creates confusion as the file is found first time around and then the reloading does not occur. And, this is not mentioned in the documentation either. Given that logback has a p2 repository for OSGi support, IMHO this feature is a must. BTW I would love to contribute this feature. Regards, Ashwin

2 1

[logback-dev] Change implementation of MessageFormatter for byte[]
by Thorsten Schöning 09 Jun '14

09 Jun '14

Hi all, I have a use case where I need to log some byte[] and the current default behavior of slf4j seems to be to print decimal values for each item in the array. I would prefer hex notation instead and can't seem to find any way to configure that behavior. It seems to me it's hard coded using LoggingEvent.getFormattedMessage and MessageFormatte.byteArrayAppend. Is there any way to change this behavior? The only thing coming into my mind is overriding LoggingEvent with a custom getFormattedMessage method, but I don't know how to get Logback using that internally. And I wouldn't want to re-implement MessageFormatter because it's most interesting methods are private. Any other options like parsing the formatted message afterwards and convert it to contain hex bytes instead? Though it sounds a lot more difficult than converting into the format I want in the first place. Thanks for your help! Mit freundlichen Grüßen, Thorsten Schöning -- Thorsten Schöning E-Mail:Thorsten.Schoening@AM-SoFT.de AM-SoFT IT-Systeme http://www.AM-SoFT.de/ Telefon...........05151- 9468- 55 Fax...............05151- 9468- 88 Mobil..............0178-8 9468- 04 AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow _______________________________________________ logback-dev mailing list logback-dev(a)qos.ch http://mailman.qos.ch/mailman/listinfo/logback-dev

1 0

Logback Spring Extension
by Ben M 03 Jun '14

03 Jun '14

I follow the configuration described at: https://github.com/qos-ch/logback-extensions/wiki/Spring but the one piece i don't understand is: <bean class="ch.qos.logback.classic.encoder.PatternLayoutEncoder" init-method="start" destroy-method="stop"> <property name="context" value="#{ T(org.slf4j.LoggerFactory).getILoggerFactory() }"/> <property name="pattern" value="%date %-5level [%thread] %logger{36} %m%n"/> </bean> The result of org.slf4j.LoggerFactory.getILoggerFactory() is a an ILoggerFactory which shares no class hierarchy with a ch.qos.logback.core.Context. What is happening here?

1 0

multiple servlet with differents files in glassfish
by Pablo Martínez Campo 27 May '14

27 May '14

I am trying to deploy 2 servlets in glassfish with log4f library. I have no problems in tomcat. Each servlet writes in its own file but in tomcat, I found this guide https://blogs.oracle.com/naman/entry/configure_log4j_for_use_in to configure and support log4f library. I got the first servlet working with it. And it writes logs in its log file. But whenever I deploy the secod servlet, I don't see its logs. The first one keeps writing in its own file but the second one not. I modify the logback.xml file included in config folder to include both files and all packages but it seems to ignore it. This is my logback.xml file: <?xml version="1.0" encoding="UTF-8"?> <configuration> <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">  <encoder> <pattern>%d{HH:mm:ss.SSS} [%thread] %-5level %logger{5} - %msg%n</pattern> </encoder> </appender> <logger name="com.lordofthejars.foo" level="INFO" additivity="false"> <appender-ref ref="STDOUT" /> </logger> <appender name="SERVER-FILE" class="ch.qos.logback.core.rolling.RollingFileAppender"> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> 0 <fileNamePattern>/root/glassfish4/glassfish/domains/domain1/logs/serverregister-%d{yyyy-MM-dd}.%i.log</fileNamePattern>  <maxHistory>7</maxHistory> <TimeBasedFileNamingAndTriggeringPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP"> <MaxFileSize>512MB</MaxFileSize> </TimeBasedFileNamingAndTriggeringPolicy> </rollingPolicy> <append>true</append> <encoder> <pattern>%d{dd-MM-yyyy HH:mm:ss.SSS} [%p] %logger{5}:%L - %msg%n</pattern> </encoder> </appender> <appender name="REGMAN-FILE" class="ch.qos.logback.core.rolling.RollingFileAppender"> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">   <fileNamePattern>/root/glassfish4/glassfish/domains/domain1/logs/registermanager-%d{yyyy-MM-dd}.%i.log</fileNamePattern>  <maxHistory>7</maxHistory> <TimeBasedFileNamingAndTriggeringPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP"> <MaxFileSize>512MB</MaxFileSize> </TimeBasedFileNamingAndTriggeringPolicy> </rollingPolicy> <append>true</append> <encoder> <pattern>%d{dd-MM-yyyy HH:mm:ss.SSS} [%p] %logger{5}:%L - %msg%n</pattern> </encoder> </appender> <logger name="com.eu.iotapi.handlers.AuthenticationGatewayHandler" level="DEBUG" additivity="false"> <appender-ref ref="SERVER-FILE"/> </logger> <logger name="com.eu.iotapi.handlers.AuthenticationHandler" level="DEBUG" additivity="false"> <appender-ref ref="SERVER-FILE"/> </logger> <logger name="com.eu.iotapi.handlers.DeviceValidationHandler" level="DEBUG" additivity="false"> <appender-ref ref="SERVER-FILE"/> </logger> <logger name="com.eu.iotapi.handlers.EventValidationHandler" level="DEBUG" additivity="false"> <appender-ref ref="SERVER-FILE"/> </logger> <logger name="com.eu.iotapi.handlers.GatewayValidationHandler" level="DEBUG" additivity="false"> <appender-ref ref="SERVER-FILE"/> </logger> <logger name="com.eu.iotapi.handlers.ObservationValidationHandler" level="DEBUG" additivity="false"> <appender-ref ref="SERVER-FILE"/> </logger> <logger name="com.eu.iotapi.resources.PublicationsResource" level="DEBUG" additivity="false"> <appender-ref ref="SERVER-FILE"/> </logger> <logger name="com.eu.iotapi.resources.RegisterDeviceOnBackground" level="DEBUG" additivity="false"> <appender-ref ref="SERVER-FILE"/> </logger> <logger name="com.eu.iotapi.resources.RegisterGatewayOnBackground" level="DEBUG" additivity="false"> <appender-ref ref="SERVER-FILE"/> </logger> <logger name="com.eu.iotapi.resources.RegistrationResource" level="DEBUG" additivity="false"> <appender-ref ref="SERVER-FILE"/> </logger> <logger name="com.eu.iotapi.resources.SubmitEventOnBackground" level="DEBUG" additivity="false"> <appender-ref ref="SERVER-FILE"/> </logger> <logger name="com.eu.iotapi.resources.SubmitObservationOnBackground" level="DEBUG" additivity="false"> <appender-ref ref="SERVER-FILE"/> </logger> <logger name="com.eu.iotapi.uns.device.RegisterDeviceHandler" level="DEBUG" additivity="false"> <appender-ref ref="SERVER-FILE"/> </logger> <logger name="com.eu.iotapi.uns.events.SubmitEventsHandler" level="DEBUG" additivity="false"> <appender-ref ref="SERVER-FILE"/> </logger> <logger name="com.eu.iotapi.uns.device.RegisterGatewayHandler" level="DEBUG" additivity="false"> <appender-ref ref="SERVER-FILE"/> </logger> <logger name="com.eu.iotapi.uns.observations.SubmitObservationsHandler" level="DEBUG" additivity="false"> <appender-ref ref="SERVER-FILE"/> </logger> <logger name="com.eu.iotapi.resources.DeviceTranslator" level="DEBUG" additivity="false"> <appender-ref ref="SERVER-FILE"/> </logger> <logger name="com.eu.registermanager.eventbroker.device.registration.DeviceRegistrationHandler" level="DEBUG" additivity="false"> <appender-ref ref="REGMAN-FILE"/> </logger> <logger name="com.eu.registermanager.eventbroker.gateway.GatewayRegistrationHandler" level="DEBUG" additivity="false"> <appender-ref ref="REGMAN-FILE"/> </logger> <logger name="com.eu.registermanager.handlers.AuthenticationGatewayHandler" level="DEBUG" additivity="false"> <appender-ref ref="REGMAN-FILE"/> </logger> <logger name="com.eu.registermanager.handlers.AuthenticationHandler" level="DEBUG" additivity="false"> <appender-ref ref="REGMAN-FILE"/> </logger> <logger name="com.eu.registermanager.resources.RegisterDeviceOnEventBrokerOnBackground" level="DEBUG" additivity="false"> <appender-ref ref="REGMAN-FILE"/> </logger> <logger name="com.eu.registermanager.resources.RegisterGatewayOnEventBrokerOnBackground" level="DEBUG" additivity="false"> <appender-ref ref="REGMAN-FILE"/> </logger> <logger name="com.eu.registermanager.resources.RegisterResource" level="DEBUG" additivity="false"> <appender-ref ref="REGMAN-FILE"/> </logger> <root level="INFO"> <appender-ref ref="STDOUT" /> </root> </configuration>

1 0

jcl-over-slf4j problem
by lee json 26 May '14

26 May '14

I understand this might not logback's issue, but I would like to collect more information so hope to fix my problem. Basically there is no problem to execute unit tests if I removed all logback related dependency. I am just wondering what inside jcl-over-slf4j may collide against dependencies in my project. I notice that when I add jcl-over-slf4j as dependency <dependency> <groupId>org.slf4j</groupId> <artifactId>jcl-over-slf4j</artifactId> <version>1.7.5</version> </dependency> this leads to my test case not being executed with maven result printed "no tests were executed!". My scala test version is 2.10 <dependency> <groupId>org.scalatest</groupId> <artifactId>scalatest_2.10</artifactId> <version>2.0</version> <scope>test</scope> </dependency> and junit version is 4.8.1 <dependency> <groupId>junit</groupId> <artifactId>junit</artifactId> <version>4.8.1</version> </dependency> If I comment out jcl-over-slf4j, maven reports "there are tests failure" Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.6:test (default-test) ...: There are test failures Please refer to.../target/surefire-reports for the individual test results. But surefire-reports folder actually is not created $ ls target/surefire-reports ls: cannot access target/surefire-reports: No such file or directory Environment I use Maven version is 3.0.5 Java version 1.6.x I appreciate any suggestions. Thanks

2 2

Switch logging to different files at runtime
by lee json 23 May '14

23 May '14

I test to run a sample logging message to a file. But I am wondering how can I switch logging to different files at runtime? For example, initially the message is logged to <log_dir>/<file_a>.log. Later on I would like the application to log message to <log_dir>/<file_b>.log. Is it doable with logback lib? I want to log message to logs/<parent_key_id>/<key_id>...log. Is RollingPolicy configured to start up once? How can I change logging to another log file such as logs/<parent_key_id1>/<key_id1>...log when certain condition is met? Thanks The current setting: logback.xml <?xml version="1.0" encoding="UTF-8"?> <configuration scan="false" debug="false"> <appender name="FILE" class="ch.qos.logback.core.rolling.RollingFileAppender"> <rollingPolicy class="sample.logging.MyRollingPolicy"> <FileNamePattern>%keyId_%d.log.gz</FileNamePattern> <MaxHistory>60</MaxHistory> </rollingPolicy> <layout class="ch.qos.logback.classic.PatternLayout">  <Pattern>[%4p] [%d{ISO8601}] [%t] %c{1}: %m%n</Pattern> </layout> </appender> <root level="INFO"> <appender-ref ref="FILE"/> </root> </configuration> MyRolling.scala package sample.logging import java.io.File import ch.qos.logback.core.rolling.TimeBasedRollingPolicy; class MyRollingPolicy[E] extends TimeBasedRollingPolicy[E] { override def setFileNamePattern(fnp: String) { try{ println("fnp passed in: "+fnp) val fnp1 = fnp.replace("%keyId", "k_1_3") println("[after replaced] fnp1 now is "+fnp1) val f = new File("logs/" + "parent_key_id"); // Logback will create any necessary parent paths. super.setFileNamePattern(f.getAbsolutePath() + "/" + fnp1); } catch { case e: Exception => { println("something go wrong..."+e) throw new RuntimeException(e); } } } }

2 2