November 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

Re: [logback-user] Add header-lines to each log file
by Schoeftner, Thomas 20 May '14

20 May '14

Sorry to bump this topic again. Any ideas? Thanks, -Tom

3 2

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

For RollingFileAppender, <rollingPolicy>/<fileNamePattern> does not work if you also have <appender>/<file>
by RobOaks 29 Nov '12

29 Nov '12

In addition to the problems I reported in my previous post ( http://old.nabble.com/Config-file-failures-unexplained-in-list-or-JIRA-td34… http://old.nabble.com/Config-file-failures-unexplained-in-list-or-JIRA-td34… ) , I have found that, for the RollingFileAppender, <rollingPolicy>/<fileNamePattern> does not work if you also have <appender>/<file>. Here is the relevant section of my config file: <appender name="file" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>Idcp.log</file> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <fileNamePattern>%d{yyyy-MM-dd_HH-mm}_Idcp.log</fileNamePattern> <maxHistory>3</maxHistory> </rollingPolicy> <encoder> <pattern>%-5level %logger{}.%method - %msg%n </pattern> </encoder> </appender> With this configuration, all output goes to Idcp.log indefinitely, in spite of the fact that it should be creating an archive file every minute. As soon as I remove <file>Idcp.log</file>, active output is logged to a file of the form yyyy-MM-dd_HH-mm_Idcp.log and a new file is created every minute. But, even in the latter case, when archive files are being properly created, <maxHistory> is ignored and archive files are created ad infinitum. Is this a particularly buggy release of Logback? I’m really hoping it’s just me. -- View this message in context: http://old.nabble.com/For-RollingFileAppender%2C-%3CrollingPolicy%3E-%3Cfil… Sent from the Logback User mailing list archive at Nabble.com.

2 2

Config file failures unexplained in list or JIRA
by RobOaks 29 Nov '12

29 Nov '12

I am encountering several initialization errors with the logback.xml file (below) that do not seem to be addressed in either this mailing list or JIRA. I am running Logback 1.0.7 with SLF4J 1.7.2. During initialization I receive the following Logback errors: 1. No applicable action for [outputPatternAsHeader]. Try as I might, I can not get Logback to recognize this property. 2. No applicable action for [immediateFlush]. This error may be expected, as I was able to glean from the list and JIRA that this property has been eliminated. Please confirm. 3. no applicable action for [withJansi] / There is no conversion class registered for composite conversion word [highlight]. I am including jansi-1.8.jar in the classpath but, obviously, this wouldn’t even come into play if withJansi isn’t even recognized. 4. Could not find Janino library on the class path. Skipping conditional processing. Both commons-compiler.jar and janino.jar 2.6.1 are on the classpath. I understand that there are potential issues with the use of conditional processing because of Janino and I’m wondering if I should abandon this feature, though it makes the config file significantly more elegant. Here is the config file: <?xml version="1.0" encoding="UTF-8"?> <configuration debug="true"> <property name="rootLevel" value="DEBUG"/> <property name="deployment" value="DEV"/> <property name="logFileFolder" value="c:/tmp/its"/> <property name="logFileName" value="Idcp"/> <property name="baseLayoutPattern" value="%logger{}.%method - %msg%n"/> <property name="fileLayoutPattern" value="%-5level ${baseLayoutPattern}"/> <property name="consoleLayoutPattern" value="%highlight(%-5level) ${baseLayoutPattern}"/> <property name="flowRowLayoutPattern" value="%msg%n"/> <property name="rollingPolicyPattern" value="${logFileFolder}/%d{yyyy-MM-dd}--${logFileName}.log"/> <property name="rollingPolicyMaxHistory" value="7"/>  <appender name="file" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>${logFileFolder}/${logFileName}.log</file> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <fileNamePattern>${rollingPolicyPattern}</fileNamePattern> <maxHistory>${rollingPolicyMaxHistory}</maxHistory> </rollingPolicy> <encoder> <pattern>${fileLayoutPattern}</pattern>  <immediateFlush>false</immediateFlush> <outputPatternAsHeader>true</outputPatternAsHeader> </encoder> </appender>  <appender name="fileFlowRow" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>${logFileFolder}/${logFileName}.log</file> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <fileNamePattern>${rollingPolicyPattern}</fileNamePattern> <maxHistory>${rollingPolicyMaxHistory}</maxHistory> </rollingPolicy> <encoder> <pattern>${flowRowLayoutPattern}</pattern>  <immediateFlush>false</immediateFlush> <outputPatternAsHeader>true</outputPatternAsHeader> </encoder> </appender>  <appender name="console" class="ch.qos.logback.core.ConsoleAppender"> <withJansi>true</withJansi> <encoder> <pattern>${consoleLayoutPattern}</pattern> </encoder> </appender>  <appender name="consoleFlowRow" class="ch.qos.logback.core.ConsoleAppender"> <encoder> <pattern>${flowRowLayoutPattern}</pattern> </encoder> </appender>  <logger name="idcpFlowRow" level="INHERITED"> <appender-ref ref="fileFlowRow"/> <if condition='!property("deployment").contains("PROD")'> <then> <appender-ref ref="consoleFlowRow"/> </then> </if> </logger>  <root level="${rootLevel}"> <appender-ref ref="file"/> <if condition='!property("deployment").contains("PROD")'> <then> <appender-ref ref="console"/> </then> </if> </root> </configuration> If I did something stupid or missed an explanation of these failures in the list, I apologize in advance. Thanks for your help. -- View this message in context: http://old.nabble.com/Config-file-failures-unexplained-in-list-or-JIRA-tp34… Sent from the Logback User mailing list archive at Nabble.com.

2 3

sifting appender is not compressing the last log file
by Shaul Zevin 27 Nov '12

27 Nov '12

Hello, Similar problem was already reported about a year ago: http://mailman.qos.ch/pipermail/logback-user/2011-November/002706.html I wonder if the problem is going to be fixed in the upcoming version. If not, what should be the most simple workaround? The most disturbing scenario related to this bug is that each value of a sifting attribute creates just one log file. The sift appender configuration is set for compression. The bug causes the log file to be left uncompressed, therefore no files are eventually compressed at all. <appender name="EXECUTION-SIFT" class="ch.qos.logback.classic.sift.SiftingAppender"> <discriminator> <key>userid</key> <defaultValue>noname</defaultValue> </discriminator> <sift> <appender name="EXECUTION" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>>${userid}.execution.log</file> <rollingPolicy class="ch.qos.logback.core.rolling.FixedWindowRollingPolicy">  <fileNamePattern>${userid}.execution.%i.log.zip</fileNamePattern> <maxIndex>100</maxIndex> </rollingPolicy> <triggeringPolicy class="ch.qos.logback.core.rolling.SizeBasedTriggeringPolicy"> <maxFileSize>${logFile.maxSize}</maxFileSize> </triggeringPolicy> <encoder> <pattern>%date{yyMMdd HH:mm:ss} %-5level %msg%n</pattern> <charset>UTF-8</charset> </encoder> </appender> </sift> </appender> Thanks, Shaul The information contained in this message is proprietary to the sender, protected from disclosure, and may be privileged. The information is intended to be conveyed only to the designated recipient(s) of the message. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, use, distribution or copying of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you.

2 2

Re: [logback-user] Ignoring specific packages?
by Pegram, David 26 Nov '12

26 Nov '12

Thank you for your help Chris! I was able to get the JUL messages bridged to SLF4J and logged in the appropriate logback managed files. However, as a result I'm picking up a lot of "noise" from other packages. I've turned them down using the following configuration options (see below). Can someone tell me if there is a way to exclude them from the two appenders without affecting higher level handlers? For example, I'd like to ignore messages from "org.jboss.*" and let the container continue to handle its own logging. Unfortunately, setting the "org.jboss" level to "OFF" has a side-effect of disabling the container's logging too (server.log). Thank you! - D. Pegram <logger name="javax.enterprise" level="WARN" /> <logger name="org.springframework" level="WARN" /> <logger name="javax.faces" level="INFO" /> <logger name="org.apache" level="INFO" /> <logger name="org.hibernate" level="WARN" /> <logger name="org.primefaces" level="INFO" /> <logger name="ch.qos.logback" level="WARN" /> <logger name="org.jboss" level="INFO" /> <root level="DEBUG"> <appender-ref ref="InfoFileAppender" /> <appender-ref ref="DebugFileAppender" /> </root> From: logback-user-bounces(a)qos.ch [mailto:logback-user-bounces@qos.ch] On Behalf Of Chris Pratt Sent: Tuesday, November 20, 2012 5:00 PM To: logback users list Subject: Re: [logback-user] Logging uncaught exceptions that go to server.log There's an extremely good probability that those statements are being written to the java.util.logging subsystem. If you would like those bridged over to your Logback for processing, look into the SLF4j Bridge Handler (http://www.slf4j.org/api/org/slf4j/bridge/SLF4JBridgeHandler.html) (*Chris*) On Tue, Nov 20, 2012 at 1:40 PM, Pegram, David <dpegram(a)biosignia.com<mailto:dpegram@biosignia.com>> wrote: Greetings! I have a web app built with Maven I've added Logback to handle the logging with two rolling file appenders. Unfortunately, some exceptions (below) still bubble up to the server.log and are not captured in the logback generated files. How can I capture these with logback and keep them out of server.log? 15:46:41,888 SEVERE [javax.enterprise.resource.webcontainer.jsf.context] (http-) JSF1073: javax.faces.event.AbortProcessingException caught during processing of PROCESS_VALIDATIONS 3 : UIComponent-ClientId=templateForm:ddlCarrierView, Message=/foo/bar.xhtml @144,91 valueChangeListener="#{BackingBean.method}": java.lang.NullPointerException 15:46:41,889 SEVERE [javax.enterprise.resource.webcontainer.jsf.context] (http-) /foo/bar.xhtml @144,91 valueChangeListener="#{BackingBean.method}": java.lang.NullPointerException: javax.faces.event.AbortProcessingException: /foo/bar.xhtml @144,91 valueChangeListener="#{BackingBean.method}": java.lang.NullPointerException at javax.faces.event.MethodExpressionValueChangeListener.processValueChange(MethodExpressionValueChangeListener.java:157) [jboss-jsf-api_2.1_spec-2.0.2.Final-redhat-1.jar:2.0.2.Final-redhat-1] ... Caused by: java.lang.NullPointerException at my.app.BackingBean.method(BackingBean.java:298) [classes:] ... Below are the relevant configuration pieces. Thank you for your help! - D. Pegram pom.xml: <dependency> <groupId>ch.qos.logback</groupId> <artifactId>logback-classic</artifactId> <version>1.0.7</version> </dependency> Logback.xml: <?xml version="1.0" ?> <configuration debug="true"> <appender class="ch.qos.logback.core.rolling.RollingFileAppender" name="InfoFileAppender"> <append>true</append> <file>${jboss.server.log.dir}/maApp.log</file> <filter class="ch.qos.logback.classic.filter.ThresholdFilter"> <level>INFO</level> </filter> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <fileNamePattern>${jboss.server.log.dir}/myApp.%d{yyyy-MM-dd}.gz</fileNamePattern> <maxHistory>30</maxHistory> </rollingPolicy> <encoder> <pattern>%date, %level, %logger, Account: %X{accountId} Session: %X{sessionId} %msg %ex%n</pattern> </encoder> </appender> <appender class="ch.qos.logback.core.rolling.RollingFileAppender" name="DebugFileAppender"> <append>true</append> <file>${jboss.server.log.dir}/myApp-debug.log</file> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <fileNamePattern>${jboss.server.log.dir}/myApp-debug.%d{yyyy-MM-dd}.gz</fileNamePattern> <maxHistory>30</maxHistory> </rollingPolicy> <encoder> <pattern> %date, %level, %thread, %logger, %class, %method, %line: Account: %X{accountId} Session: %X{sessionId} %msg %ex%n </pattern> </encoder> </appender> <root> <level value="debug" /> <appender-ref ref="InfoFileAppender" /> <appender-ref ref="DebugFileAppender" /> </root> </configuration> ________________________________ The contents contained herein may contain confidential information. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, printing or action taken on the contents is strictly prohibited. If you have received this email in error, please notify the sender immediately and delete this message. _______________________________________________ Logback-user mailing list Logback-user(a)qos.ch<mailto:Logback-user@qos.ch> http://mailman.qos.ch/mailman/listinfo/logback-user

1 0

Rolling not working from raid10 to raid5
by Krishna Prasad 26 Nov '12

26 Nov '12

Hi all, My log file only rolls when I add a '.gz' (compression) to the filename pattern. Following is the configuration. -------------------------------------------------------------- where LOGS is raid10 & LOGS_OLD is raid5 -------------------------------------------------------------- appender which is not working, <appender name="impression_log" class="ch.qos.logback.core.rolling.RollingFileAppender"> <File>${LOGS}/qreda-push-scheduler/analyticData/pushImpressionLog.log </File> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <FileNamePattern>${LOGS_OLD}/qreda-push-scheduler/pushImpressionLog.%d{yyyy-MM-dd_HH-mm}.log </FileNamePattern> </rollingPolicy> <encoder> <Pattern>%msg%n</Pattern> </encoder> </appender> appender which works fine, (Only difference is, added .gz) <appender name="impression_log" class="ch.qos.logback.core.rolling.RollingFileAppender"> <File>${LOGS}/qreda-push-scheduler/analyticData/pushImpressionLog.log </File> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <FileNamePattern>${LOGS_OLD}/qreda-push-scheduler/pushImpressionLog.%d{yyyy-MM-dd_HH-mm}.log .gz </FileNamePattern> </rollingPolicy> <encoder> <Pattern>%msg%n</Pattern> </encoder> </appender> Is there something that I missed ? -------------------------------------- slf4j.version 1.6.4 | logback.version 1.0.0 | ------------------------------------- Thanks & Regards, Krishnaprasad

1 1