February 2012 - logback-user

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

(Important) Dynamically change the scan period
by Yihya Hugirat 08 Apr '13

08 Apr '13

hi all, i have migrated to logback to be able to change the log levels dynamically. i'm testing it now with calssfish 3.01 and somehow it is not working when i change the levels in logback.xml there nothing happens. by deploying from netbeans i get the following: |-INFO in ch.qos.logback.classic.turbo.ReconfigureOnChangeFilter@11bfee0 - Will scan for changes in [[C:\Dokumente und Einstellungen\user_Home\Eigene Dateien\NetBeansProjects\WS-LDAP\build\web\WEB-INF\classes\logback.xml]] every 15 seconds. but when i change the levels in this file nothing happens Any help will be appreciated Hugirat -- إِنَّ الَّذِينَ يُحِبُّونَ أَنْ تَشِيعَ الْفَاحِشَةُ فِي الَّذِينَ آمَنُوا لَهُمْ عَذَابٌ أَلِيمٌ فِي الدُّنْيَا وَالآخِرَةِ وَاللَّهُ يَعْلَمُ وَأَنْتُمْ لا تَعْلَمُونَ My public key please use it when you contact me: هذا مفتاحي العام الرجاء أستخدامه عند الإتصال بي: 09BA B710 4B98 ECDA 8C0A 6CB1 2E1E CF88 6A12 F2C3

3 4

Websphere specific JMX configuration?
by Sumanth Donthi 12 Jun '12

12 Jun '12

How can we enable JMX for logback in WebSphere ? Currently do not see ch.qos.logback.classic.jmx.Configurator in jconsole though <jmxConfigurator/> tag exist in logback configuration file. logback 0.9.27 WebSphere 7.0 This is similar to one posted earlier -- http://www.qos.ch/pipermail/logback-user/2010-November/001886.html -Sumanth

4 6

SMTPAppender mail not sent (logback 1.0.0, JDK 1.5)
by Louis-Félix 03 May '12

03 May '12

Hi, I upgraded to logback 1.0.0 in a web application (tomcat 5, JDK 1.5), and the ERROR email are not sent anymore from the SMTPAppender. When I rollback my logback-core and logback-classic JARs to version 0.9.30, it's working again. I have a simple config: <appender name="courriel" class="ch.qos.logback.classic.net.SMTPAppender"> <smtpHost>smtp.xxx.xx.xx</smtpHost> <to>xxx(a)xxx.xx.xx</to> <from>no-reply.ti(a)xxx.xx.xx</from> <subject>Test</subject> <cyclicBufferTracker class="ch.qos.logback.core.spi.CyclicBufferTrackerImpl"> <bufferSize>25</bufferSize> </cyclicBufferTracker> <layout class="ch.qos.logback.classic.html.HTMLLayout"> <pattern>%date%level%thread%logger%line%message</pattern> </layout> </appender> I am using logback 1.0.0 with no problem in an other project (with JDK 1.6). Is there any known compatibility problem between logback 1.0.0 and JDK 1.5? Thanks, Louis-Félix

6 10

Sane solution for centralised logging with logback
by Michael McCarthy 29 Feb '12

29 Feb '12

Hi all, Just working on a solution for centralised logging in our development environment, and it would be good to get some feedback. The solution until this morning was this: - Developers build apps with their own logback.xml inside - These get deployed to jboss. A system property for the logback file kicks in, and the logback file on jboss takes precedence over the application one. This logback file has a gelf appender, and all logging is done centrally. This works perfectly, logback is working well, logback-gelf is working well to. The only problem with it is once more applications are deployed. When looking at logs we suddenly have no idea which app a log is coming from. The change of plan would be to use the contextName. What I was thinking was that the war files get stripped at deploy time, their logback files removed and replaced with a generic one (that has the gelf stuff). This logback config would have a contextName which would be written to on the fly. The war would then get re-assembled and deployed. Any feedback appreciated, the basic goals are that all applications should be logging the exact same way, centrally, and that is should be possible to distinguish which app a log has come from given that multiple apps can be deployed to the same app server. Many thanks :)

1 0

Multiple date patterns in filename pattern
by Chris Lemper 28 Feb '12

28 Feb '12

Hi Logback users! I would like to store daily log files in the format: /logs/%d{yyyy/MM}/app.%d{yyyyMMdd}.log So that the end result is: /logs/2012/02/app.20120228.log That is I would like all daily log files for a given month in a single directory but each log file containing the full date. However, when I configure this filename pattern using ch.qos.logback.core.rolling.TimeBasedRollingPolicy, logback bases the rolling policy only on the first pattern: INFO in c.q.l.core.rolling.DefaultTimeBasedFileNamingAndTriggeringPolicy - The date pattern is 'yyyy/MM' from file name pattern '/logs/%d{yyyy/MM}/app.%d{yyyyMMdd}.log'. INFO in c.q.l.core.rolling.DefaultTimeBasedFileNamingAndTriggeringPolicy - Rollover at start of every month. Is it possible to accomplish this, even by just forcing the rollover to be daily (at midnight) independent of the filename pattern? I have looked through the mailing lists, documentation, and source code and cannot figure out how or if it can be done. Thanks, Chris Lemper

3 2

Is it possible to acces MDC values as properties?
by Stefan Eder 26 Feb '12

26 Feb '12

Hi, applies to Logback classic 1.0.0. Is it possible to acces MDC values as properties like this: <file>${catalina.base}/logs/exchanges/${breadcrumbId}-gsem.log</file> <encoder> <pattern>...</pattern> </encoder> where 'breadcrumbId' is mapped in the MDC. The above example produces a file named breadcrumbId_IS_UNDEFINED-gsem.log. The snippet is used in a sifting appender, but 'breadcrumbId' is not the descriminator. Do I have to use another notation or do I have to implement ch.qos.logback.core.spi.PropertyDefiner? Thanks, Stefan

2 2

class & line conversion words not working
by Chris Cheshire 23 Feb '12

23 Feb '12

I have just upgraded to logback 1.0 (from 0.9.x), and now the conversion words for %class and %line just produce a question mark. My pattern layout is <layout class="ch.qos.logback.classic.PatternLayout"> <Pattern>%date [%thread] %-5level %logger %n%n Class : %class%n Line : %line%n%n%message%n</Pattern> </layout> Prior to the update this was working and now it's not. Everything else in the layout displays as specified, except %class and %line. I do have the java compiler generating debug information too. Any suggestions? Chris

1 2

issues with logback-demo
by Arun Ramakrishnan 23 Feb '12

23 Feb '12

I tried the demo today and ran into the following issues during the jetty:run stage. This is for Maven 3 and Mac OS X. This is the full console output <https://gist.github.com/1889422>to the command "mvn package jetty:run" Here is the first exception thats thrown. ************** 02:43:01 [pool-1-thread-1] INFO ch.qos.logback.demo.LoggingTask - Howdydy-diddly-ho - 99 java.lang.Exception: e at ch.qos.logback.demo.LoggingTask.run(LoggingTask.java:28) [classes/:na] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) [na:1.6.0_29] at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) [na:1.6.0_29] at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) [na:1.6.0_29] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) [na:1.6.0_29] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180) [na:1.6.0_29] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204) [na:1.6.0_29] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [na:1.6.0_29] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [na:1.6.0_29] at java.lang.Thread.run(Thread.java:680) [na:1.6.0_29] 02:43:11 [pool-1-thread-1] INFO ch.qos.logback.demo.LoggingTask - Howdydy-diddly-ho - 199 java.lang.Exception: e at ch.qos.logback.demo.LoggingTask.run(LoggingTask.java:28) [classes/:na] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) [na:1.6.0_29] at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) [na:1.6.0_29] at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) [na:1.6.0_29] *************************** System Info ******************************* Apache Maven 3.0.3 (r1075438; 2011-02-28 09:31:09-0800) Maven home: /usr/share/maven Java version: 1.6.0_29, vendor: Apple Inc. OS name: "mac os x", version: "10.7.2", arch: "x86_64", family: "mac" *************************************

1 0

Creating logback logger programmatically
by Yusuf Soysal 22 Feb '12

22 Feb '12

Hello everyone, I'm sorry to post this message again, but I have no clue to continue. Is it possible to solve this issue in anyway? By the way, I was able to accomplish this with log4j :( Regards ---------------------- Hello, I have a problem regarding to logback project. My requirement is I have to create log properties dynamically. Let me explain this by an example. My project creates socket communication with external system and it may have multiple sockets. For each socket, I want to have different log files which will contain the messages that is read and sent. To accomplish this, I create the logger for sockets programmatically. Problem is when I want to reconfigure loggers based on logback.xml (by adding scan="true" or by reinitializing the logback), the loggers I created becomes unusable. How can I fixed that or can you advise me another solution? This is my configuration file (logback.xml) <?xml version="1.0" ?> <configuration> <property name="HOME_PATH" value="/data/logs/myapp/" scope="CONTEXT" /> <property name="MYAPP_LOG_FILE" value="myapp.log" /> <property name="MYAPP_ROLLING_TEMPLATE" value="%d{yy-MM-dd}" scope="CONTEXT" /> <property name="MYAPP_OLD_LOG_FILE" value="${MYAPP_LOG_FILE}.%d{yy-MM-dd}" /> <property name="DEFAULT_PATTERN" value="%d{yyyy-MM-dd HH:mm:ss.SSS} [%file:%line] [%level] %msg%n" scope="CONTEXT" /> <appender name="myAppender" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>${HOME_PATH}${MYAPP_LOG_FILE}</file> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <fileNamePattern>${HOME_PATH}${MYAPP_LOG_FILE}.${MYAPP_ROLLING_TEMPLATE}</fileNamePattern> </rollingPolicy> <encoder class="ch.qos.logback.classic.encoder.PatternLayoutEncoder"> <pattern>${DEFAULT_PATTERN}</pattern> </encoder> </appender> <logger name="com.myapp" level="DEBUG" additivity="false"> <appender-ref ref="myAppender" /> </logger> <root level="OFF"> </root> </configuration> and here you can see how I create loggers programmatically (again, I do this only for socket logs). public static Logger createLogger(String name) { ch.qos.logback.classic.Logger templateLogger = (ch.qos.logback.classic.Logger) LogUtil.getLogger("com.myapp"); LoggerContext context = templateLogger.getLoggerContext(); String logDir = context.getProperty("HOME_PATH"); PatternLayoutEncoder encoder = new PatternLayoutEncoder(); encoder.setPattern(context.getProperty("DEFAULT_PATTERN")); encoder.setContext(context); DefaultTimeBasedFileNamingAndTriggeringPolicy<ILoggingEvent> timeBasedTriggeringPolicy = new DefaultTimeBasedFileNamingAndTriggeringPolicy<ILoggingEvent>(); timeBasedTriggeringPolicy.setContext(context); TimeBasedRollingPolicy<ILoggingEvent> timeBasedRollingPolicy = new TimeBasedRollingPolicy<ILoggingEvent>(); timeBasedRollingPolicy.setContext(context); timeBasedRollingPolicy.setFileNamePattern(logDir + name + ".log." + context.getProperty("MYAPP_ROLLING_TEMPLATE")); timeBasedRollingPolicy.setTimeBasedFileNamingAndTriggeringPolicy(timeBasedTriggeringPolicy); timeBasedTriggeringPolicy.setTimeBasedRollingPolicy(timeBasedRollingPolicy); RollingFileAppender<ILoggingEvent> rollingFileAppender = new RollingFileAppender<ILoggingEvent>(); rollingFileAppender.setAppend(true); rollingFileAppender.setContext(context); rollingFileAppender.setEncoder(encoder); rollingFileAppender.setFile(logDir + name + ".log"); rollingFileAppender.setName(name + "Appender"); rollingFileAppender.setPrudent(false); rollingFileAppender.setRollingPolicy(timeBasedRollingPolicy); rollingFileAppender.setTriggeringPolicy(timeBasedTriggeringPolicy); timeBasedRollingPolicy.setParent(rollingFileAppender); encoder.start(); timeBasedRollingPolicy.start(); rollingFileAppender.stop(); rollingFileAppender.start(); ch.qos.logback.classic.Logger logbackLogger = (ch.qos.logback.classic.Logger) LogUtil.getLogger(name); logbackLogger.setLevel(templateLogger.getLevel()); logbackLogger.setAdditive(false); logbackLogger.addAppender(rollingFileAppender); return logbackLogger; } And this is how I reinitialize logback private static void initializeLogback() { File logbackFile = new File(logFilePath); System.setProperty("logback.configurationFile", logbackFile.getAbsolutePath()); StaticLoggerBinder loggerBinder = StaticLoggerBinder.getSingleton(); LoggerContext loggerContext = (LoggerContext) loggerBinder.getLoggerFactory(); loggerContext.reset(); JoranConfigurator configurator = new JoranConfigurator(); configurator.setContext(loggerContext); try { configurator.doConfigure(logbackFile); } catch( JoranException e ) { throw new ColumbusRuntimeException(e.getMessage(), e); } } Note: I also posted the same question to stackoverflow: http://stackoverflow.com/questions/9060545/creating-logback-logger-programm…

1 0