August 2012 - logback-user - mailman3.qos.ch

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

Replacing Tomcat7 Logging with Logback?
by James Carr 17 Sep '13

17 Sep '13

Hi All, Is there a good tutorial or documentation on replacing Tomcat's default logging with logback? So far my searches turn up http://logback.qos.ch/access.html which only seems to work with access logs, not the actual server logging itself. Thanks, James

4 3

(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

Externalized Logback configuration for web applications
by Perryn Fowler 01 Feb '13

01 Feb '13

Hello, I have a logging use case that I would think was relatively common, but that does not seem to be supported particularly well by logback. I wanted to see what the logback community thinks/advises. The details of the use case - I am writing java web apps to be deployed to JEE web containers. - I want the logging config to be external to the wars, so that I can use the same wars in different environments, but configure logging differently. - I want to be able to deploy several different wars to the same web container and have them use different logging configurations. The logback documentation seems to push towards either packaging the logback config in the wars, or sharing an external logging config between them. (Whereas I want separate external logging configuration for each war) I hope that makes sense. The JNDI support described here: http://logback.qos.ch/manual/loggingSeparation.html looks like it might be of use, but it does seem to require that the config files are placed in WEB-INF/classes and I would prefer they are completely external to the war. I have found a number of people who have coded up their own solutions, notably: http://blog.iprofs.nl/tag/logback/ and https://bowerstudios.com/node/896 That doesn't look too bad, but wondering what the community thinks of these approaches -- ----------------------- Perryn Fowler

6 10

SMTPAppender, HTMLLayout with text/plain
by Filipe Sousa 14 Nov '12

14 Nov '12

Hi. For some reason I'm receiving email reports with mime type text/plain and my email client shows all the html code. I'm attaching a report sent by logback. I'm using javax.mail 1.4.4 and this logback (1.0.3) configuration <?xml version="1.0" encoding="UTF-8"?> <configuration scan="true" scanPeriod="5000"> <appender name="file" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>../logs/sama.log</file> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <fileNamePattern>logFile.%d{yyyy-MM-dd}.log</fileNamePattern> <maxHistory>30</maxHistory> </rollingPolicy> <encoder> <pattern>%d [%thread] %-5level %logger{36} - %msg%n</pattern> </encoder> </appender> <appender name="mail" class="ch.qos.logback.classic.net.SMTPAppender"> <smtpHost>mail.ipb.pt</smtpHost> <to>filipe(a)ipb.pt</to> <from>noreply(a)ipb.pt</from> <subject>[sama]: %logger{20} - %m</subject> <layout class="ch.qos.logback.classic.html.HTMLLayout" /> <filter class="ch.qos.logback.classic.filter.ThresholdFilter"> <level>WARN</level> </filter> </appender> <logger name="org.eclipse.jetty" level="WARN" /> <logger name="org.apache.cxf" level="WARN"/> <logger name="pt.ipb.sama" level="WARN" /> <root level="WARN"> <appender-ref ref="file" /> <appender-ref ref="mail"/> </root> </configuration> Thanks -- Filipe Sousa

2 1

java.lang.ClassCircularityError: java/util/logging/LogRecord
by Sergey Parhomenko 02 Sep '12

02 Sep '12

Hi, I am using logback (latest version) on Tomcat, and have this error when trying to start the application: *Exception in thread "RMI RenewClean-<ip>:<port>" java.lang.ClassCircularityError: java/util/logging/LogRecord* *at org.slf4j.bridge.SLF4JBridgeHandler.getSLF4JLogger(SLF4JBridgeHandler.java:200) * *at org.slf4j.bridge.SLF4JBridgeHandler.publish(SLF4JBridgeHandler.java:289) * *at java.util.logging.Logger.log(Logger.java:458)* *at java.util.logging.Logger.doLog(Logger.java:480)* *at java.util.logging.Logger.logp(Logger.java:596)* The error is blocking Tomcat startup. The application has logback and jul-over-slf4j bridge JARs inside, and is using a servlet context listener to run * SLF4JBridgeHandler.removeHandlersForRootLogger()* and * SLF4JBridgeHandler.install()* on startup. The *logback.xml* used has * ch.qos.logback.classic.jul.LevelChangePropagator* context listener in it, with *resetJUL* set to *true*. I saw a thread on this mailing list in February 2011<http://mailman.qos.ch/pipermail/slf4j-user/2011-February/001044.html> with the similar issue so it might be quite old. Tomcat version is 7, but the mail list thread and this StackOverflow<http://stackoverflow.com/questions/2656565/classcircularityerror-when-runni…>question are using Tomcat 6 and having the same problem. As the last answer on StackOverflow correctly says, error is reproducible only if the *LevelChangePropagator* element is in the beginning of * logback.xml*. Moving it to the end of the file fixes the issue, so it has an easy workaround. If you have problems reproducing it please let me know, I'll try to provide a test project. -- Best regards, Sergey Parhomenko

2 2

occasional logging exceptions in tomcat
by feedly team 31 Aug '12

31 Aug '12

I am using logback within tomcat using the sifting appender. Occasionally I see "IO failure in appender java.nio.channels.ClosedChannelException" exception in catalina.out. I have prudent mode set to true, and although I have multiple webapps deployed, only one is actually logging messages, though it is doing so from shared libraries as well as app code and multi-threaded. I am using slf4j 1.6.1 and logback 1.0.3. How can I debug this issue? Configuration and full stack below: <configuration> <statusListener class="ch.qos.logback.core.status.OnConsoleStatusListener" /> <appender name="SIFT" class="ch.qos.logback.classic.sift.SiftingAppender"> <discriminator class="ch.qos.logback.classic.sift.JNDIBasedContextDiscriminator"> <defaultValue>unknown</defaultValue> </discriminator> <sift> <appender name="FILE-${contextName}" class="ch.qos.logback.core.rolling.RollingFileAppender"> <prudent>true</prudent> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">  <fileNamePattern>${catalina.home}/logs/${contextName}.%d{yyyy-MM-dd}.log</fileNamePattern>  <maxHistory>90</maxHistory> </rollingPolicy> <encoder> <pattern>%logger{35}[%level|%thread|%d{HH:mm:ss}]: %msg%n</pattern> </encoder> </appender> </sift> </appender> <root level="INFO"> <appender-ref ref="SIFT" /> </root> </configuration> 10:20:05,777 |-ERROR in ch.qos.logback.core.rolling.RollingFileAppender[FILE-jobs.v1] - IO failure in appender java.nio.channels.ClosedChannelException at java.nio.channels.ClosedChannelException at at sun.nio.ch.FileChannelImpl.ensureOpen(FileChannelImpl.java:88) at at sun.nio.ch.FileChannelImpl.position(FileChannelImpl.java:243) at at ch.qos.logback.core.FileAppender.safeWrite(FileAppender.java:188) at at ch.qos.logback.core.FileAppender.writeOut(FileAppender.java:204) at at ch.qos.logback.core.OutputStreamAppender.subAppend(OutputStreamAppender.java:211) at at ch.qos.logback.core.rolling.RollingFileAppender.subAppend(RollingFileAppender.java:148) at at ch.qos.logback.core.OutputStreamAppender.append(OutputStreamAppender.java:102) at at ch.qos.logback.core.UnsynchronizedAppenderBase.doAppend(UnsynchronizedAppenderBase.java:88) at at ch.qos.logback.core.sift.SiftingAppenderBase.append(SiftingAppenderBase.java:94) at at ch.qos.logback.core.AppenderBase.doAppend(AppenderBase.java:85) at at ch.qos.logback.core.spi.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:53) at at ch.qos.logback.classic.Logger.appendLoopOnAppenders(Logger.java:282) at at ch.qos.logback.classic.Logger.callAppenders(Logger.java:269) at at ch.qos.logback.classic.Logger.buildLoggingEventAndAppend(Logger.java:470) at at ch.qos.logback.classic.Logger.filterAndLog_0_Or3Plus(Logger.java:424) at at ch.qos.logback.classic.Logger.error(Logger.java:583) After failure, the appender seems to recover, but I assume I am losing log messages: 10:25:56,689 |-WARN in ch.qos.logback.core.rolling.RollingFileAppender[FILE-jobs.v1] - Attempted to append to non started appender [FILE-jobs.v1]. 10:25:56,724 |-WARN in ch.qos.logback.core.rolling.RollingFileAppender[FILE-jobs.v1] - Attempted to append to non started appender [FILE-jobs.v1]. 10:25:56,738 |-WARN in ch.qos.logback.core.rolling.RollingFileAppender[FILE-jobs.v1] - Attempted to append to non started appender [FILE-jobs.v1]. 10:25:57,449 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.rolling.RollingFileAppender] 10:25:57,449 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [FILE-jobs.v1] 10:25:57,450 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy - No compression will be used 10:25:57,450 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy - Will use the pattern /etc/webserver/logs/jobs.v1.%d{yyyy-MM-dd}.log for the active file 10:25:57,450 |-INFO in c.q.l.core.rolling.DefaultTimeBasedFileNamingAndTriggeringPolicy - The date pattern is 'yyyy-MM-dd' from file name pattern '/etc/webserver/logs/jobs.v1.%d{yyyy-MM-dd}.log'. 10:25:57,450 |-INFO in c.q.l.core.rolling.DefaultTimeBasedFileNamingAndTriggeringPolicy - Roll-over at midnight. 10:25:57,450 |-INFO in c.q.l.core.rolling.DefaultTimeBasedFileNamingAndTriggeringPolicy - Setting initial period to Tue Aug 28 10:25:57 PDT 2012 10:25:57,450 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property 10:25:57,451 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[FILE-jobs.v1] - Active log file name: /etc/webserver/logs/jobs.v1.2012-08-28.log 10:25:57,451 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[FILE-jobs.v1] - File property is set to [null]

1 1

Release of logback-beagle 1.1.3
by ceki 31 Aug '12

31 Aug '12

Hello all, I am happy to announce the release of logback-beagle 1.1.3, an eclipse plug-in for viewing logs. Compared to release 1.1.2, this release fixes a number of bugs and adds minor new features. - Fixed issues: CONSPLUG-34 modification of logger tree incorrectly clears all buffers - Documentation For more information on logback-beagle please see: http://logback.qos.ch/beagle/ - Installation Logback-beagle requires the Nebula Grid which can be installed from http://download.eclipse.org/technology/nebula/snapshot/ Once Nebula Grid is installed, you can install logback-beagle from http://logback.qos.ch/p2/ - Upgrading If you have already installed a previous version of logback-beagle, invoking Help -> "Check for Updates" in Eclipse should discover this new release of logback-beagle. - Announcement mailing list 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 http://tinyurl.com/proLogback

1 0

Release of logback-beagle 1.1.2
by ceki 28 Aug '12

28 Aug '12

Hello all, I am happy to announce the release of logback-beagle 1.1.2, an eclipse plug-in for viewing logs. Compared to release 1.1.0, this release fixes a number of bugs and adds minor new features. Here is the list of fixed issues: CONSPLUG-32, compatibility with Java 1.6 CONSPLUG-33, clearing does not clear internal buffers CONSPLUG-29, added ability to change the font used CONSPLUG-31, toggle to view/hide the logger tree For more information on logback-beagle please see: http://logback.qos.ch/beagle/ Logback-beagle requires the Nebula Grid which can be installed from http://download.eclipse.org/technology/nebula/snapshot/ Once Nebula Grid is installed, you can install logback-beagle from http://logback.qos.ch/p2/ 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 http://tinyurl.com/proLogback

1 0

Release of logback-beagle 1.1.0
by ceki 28 Aug '12

28 Aug '12

Hello all, I am happy to announce the release of logback-beagle 1.1.0, an eclipse plug-in for viewing logs. This release is a complete overhaul of the code bringing several new features. For more information on logback-beagle please see: http://logback.qos.ch/beagle/ Logback-beagle requires the Nebula Grid which can be installed from http://download.eclipse.org/technology/nebula/snapshot/ Once Nebula Grid is installed, you can install logback-beagle from http://logback.qos.ch/p2/ 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 http://tinyurl.com/proLogback

2 2