- logback-user - mailman3.qos.ch

logback-android problem with exception logging and logcat
by Duarte Silva 07 Dec '12

07 Dec '12

Hi, I have searched for this problem but haven't been successful in my quest for a solution. I have attached the configuration used as well as the result in the logcat output using logback and the Android Log. The logging call is the following (where LOGGER as been obtained by using the LoggerFactory and the configuration is in the application manifest): if (LOGGER.isWarnEnabled()) { LOGGER.warn("Failed to use the mark/reset, will retrieve the data again", exception); } As you may notice the output is all crapped out. What am I doing wrong? Best regards, Duarte Silva

2 2

Release of logback version 1.0.8
by ceki 04 Dec '12

04 Dec '12

Hello all, I am happy to announce the release of logback version 1.0.8. It should hit the Maven central repository within the next 2 hours. Please refer to the news page for precise details of this release. http://logback.qos.ch/news.html You can download logback, including full source code, class files and documentation on our download page, shown below. http://logback.qos.ch/download.html 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 You may also receive announcements via twitter via the following account: https://twitter.com/qos_ch Enjoy, -- Ceki 65% of statistics are made up on the spot

1 0

Logback, OSGi and DynamicClassLoadingException
by Benoît Thiébault 03 Dec '12

03 Dec '12

Hi everyone, I am migrating an OSGi-based application from System.out.println to slf4j / logback and I am having some problems. I have provided logback with a configuration file via the "logback.configurationFile" and it works very well. In this configuration file, I have defined a specific appender that I have developed, but logback fails to instantiate it (cf. stacktrace below). This is not really a surprise: each OSGi bundle has its own classloader. My org.test.LogConsole is in its own bundle and thus logback classloader cannot find it. One solution is to declare my org.test.LogConsole bundle as a fragment of logback. The fragment bundle is not a bundle per se and shares its classloader with the host bundle. This is however very constraining in term of bundle resolution / starting order as the fragment bundle has to be installed before the host. Isn't there another way (such as LogBack.Configuration.addClassloader()) to indicate logback classic where to search for my org.test.LogConsole class ? Kind regards, Ben 10:58:48,848 |-ERROR in ch.qos.logback.core.joran.action.AppenderAction - Could not create an Appender of type [org.test.LogConsole]. ch.qos.logback.core.util.DynamicClassLoadingException: Failed to instantiate type org.test.LogConsole at ch.qos.logback.core.util.DynamicClassLoadingException: Failed to instantiate type org.test.LogConsole at at ch.qos.logback.core.util.OptionHelper.instantiateByClassNameAndParameter(OptionHelper.java:74) at at ch.qos.logback.core.util.OptionHelper.instantiateByClassName(OptionHelper.java:49) at at ch.qos.logback.core.util.OptionHelper.instantiateByClassName(OptionHelper.java:35) at at ch.qos.logback.core.joran.action.AppenderAction.begin(AppenderAction.java:54) at at ch.qos.logback.core.joran.spi.Interpreter.callBeginAction(Interpreter.java:276) at at ch.qos.logback.core.joran.spi.Interpreter.startElement(Interpreter.java:148) at at ch.qos.logback.core.joran.spi.Interpreter.startElement(Interpreter.java:130) at at ch.qos.logback.core.joran.spi.EventPlayer.play(EventPlayer.java:50) at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:157) at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:143) at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:106) at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:56) at at ch.qos.logback.classic.util.ContextInitializer.configureByResource(ContextInitializer.java:75) at at ch.qos.logback.classic.util.ContextInitializer.autoConfig(ContextInitializer.java:148) at at org.slf4j.impl.StaticLoggerBinder.init(StaticLoggerBinder.java:84) at at org.slf4j.impl.StaticLoggerBinder.<clinit>(StaticLoggerBinder.java:54) at at org.slf4j.LoggerFactory.bind(LoggerFactory.java:128) at at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:107) at at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:295) at at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:269)

1 0

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

How to change the underlying buffer size of BufferedOutputStream used by logback's FileAppender?
by Tim Shi 23 Nov '12

23 Nov '12

Hi, We are using logback as our logging framework. We noticed that the FileAppender uses ResilientFileOutputStream which is backed by an BufferedOutputStream. We are wondering if there's a way to configure the buffer size of this BufferedOutputStream instance so that we can tune the performance of logback. Thanks, Tim

1 0

Logging uncaught exceptions that go to server.log
by Pegram, David 20 Nov '12

20 Nov '12

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.

2 1