- logback-user - mailman3.qos.ch

Réponse automatique
by johan.bos＠c6.eu 07 Aug '13

07 Aug '13

I will be out of the office till August 20th with limited email access. For a technical request, please send your message to support(a)c6.eu. For other requests, please email contact(a)c6.eu. > From: Xavier Outhier <xouthier(a)yahoo.fr> > Subject: [logback-user] Searching in the archive of logback-user? > Date: Wed, 7 Aug 2013 13:49:41 +0100 (BST)

1 0

How to make RollingFileAppender roll even if no log events
by David Rosenstrauch 02 Aug '13

02 Aug '13

Hi. We're trying to integrate the logback framework into our app, but we're running into an issue with RollingFileAppender. Our app is creating log files. We are then using RollingFileAppender to periodically roll the log file, gzip it, and move it to another directory (where it subsequently gets pushed to another server for processing). This all works fine ... as long as there's logging events happening. However, when there's no log events, the log file never rolls - which prevents it from getting moved to the other directory, and getting pushed to the other server. So in effect, any data in the log file stays there and never gets processed. This takes on particular importance when we want to shut a server down. What should happen is that we stop sending the server traffic, wait till the log file rolls, and then gets pushed to the processing server - after which it's safe to shut the machine down and be assured of no log data loss. But when we stop sending the server traffic, logback stops rolling the log too - resulting in a situation where the log data just sits in the original log file and never gets rolled, pushed, and processed. So there's no safe time to shut the server down without loss of log data. Is there any way out of this situation? I.e., any way to force logback to do actual clock-based rolling, rather than event-based? Thanks, DR

3 2

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

RollingFileAppender overwriting old files
by Sean Rhea 23 Jul '13

23 Jul '13

All, I'm using RollingFileAppender under jetty, and it occasionally seems to overwrite the contents of log files it has rotated in the past. My logback configuration is attached. Also attached is a terminal session in which you can see that the first line of the rotated log files *usually* is from the right timeframe, but occasionally is from a completely different time. For example, the file named jetty/logs/app.2013-07-22-1000.log contains a log message from the 1300 hour. In those cases, the messages that were once in that log file have been overwritten. Also in that terminal session is the contents of /proc/xxx/fd for the jetty process, where you can see that the process is maintaining open file descriptors to past rotated files. That seems like a bug to me. I see this same behavior with both logback versions 0.9.28 and 1.0.13. I'm using jetty 7.3.1.v20110307. I would appreciate any pointers you could give to help me track this down. If it's just a simple misconfiguration on my part, I'd love to know that, too, of course. I've searched for past mentions of this behavior and haven't found one. Apologies if I overlooked any that exist. Thanks, Sean === Configuration === <configuration> <appender name="FILE" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>logs/nmr.log</file> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <fileNamePattern>logs/nmr.%d{yyyy-MM-dd-HH}00.log</fileNamePattern> <maxHistory>672</maxHistory> </rollingPolicy> <encoder> <pattern>%date [%thread] %-5level %msg%n</pattern> </encoder> </appender> <appender name="EMAIL" class="ch.qos.logback.classic.net.SMTPAppender"> <evaluator class="RateLimitingEvaluator" /> <smtpHost>localhost</smtpHost> <to>jetty-errors(a)company.com</to> <from>Jetty Errors <jetty-errors(a)company.com></from> <subject>%mdc{environment} %mdc{shard} error: %msg</subject> <layout class="ch.qos.logback.classic.PatternLayout"> <pattern>Date: %date%n{}Message: %msg%n{}Context: %mdc%n</pattern> </layout> <cyclicBufferTracker class="ch.qos.logback.core.spi.CyclicBufferTrackerImpl"> <bufferSize>1</bufferSize>  </cyclicBufferTracker> </appender> <root level="INFO"> <appender-ref ref="FILE" /> <appender-ref ref="EMAIL" /> </root> </configuration> === Notes from terminal session === user@host:/var/local/webapp$ head -1 jetty/logs/app.2013-07-22-* ==> jetty/logs/app.2013-07-22-0000.log <== 2013-07-22 00:00:06,253 [qtp28715691-220085] INFO ... ==> jetty/logs/app.2013-07-22-0100.log <== 2013-07-22 01:00:04,447 [qtp28715691-220283] INFO ... ==> jetty/logs/app.2013-07-22-0200.log <== 2013-07-22 10:00:04,406 [qtp28715691-221647] INFO ... ==> jetty/logs/app.2013-07-22-0300.log <== 2013-07-22 03:00:00,047 [qtp28715691-220456] INFO ... ==> jetty/logs/app.2013-07-22-0400.log <== 2013-07-22 04:00:00,621 [qtp28715691-220497] INFO ... ==> jetty/logs/app.2013-07-22-0500.log <== 2013-07-22 05:00:03,765 [qtp28715691-220332] INFO ... ==> jetty/logs/app.2013-07-22-0600.log <== 2013-07-22 06:00:02,535 [qtp28715691-220805] INFO ... ==> jetty/logs/app.2013-07-22-0700.log <== 2013-07-22 07:00:02,687 [qtp28715691-221141] INFO ... ==> jetty/logs/app.2013-07-22-0800.log <== 2013-07-22 08:00:00,891 [qtp28715691-220805] INFO ... ==> jetty/logs/app.2013-07-22-0900.log <== 2013-07-22 09:00:00,537 [qtp28715691-221493] INFO ... ==> jetty/logs/app.2013-07-22-1000.log <== 2013-07-22 13:00:00,000 [qtp28715691-222323] INFO ... ==> jetty/logs/app.2013-07-22-1100.log <== 2013-07-22 11:00:02,096 [qtp28715691-221933] INFO ... ==> jetty/logs/app.2013-07-22-1200.log <== 2013-07-22 12:00:00,054 [qtp28715691-222149] INFO ... ==> jetty/logs/app.2013-07-22-1300.log <== 2013-07-22 13:12:57,841 [qtp28715691-222370] INFO ... user@host:/var/local/webapp$ ps auxww | grep -v grep | grep jetty jetty 13570 2.8 1.3 1153892 870036 ? Sl May13 2832:30 /usr/bin/java -Xss1m -Xmx128m -Duser.timezone=America/Los_Angeles -Djetty.port=30800 -jar start.jar user@host:/var/local/webapp$ sudo ls -l /proc/13570/fd | grep 'app\.' l-wx------ 1 jetty jetty 64 Jul 22 14:03 102 -> /var/local/webapp/jetty/logs/app.log l-wx------ 1 jetty jetty 64 Jul 22 14:03 105 -> /var/local/webapp/jetty/logs/app.2013-06-12-1400.log (deleted) l-wx------ 1 jetty jetty 64 Jul 22 14:03 112 -> /var/local/webapp/jetty/logs/app.2013-06-26-1600.log l-wx------ 1 jetty jetty 64 Jul 22 14:03 118 -> /var/local/webapp/jetty/logs/app.2013-07-17-1600.log l-wx------ 1 jetty jetty 64 Jul 22 14:03 122 -> /var/local/webapp/jetty/logs/app.2013-06-11-1100.log (deleted) l-wx------ 1 jetty jetty 64 Jul 22 14:03 130 -> /var/local/webapp/jetty/logs/app.2013-07-22-0200.log l-wx------ 1 jetty jetty 64 Jul 22 14:03 144 -> /var/local/webapp/jetty/logs/app.2013-07-22-1000.log l-wx------ 1 jetty jetty 64 Jul 22 14:03 20 -> /var/local/webapp/jetty/logs/app.2013-07-15-1400.log l-wx------ 1 jetty jetty 64 Jul 22 14:03 4 -> /var/local/webapp/jetty/logs/app.2013-07-22-1300.log l-wx------ 1 jetty jetty 64 Jul 22 14:03 85 -> /var/local/webapp/jetty/logs/app.2013-07-10-1200.log l-wx------ 1 jetty jetty 64 Jul 22 14:03 99 -> /var/local/webapp/jetty/logs/app.2013-07-10-1000.log

2 1

AUTO: Manfred Kuhlmann is out of office. (Rückkehr am 07.08.2013)
by manfred.kuhlmann＠steria-mummert.de 22 Jul '13

22 Jul '13

Ich werde ab dem 20.07.2013 nicht im Büro sein. Ich kehre zurück am 07.08.2013. I will be out of the office starting 20.07.2013. I will be back on 07.08.2013. Ihre Nachricht werde ich nach meiner Rückkehr beantworten. Mit freundlichen Grüßen Manfred Kuhlmann Hinweis: Dies ist eine automatische Antwort auf Ihre Nachricht " [logback-user] RollingFileAppender overwriting old files" gesendet am 22.07.2013 23:23:59. Diese ist die einzige Benachrichtigung, die Sie empfangen werden, während diese Person abwesend ist. Steria Mummert Consulting AG Vorsitzender des Aufsichtsrates: François Enaud - Vorstand: Dr. Fritz Moser Gesellschaftssitz: Hamburg - HR B 61 116 Amtsgericht Hamburg - USt-ID-Nr.: DE118671351 Bitte denken Sie an Ihre Verantwortung gegenüber der Umwelt: Jede ausgedruckte E-Mail verursacht ca. 0,3 Gramm CO2 pro Seite. Diese Nachricht kann vertrauliche Informationen enthalten und ist allein für den Adressaten bestimmt. Wenn Sie nicht der rechtmäßige Empfänger sind, sind der Zugriff, die Weiterleitung, das Kopieren, die Veröffentlichung oder anderweitige Verwendung des Inhalts untersagt. In diesem Fall bitten wir Sie, den Absender unverzüglich zu informieren und diese E-Mail sowie sämtliche Kopien dieser E-Mail zu löschen. Der Inhalt von E-Mails innerhalb des Netzwerks kann überprüft werden, um die Übereinstimmung mit den geltenden Firmenrichtlinien und Vorgehensweisen zu gewährleisten. E-Mails können auf dem Transportweg von Dritten verändert werden, so dass deren Vollständigkeit und Echtheit nicht garantiert werden können. This e-mail communication may contain confidential information and is intended only for the recipient. If you are not the intended recipient you are not allowed to read, copy, distribute, publicize or use the content of this e-mail in any way. Please notify the sender and delete the e-mail and any copies of it. The content of e-mails within our network may be monitored to ensure compliance with company policies and procedures. E-mails can be alterated by third parties in transit. Therefore any e-mail is susceptible to alteration and its integrity cannot be assured.

1 0

Configure RollingFileAppender to keep a back up of Fifty log files in Logback
by Govardhana 18 Jul '13

18 Jul '13

Hi, I have used *RollingFileAppender *in logback Configuration file. My requirement is to keep 50 log files [ maxIndex ]as back up. Please give me some idea on this to fulfill my requirement. Example: myLog.log , myLog.log.1, ........ myLog.log.50 Regards, Reddy -- View this message in context: http://logback.10977.n7.nabble.com/Configure-RollingFileAppender-to-keep-a-… Sent from the Users mailing list archive at Nabble.com.

3 5

class name is displayed incorrectly for java inner classes
by Andrew E. Davidson 17 Jul '13

17 Jul '13

Hi I am using log back-1.0.13. Bellow is the output and sample java code I used to test log back with. noticed that I have an inner class how ever the log output always displays the class name as the outer class. Is there a way to set up log back so that it prints something like outer.inner ??? Also has anyone given any thought to defining an XSD file? This would allow my ice (eclipse) to catch a lot of configuration problems for me. I really appreciate all the hard work everyone has put into this project thanks in advance andy [SLF4JConsoleTest.java] [line 50] [thr main] [class SLF4JConsoleTest] [execute()] Test: INFO level message. [SLF4JConsoleTest.java] [line 53] [thr main] [class SLF4JConsoleTest] [execute()] Test: WARN level message. [SLF4JConsoleTest.java] [line 56] [thr main] [class SLF4JConsoleTest] [execute()] Test: ERROR level message. [SLF4JConsoleTest.java] [line 73] [thr main] [class SLF4JConsoleTest] [execute()] MyInnerClass: INFO level message. [SLF4JConsoleTest.java] [line 76] [thr main] [class SLF4JConsoleTest] [execute()] MyInnerClass: WARN level message. [SLF4JConsoleTest.java] [line 79] [thr main] [class SLF4JConsoleTest] [execute()] MyInnerClass: ERROR level message. <?xml version="1.0" encoding="UTF-8"?> <configuration>  <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender"> <layout class="ch.qos.logback.classic.PatternLayout">  <Pattern>[%15file] [line %4L] [thr %4t] [class %17c{0}] [%method] %m %n</Pattern> </layout> </appender> <root level="INFO"> <appender-ref ref="STDOUT" /> </root> </configuration> public class SLF4JConsoleTest { static final Logger LOG = LoggerFactory.getLogger(SLF4JConsoleTest.class); /** * @param args */ public static void main(String[] args) { SLF4JConsoleTest console = new SLF4JConsoleTest(); console.execute(); } public SLF4JConsoleTest() { } public void execute() { if (LOG.isTraceEnabled()) { LOG.trace("Test: TRACE level message."); } if (LOG.isDebugEnabled()) { LOG.debug("Test: DEBUG level message."); } if (LOG.isInfoEnabled()) { LOG.info("Test: INFO level message."); } if (LOG.isWarnEnabled()) { LOG.warn("Test: WARN level message."); } if (LOG.isErrorEnabled()) { LOG.error("Test: ERROR level message."); } MyInnerClass mic = new MyInnerClass(); mic.execute(); } public class MyInnerClass { public void execute() { if (LOG.isTraceEnabled()) { LOG.trace("MyInnerClass: TRACE level message."); } if (LOG.isDebugEnabled()) { LOG.debug("MyInnerClass: DEBUG level message."); } if (LOG.isInfoEnabled()) { LOG.info("MyInnerClass: INFO level message."); } if (LOG.isWarnEnabled()) { LOG.warn("MyInnerClass: WARN level message."); } if (LOG.isErrorEnabled()) { LOG.error("MyInnerClass: ERROR level message."); } } } }

2 7