July 2013 - 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

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

Logger level from Layout class
by gaston sponer 22 Aug '13

22 Aug '13

Hi, Is there any way to get from MyLayout the logger level? I don't want to do this: package com.render;import org.slf4j.LoggerFactory;import ch.qos.logback.classic.Logger;import ch.qos.logback.classic.spi.ILoggingEvent;import ch.qos.logback.core.LayoutBase; import com.render.domain.Employee; public class MyLayout extends LayoutBase<ILoggingEvent>{ String level= ((Logger)LoggerFactory.getLogger("employee")).getLevel().toString();...... This works well but i don't like to instantiate an object just to get a logger level. This is my xml config file: <configuration><logger name="employee" level="debug"/> <appender name="CONSOLE" class="ch.qos.logback.core.ConsoleAppender"> <encoder class="ch.qos.logback.core.encoder.LayoutWrappingEncoder"> <layout class="com.render.MyLayout" > </layout> </encoder> </appender> <root level="off"> <appender-ref ref="CONSOLE" /> </root></configuration> Thanks,Gastón.

4 9

DBAppender and markers
by Leonardo Souza 21 Aug '13

21 Aug '13

Hi, We have a system with a lot of log statements using markers, this.logger.info(this.marker, "ex fvmo dare lvcem"); We are planning to store the logs in a database using DBAppender but ther marker do not have a column, only appears in the formatted_message field. We will query this database filtering by the markers, a sql like query is not a desirable solution. Anyone has a better idea instead of creating a custom appender? thanks .. -- Leonardo S Souza

3 12

Beagle not working in Kepler?
by Thom DeCarlo 08 Aug '13

08 Aug '13

Hi, I downloaded the newest Eclipse release today and found that the logback-beagle plugin no longer works. Are there plans to migrate to Kepler, or isn't anyone using Beagle anymore? Thanks! Sent from my iPad and at the mercy of Autocorrect

2 1

How to know the filename used by the appender of a given logger
by Ulrich 01 Aug '13

01 Aug '13

Within my application I would like to know the filename used by it's logger. I've asked this question before but didn't get an answer. So I will give it another try. I've browsed through the Javadoc of the classes and interfaces where I thought by their name they should be able to provide this piece of information (LoggerContext and Appender to name two of them), but wasn't lucky. Can anyone help here? Ulrich

2 4

Why is RollingFileAppender so noisy?
by cowwoc 31 Jul '13

31 Jul '13

Hi, I am trying to configure logback to launch silently (without outputting verbose information about its configuration). When my configuration file contains: <appender name="file" class="ch.qos.logback.core.FileAppender"> <file>../../../foo.log</file> <append>false</append> <encoder> <pattern>%d{HH:mm:ss.SSS} [%thread] %-5level %class{}.%method\(\) - %msg%n</pattern> </encoder> </appender> I don't get any output at startup (good!). When I replace this with: <appender name="file" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>../../../foo.log</file> <append>false</append> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <fileNamePattern>../../../foo.%d{yyyy-MM-dd}.%i.log</fileNamePattern> <timeBasedFileNamingAndTriggeringPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP"> <maxFileSize>100MB</maxFileSize> </timeBasedFileNamingAndTriggeringPolicy> </rollingPolicy> <encoder> <pattern>%d{HH:mm:ss.SSS} [%thread] %-5level %class{}.%method\(\) - %msg%n</pattern> </encoder> </appender> I suddenly get this output: 01:17:17,188 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback.groovy] 01:17:17,189 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback-test.xml] 01:17:17,189 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Found resource [logback.xml] at [file:/C:/Users/Gili/Documents/foo.service/web/target/classes/logback.xml] 01:17:17,379 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - debug attribute not set 01:17:17,391 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.ConsoleAppender] 01:17:17,395 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [stdout] 01:17:17,425 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property 01:17:17,482 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.rolling.RollingFileAppender] 01:17:17,484 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [file] 01:17:17,519 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy - No compression will be used 01:17:17,521 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy - Will use the pattern ../../../foo.%d{yyyy-MM-dd}.%i.log for the active file 01:17:17,523 |-INFO in ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP@1ea40b04 - The date pattern is 'yyyy-MM-dd' from file name pattern '../../../foo.%d{yyyy-MM-dd}.%i.log'. 01:17:17,523 |-INFO in ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP@1ea40b04 - Roll-over at midnight. 01:17:17,526 |-INFO in ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP@1ea40b04 - Setting initial period to Wed Jul 31 01:17:17 EDT 2013 01:17:17,530 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property 01:17:17,531 |-WARN in ch.qos.logback.core.rolling.RollingFileAppender[file] - Append mode is mandatory for RollingFileAppender 01:17:17,533 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[file] - Active log file name: ../../../foo.log 01:17:17,533 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[file] - File property is set to [../../../foo.log] 01:17:17,535 |-INFO in ch.qos.logback.classic.joran.action.LoggerContextListenerAction - Adding LoggerContextListener of type [ch.qos.logback.classic.jul.LevelChangePropagator] to the object stack 01:17:17,537 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@23cf4353 - Propagating DEBUG level on Logger[ROOT] onto the JUL framework 01:17:17,542 |-INFO in ch.qos.logback.classic.joran.action.LoggerContextListenerAction - Starting LoggerContextListener 01:17:17,542 |-INFO in ch.qos.logback.classic.joran.action.RootLoggerAction - Setting level of ROOT logger to TRACE 01:17:17,542 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@23cf4353 - Propagating TRACE level on Logger[ROOT] onto the JUL framework 01:17:17,542 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [stdout] to Logger[ROOT] 01:17:17,543 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [file] to Logger[ROOT] 01:17:17,543 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [com.foo.Preconditions] to INFO 01:17:17,543 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@23cf4353 - Propagating INFO level on Logger[com.foo.Preconditions] onto the JUL framework 01:17:17,543 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [com.foo.ToJsonString] to INFO 01:17:17,543 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@23cf4353 - Propagating INFO level on Logger[com.foo.ToJsonString] onto the JUL framework 01:17:17,544 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [com.foo.sql.Session] to INFO 01:17:17,544 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@23cf4353 - Propagating INFO level on Logger[com.foo.sql.Session] onto the JUL framework 01:17:17,544 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [com.google.inject.servlet.GuiceFilter] to OFF 01:17:17,544 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@23cf4353 - Propagating OFF level on Logger[com.google.inject.servlet.GuiceFilter] onto the JUL framework 01:17:17,544 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [com.sun.jersey.server.impl.ejb.EJBComponentProviderFactoryInitilizer] to WARN 01:17:17,544 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@23cf4353 - Propagating WARN level on Logger[com.sun.jersey.server.impl.ejb.EJBComponentProviderFactoryInitilizer] onto the JUL framework 01:17:17,544 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [com.sun.jersey.server.impl.managedbeans.ManagedBeanComponentProviderFactoryInitilizer] to WARN 01:17:17,544 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@23cf4353 - Propagating WARN level on Logger[com.sun.jersey.server.impl.managedbeans.ManagedBeanComponentProviderFactoryInitilizer] onto the JUL framework 01:17:17,544 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [com.sun.jersey.server.impl.cdi.CDIComponentProviderFactoryInitializer] to WARN 01:17:17,544 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@23cf4353 - Propagating WARN level on Logger[com.sun.jersey.server.impl.cdi.CDIComponentProviderFactoryInitializer] onto the JUL framework 01:17:17,544 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting additivity of logger [com.sun.jersey.api.container.filter.LoggingFilter] to false 01:17:17,544 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [file] to Logger[com.sun.jersey.api.container.filter.LoggingFilter] 01:17:17,544 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [org.glassfish.grizzly.] to WARN 01:17:17,544 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@23cf4353 - Propagating WARN level on Logger[org.glassfish.grizzly.] onto the JUL framework 01:17:17,545 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - End of configuration. 01:17:17,545 |-INFO in ch.qos.logback.classic.joran.JoranConfigurator@7c4d1082 - Registering current configuration as safe fallback point Any idea why RollingFileAppender is producing all this noise? Thanks, Gili

3 2

Curly Braces
by gaston sponer 29 Jul '13

29 Jul '13

Hi, i'm doing: logger.debug("{}", employee); And the log resutl is: DEBUG [main] Company_Module - {}DEBUG Level - Personal: name=John, age=36, id=3124362] Is there any way to remove curly braces before DEBUG word from this log? I would like to have: DEBUG [main] Company_Module - DEBUG Level - Personal: name=John, age=36, id=3124362] Thanks ¡

3 3

Object domain from layouts
by gaston sponer 25 Jul '13

25 Jul '13

i'm working with Logback and i'm sending this concern to you because i can't find any solution for my problem. What i need to know if i can manipulate my objects in the layouts. Ex.: -------------------------------------------------------------------------------- public RenderTest class{ static final Logger logger = LoggerFactory.getLogger("Fred"); public static void main(String...args){ getRenderTest().logging(); } static RenderTest getRenderTest(){ return new RenderTest(); } private void logging(){ xmlFileConfiguration(); Employee employee = getSampleEmployee(); logger.debug("Employee {}", new EmployeeRenderer().getLogMessage(employee, logger)); } private Employee getSampleEmployee(){ Person person = new Person("John", 36, 3124362); Address address = new Address("Columbus", 756, "Cordoba", "X5003","Cordoba"); Salary salary = new Salary(18565.54, "ARS"); Employee employee = new Employee("AA", 324214231, salary, person,address); return employee; } } -------------------------------------------------------------------------------- MyLayout: public class EmployeeLayout extends LayoutBase<ILoggingEvent>{ Context logger = getContext(); public String doLayout(ILoggingEvent event) { StringBuffer sbuf = new StringBuffer(128); sbuf.append(event.getLevel()); sbuf.append(" ["); sbuf.append(event.getThreadName());// sbuf.append(employee.getName()); // How can i get employee object from here? sbuf.append("] "); sbuf.append(event.getLoggerName()); sbuf.append(" - "); sbuf.append(event.getFormattedMessage()); //so far so good, but now I need to get my employee object to render some important information from it. // I tried with event.getArgumentArray()[0], but I can't take for instance a employee.getCompany() return sbuf.toString(); } } -------------------------------------------------------------------------------- My config file: <configuration> <logger name="Fred" level="debug"/> <appender name="CONSOLE" class="ch.qos.logback.core.ConsoleAppender"> <encoder class="ch.qos.logback.core.encoder.LayoutWrappingEncoder"> <layout class="com.render.EmployeeLayout" /> </encoder> --> </appender> <root level="off"> <appender-ref ref="CONSOLE" /> </root> </configuration> -------------------------------------------------------------------------------- I would like to do something like this from layout to decide what objects will show in the log: sbuf.append(employee.getName()); sbuf.append(employee.getCompany()); Is there any way to do that? Do you see any drawbacks to do that? Thanks a lot,

2 3