- logback-user - mailman3.qos.ch

logback issue
by Yaer Dili 02 Nov '19

02 Nov '19

hi there, we are using logback in our spring boot application and all our logback related configuration is in the `logback-spring.xml` file ad we configure `springProfile` for different environments in the xml file like this <springProfile name="local,dev"> <root level="DEBUG"> <appender-ref ref="console"/> </root> </springProfile> after this configuration if we want to add other environment property, it must be added to this `springProfile` first otherwise our application failed to start with newly added property file. for example if I just add a new property file called `application-uat.yml` and directly start the application with this property file, our application failed to start. for fixing this I need to add this property name in the `SpringProfile` configuration like this `<springProfile name="local,dev,uat" >` we think logback rather than directly block our app start should have a default value for newly added property file, do you have anything to share with us? thank you regards, yaer

1 0

About FileAppender in Logback
by Hasan.Birol＠ing.com.tr 01 Nov '19

01 Nov '19

Dear Logback Team; Have a problem with logback . Have a logback.xml file find it below. Each thread has a single log file. However, cant recognize file is done or thread is done with looking the file. File is not locked or something (tried to lock the file by extending fileappender but cant succeed) . I don't would like to write a code to get content of file which I mean, dont wanna write a some symbol to find out file is done. I also used, triggeringPolicy cant succeed.. <appender name="SIFT" class="XXXXX.SiftingAppender"> <discriminator> <key>fileLocation</key> <defaultValue>${user.home}\start.log</defaultValue> </discriminator> <sift> <appender name="FILE-${fileLocation}" class="ch.qos.logback.core.FileAppender"> <file>${fileLocation}</file> <append>false</append> <encoder> <pattern>%msg%n</pattern> </encoder> </appender> </sift> </appender> I just would like to change extension when thread is done .log to .xml, or lock the file while end of the thread, or move the file end of the thread. Many many thanks. Have a nice day, Hasan Birol Yaz?l?m Dan??man? - Software Consultant Yaz?l?m Geli?tirme Sistemleri ve Platform Uygulamalar? B?l?m? - Software Development Frameworks and Platform Applications T: E: Hasan.Birol(a)ing.com.tr [http://image.ing.com.tr/EmailBanner/ING_LOGO_89x42px-02.png]<https://www.ing.com.tr> Kisiye ozel bu mesaj ve icerigindeki bilgiler gizlidir. ING bu mesajin icerigi ve ekleri ile ilgili olarak hukuksal hicbir sorumluluk kabul etmez.Yetkili alicilardan biri degilseniz, bu mesajin herhangi bir sekilde ifsa edilmesi, kullanilmasi, kopyalanmasi,yayilmasi veya mesajda yeralan hususlarla ilgili olarak herhangi bir islem yapilmasinin kesinlikle yasak oldugunu bildiririz.Boyle bir durumda lutfen hemen mesajin gondericisini bilgilendiriniz ve mesaji sisteminizden siliniz.Internet ortaminda gonderilen e-posta mesajlarindaki hata ve/veya eksikliklerden veya viruslerden dolayi mesajin gondericisi herhangi bir sorumluluk kabul etmemektedir.Tesekkur ederiz. The information contained in this communication may contain confidential or legally privileged information. ING doesn't accept any legal responsibility for the contents and attachments of this message. If you are not the intended recipient you are hereby notified that any disclosure, use, copying, distribution or taking any action in reliance on the contents of this information is strictly prohibited. If you have received this communication in error, please notify the sender immediately by responding to this e-mail and then delete it from your system. The sender does not accept any liability for any errors or omissions or any viruses in the context of this message which arise as a result of internet transmission. Thank you.

2 2

Appending an hourly log line when idle
by Mat Schaffer 01 Nov '19

01 Nov '19

Hello all, I have a service which sits idle sometimes for days and doesn't log anything. This sometimes creates confusion that the process (or log collection) isn't working, but it actually just doesn't have work to do. Is there any logback feature that I could leverage to send an hourly "MARK" if nothing has gone through the appender? Or should I just add something in the app itself? Thanks in advance! -Mat

2 2

SMTP Appender always shows DEBUG info
by Richmond, Thomas 31 Oct '19

31 Oct '19

Using 1.3.0-alpha5 (which is, admittedly, Alpha), SMTPAppenderBase.java calls session.setDebug(true) at line 124, which causes a lot of SMTP info to spam the console. This is probably a merge error made during the checkin of c01fde48c1b3ebb9a5066f6300fcf81be1e0965b. But if it isn't, I don't think this should be the default behavior because: 1. The next line is "if (session == null)", meaning that session can be null here, meaning that session.setDebug(...) can NPE. 2. I don't want debug info spammed to the console. If this is desired behavior, can I suggest passing a custom output stream to session that passes logger info to the logger in a way that I can squelch using regular logger configuration, for example as shown in Karl Richter's answer here: https://stackoverflow.com/questions/6995946/log4j-how-do-i-redirect-an-outp… Thanks for all the good work, I hope you find this helpful. Tom ________________________________ Please be advised that this email may contain confidential information. If you are not the intended recipient, please notify us by email by replying to the sender and delete this message. The sender disclaims that the content of this email constitutes an offer to enter into, or the acceptance of, any agreement; provided that the foregoing does not invalidate the binding effect of any digital or other electronic reproduction of a manual signature that is included in any attachment.

2 1

How to output short exception when Marker is present, but full otherwise?
by te＠spudsoft.co.uk 23 Oct '19

23 Oct '19

Hi, I want this: logger.debug("Test logging: ", new IllegalStateException("Wibble")); to give me a full stack trace, and this: logger.debug(MarkerFactory.getMarker("MINIMAL_EXCEPTION"), "Test logging: ", new IllegalStateException("Wibble")); to just output the class and message. I don't have Janino, and I'm trying to keep it all as small as possible (also not sure I could pay the price of expression evaluation for each message). The closest I've got is this: <evaluator name="DISPLAY_EX_EVAL" class="ch.qos.logback.classic.boolex.OnMarkerEvaluator"> <marker>MINIMAL_EXCEPTION</marker> </evaluator> <appender name="STDOUTPUT" class="ch.qos.logback.core.ConsoleAppender"> <encoder> <charset>UTF-8</charset> <pattern>%d{HH:mm:ss.SSS} [%thread] %-5level %logger{36} %line - %msg%ex{full, DISPLAY_EX_EVAL}%n</pattern> </encoder> </appender> <contextListener class="ch.qos.logback.classic.jul.LevelChangePropagator" /> But that doesn't output exception at all when the Marker is present. Is there any way to get what I want without a more complex expression? Thanks. Jim

1 0

Re: [logback-user] About FileAppender in Logback
by Hasan.Birol＠ing.com.tr 18 Oct '19

18 Oct '19

Added to mailing list. From: Hasan Birol [Yazilim Gelistirme Sistemleri ve Platform Uygulamalari Bolumu] Sent: Friday, October 18, 2019 2:00 PM To: 'logback-user(a)qos.ch' <logback-user(a)qos.ch> Cc: Bilgehan Yildiz [Yazilim Gelistirme Sistemleri ve Platform Uygulamalari Bolumu] <Bilgehan.Yildiz(a)ing.com.tr>; Rafet Cambaz [Yazilim Gelistirme Sistemleri ve Platform Uygulamalari Bolumu] <Rafet.Cambaz(a)ing.com.tr> Subject: About FileAppender in Logback Dear Logback Team; Have a problem with logback . Have a logback.xml file find it below. Each thread has a single log file. However, cant recognize file is done or thread is done with looking the file. File is not locked or something (tried to lock the file by extending fileappender but cant succeed) . I don't would like to write a code to get content of file which I mean, dont wanna write a some symbol to find out file is done. I have been searching it for 3 months :) I hope you help me. Many thanks. <appender name="SIFT" class="XXXXX.SiftingAppender"> <discriminator> <key>fileLocation</key> <defaultValue>${user.home}\start.log</defaultValue> </discriminator> <sift> <appender name="FILE-${fileLocation}" class="ch.qos.logback.core.FileAppender"> <file>${fileLocation}</file> <append>false</append> <encoder> <pattern>%msg%n</pattern> </encoder> </appender> </sift> </appender> I just would like to change extension when thread is done .log to .xml, or lock the file while end of the thread, or move the file end of the thread. Many many thanks. Have a nice day, Q on StackOverFlow : https://stackoverflow.com/questions/58434943/why-fileappender-is-not-lockin… Hasan Kisiye ozel bu mesaj ve icerigindeki bilgiler gizlidir. ING bu mesajin icerigi ve ekleri ile ilgili olarak hukuksal hicbir sorumluluk kabul etmez.Yetkili alicilardan biri degilseniz, bu mesajin herhangi bir sekilde ifsa edilmesi, kullanilmasi, kopyalanmasi,yayilmasi veya mesajda yeralan hususlarla ilgili olarak herhangi bir islem yapilmasinin kesinlikle yasak oldugunu bildiririz.Boyle bir durumda lutfen hemen mesajin gondericisini bilgilendiriniz ve mesaji sisteminizden siliniz.Internet ortaminda gonderilen e-posta mesajlarindaki hata ve/veya eksikliklerden veya viruslerden dolayi mesajin gondericisi herhangi bir sorumluluk kabul etmemektedir.Tesekkur ederiz. The information contained in this communication may contain confidential or legally privileged information. ING doesn't accept any legal responsibility for the contents and attachments of this message. If you are not the intended recipient you are hereby notified that any disclosure, use, copying, distribution or taking any action in reliance on the contents of this information is strictly prohibited. If you have received this communication in error, please notify the sender immediately by responding to this e-mail and then delete it from your system. The sender does not accept any liability for any errors or omissions or any viruses in the context of this message which arise as a result of internet transmission. Thank you.

1 0

Release of logback version 1.3.0-alpha5
by Ceki 12 Oct '19

12 Oct '19

Hello all, I am happy to announce the release of logback version 1.3.0-alpha5. This version directly supports the fluent-API introduced in SLF4J 2.0.x. It also supports Jigsaw/Java9 modularization. Joran, logback's configuration system, has been rewritten to use an internal representation model which can be processed separately. Given the breadth of the changes, support for SiftingAppender and Groovy configuration have been dropped temporarily. No new features are available in this version. Future releases will gradually introduce new features made possible by Joran representation model. The 1.3.x series requires Java 8 at runtime. If you wish to build logback from source, you will need Java 9. Please refer to the news page for precise details. http://logback.qos.ch/news.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 by following: https://twitter.com/qos_ch Enjoy, -- Ceki Gülcü

1 0

vjdbc.jar Disables Logback?
by Scott Dudley 11 Oct '19

11 Oct '19

I recently attempted to reintroduce vjdbc.jar (http://vjdbc.sourceforge.net/) to my project only to discover that on doing so, logback (slf4j) is disabled and all logging goes to stdout. Following are the applicable jars in my CLASSPATH: jcl-over-slf4j-1.6.1.jar jul-to-slf4j-1.7.24.jar log4j-over-slf4j-1.6.1.jar logback-access-1.0.13.jar logback-classic-1.0.13.jar logback-core-1.0.13.jar slf4j-api-1.6.1.jar vjdbc.jar The MANIFEST.MF in vjdbc.jar contains no classpath info nor does the jar contain a logback.xml, etc. How could introduction of this jar to my classpath disable logback altogether? Thanks. Scott Dudley -------------------------------------------------------------------------------------------------------------------------------------------------- This message is for the designated recipient(s) only and may contain privileged, proprietary, and/or confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited. Any views or opinions expressed are solely those of the author and do not necessarily represent those of MDSL. --------------------------------------------------------------------------------------------------------------------------------------------------

1 0

Multiple FileAppenders writing to single file no longer working in Logback 1.2.3
by John Morton 24 Sep '19

24 Sep '19

Hello there Logback users. An application I’m responsible uses logback for its internal logging. It logs to various files at various levels. I’ve extended it successfully to reformat certain log messages and save them into a new log called “combined-audit.log”. This is all within a single JVM, logging to a file on a local filesystem. The reason for the three loggers/appenders is that I want to log from three different packages, at different levels, filter each differently, and encode each differently. This is all necessary because I cannot make changes to the app itself, so I’m trying to use Logback to accomplish my needs. The below configuration works in Logback 1.1.3 and not in Logback 1.2.3. In Logback 1.2.3, only messages from one of the three loggers are logged to the single file. When I change the file name to three different files, messages from each logger are in each file. I read through release notes from 1.1.3 to 1.2.3 and nothing jumped out at me as having the potential to change this behavior. Is this a supported configuration in 1.2.3? Does anyone have any ideas for how to accomplish the objective?  <appender name="COMBINED_AUDIT" class="ch.qos.logback.core.FileAppender"> <File>${logging.directory}/combined-audit.log</File> <encoder class="ch.qos.logback.classic.encoder.PatternLayoutEncoder"> <charset>UTF-8</charset> <Pattern>%date{ISO8601}|%mdc{m.remote_addr}|%mdc{m.jsessionid}||%msg%n</Pattern> </encoder> </appender> <logger name="j.k.l" level="ALL" additivity="false"> <appender-ref ref="COMBINED_AUDIT"/> </logger>  <appender name="COMBINED_LDAP" class="ch.qos.logback.core.FileAppender"> <File>${logging.directory}/combined-audit.log</File> <encoder class="ch.qos.logback.classic.encoder.PatternLayoutEncoder"> <charset>UTF-8</charset> <Pattern>%date{ISO8601}|%mdc{m.remote_addr}|%mdc{m.jsessionid}|%replace(%replace(%replace(%msg){'^.*resultCode=',''}){',.*identifier=','|'}){', context=.*$',''}|LDAP|||%n</Pattern> </encoder> <filter class="ch.qos.logback.core.filter.EvaluatorFilter"> <evaluator> <expression>return message.contains("authenticate response=");</expression> </evaluator> <OnMatch>ACCEPT</OnMatch> <OnMismatch>DENY</OnMismatch> </filter> </appender> <logger name="a.b.c.d" level="DEBUG" additivity="false"> <appender-ref ref="COMBINED_LDAP"/> </logger>  <appender name="COMBINED_INVALID_USERNAME" class="ch.qos.logback.core.FileAppender"> <File>${logging.directory}/combined-audit.log</File> <encoder class="ch.qos.logback.classic.encoder.PatternLayoutEncoder"> <charset>UTF-8</charset> <Pattern>%date{ISO8601}|%mdc{m.remote_addr}|%mdc{m.jsessionid}|INVALID_USERNAME||LDAP|||%n</Pattern> </encoder> <filter class="ch.qos.logback.core.filter.EvaluatorFilter"> <evaluator> <expression>return message.contains("failed using filter=");</expression> </evaluator> <OnMatch>ACCEPT</OnMatch> <OnMismatch>DENY</OnMismatch> </filter> </appender> <logger name="v.w.x.y.z" level="INFO" additivity="false"> <appender-ref ref="COMBINED_INVALID_USERNAME"/> </logger>

3 4

config question (why is debug on, and why is my filter not filtering?)
by Mike Wertheim 20 Sep '19

20 Sep '19

I'm maintaining a Java application that's using logback1.2.2. Someone who isn't around anymore set up the logback configuration, and I'm having some trouble understanding it. I am trying to add a filter. The behavior I'm seeing is that the filter works fine on lines that are logged at the INFO level, but the filter is not filtering lines that are logged at the DEBUG level. (So the INFO lines are removed correctly, but the DEBUG lines are still being logged.) Furthermore, I'm realizing that I don't actually understand why any of the DEBUG logging (regardless of the filter) is happening at all. DEBUG logging is working, and I want DEBUG logging to be working, but I'm not understanding why it's working. The reason I was thinking that it wouldn't be working is that the logback.xml adds the file appender to a root node that has level=INFO, so I was expecting to only see INFO logging and not DEBUG logging. Here is the logback.xml (including the filter that I added to both of the appenders)... <configuration debug="true"> <logger name="com.mycompany" level="debug"/> <logger name="com.mycompany.app.server.config.AccessLogHandler" level="INFO" /> <logger name="org.hibernate" level="info"/> <logger name="org.springframework" level="info"/> <logger name="org.apache" level="info"/> <jmxConfigurator /> <contextListener class="ch.qos.logback.classic.jul.LevelChangePropagator"/> <appender name="CONSOLE" class="ch.qos.logback.core.ConsoleAppender"> <encoder> <pattern>%date $%thread$ %-5level [%logger{40}] %message%n</pattern> </encoder> <filter class="ch.qos.logback.core.filter.EvaluatorFilter"> <evaluator> <expression>return message.contains("UserInfoEntry");</expression> </evaluator> <OnMismatch>NEUTRAL</OnMismatch> <OnMatch>DENY</OnMatch> </filter> </appender> <property name="LOG_PATH" value="var/log"/> <appender name="FILE" class="ch.qos.logback.core.rolling.RollingFileAppender"> <filter class="ch.qos.logback.core.filter.EvaluatorFilter"> <evaluator> <expression>return message.contains("UserInfoEntry");</expression> </evaluator> <OnMismatch>NEUTRAL</OnMismatch> <OnMatch>DENY</OnMatch> </filter> <file>${LOG_PATH}/app.log</file> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">  <fileNamePattern>${LOG_PATH}/app_%d{yyyy-MM-dd}.%i.log</fileNamePattern> <timeBasedFileNamingAndTriggeringPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP"> <maxFileSize>5MB</maxFileSize> </timeBasedFileNamingAndTriggeringPolicy>  <maxHistory>30</maxHistory> </rollingPolicy> <encoder> <charset>UTF-8</charset> <pattern>%date [%thread] %-5level %logger{36} %X - %msg%n</pattern> </encoder> </appender> <root level="INFO"> <appender-ref ref="FILE"/> </root> </configuration> Here is the output from logback (since i have debug=true on)... 20:50:55,109 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback-test.xml] 20:50:55,109 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback.groovy] 20:50:55,109 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Found resource [logback.xml] at [file:/opt/app/app-server-4.3.1-SNAPSHOT/etc/logback.xml] 20:50:55,224 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [com.mycompany] to DEBUG 20:50:55,224 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [org.springframework.security] to INFO 20:50:55,224 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [com.mycompany.app.server.config.AccessLogHandler] to INFO 20:50:55,224 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [org.hibernate] to INFO 20:50:55,224 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [org.springframework] to INFO 20:50:55,224 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [com.zaxxer.hikari.pool.PoolBase] to WARN 20:50:55,225 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [org.springframework.aop.framework.CglibAopProxy] to ERROR 20:50:55,225 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [org.eclipse.jetty.util.log] to WARN 20:50:55,225 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [com.netflix.hystrix] to WARN 20:50:55,225 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [org.apache] to INFO 20:50:55,225 |-INFO in ch.qos.logback.classic.joran.action.JMXConfiguratorAction - begin 20:50:55,291 |-INFO in ch.qos.logback.classic.joran.action.LoggerContextListenerAction - Adding LoggerContextListener of type [ch.qos.logback.classic.jul.LevelChangePropagator] to the object stack 20:50:55,293 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@5e853265 - Propagating DEBUG level on Logger[ROOT] onto the JUL framework 20:50:55,293 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@5e853265 - Propagating WARN level on Logger[com.netflix.hystrix] onto the JUL framework 20:50:55,293 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@5e853265 - Propagating DEBUG level on Logger[com.mycompany] onto the JUL framework 20:50:55,293 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@5e853265 - Propagating INFO level on Logger[com.mycompany.app.server.config.AccessLogHandler] onto the JUL framework 20:50:55,293 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@5e853265 - Propagating WARN level on Logger[com.zaxxer.hikari.pool.PoolBase] onto the JUL framework 20:50:55,293 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@5e853265 - Propagating INFO level on Logger[org.apache] onto the JUL framework 20:50:55,294 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@5e853265 - Propagating WARN level on Logger[org.eclipse.jetty.util.log] onto the JUL framework 20:50:55,294 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@5e853265 - Propagating INFO level on Logger[org.hibernate] onto the JUL framework 20:50:55,294 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@5e853265 - Propagating INFO level on Logger[org.springframework] onto the JUL framework 20:50:55,294 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@5e853265 - Propagating ERROR level on Logger[org.springframework.aop.framework.CglibAopProxy] onto the JUL framework 20:50:55,294 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@5e853265 - Propagating INFO level on Logger[org.springframework.security] onto the JUL framework 20:50:55,294 |-INFO in ch.qos.logback.classic.joran.action.LoggerContextListenerAction - Starting LoggerContextListener 20:50:55,294 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.ConsoleAppender] 20:50:55,298 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [CONSOLE] 20:50:55,303 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property 20:50:55,336 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default type [ch.qos.logback.classic.boolex.JaninoEventEvaluator] for [evaluator] property 20:50:55,582 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.rolling.RollingFileAppender] 20:50:55,585 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [FILE] 20:50:55,586 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default type [ch.qos.logback.classic.boolex.JaninoEventEvaluator] for [evaluator] property 20:50:55,603 |-INFO in ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP@419c5f1a - The date pattern is 'yyyy-MM-dd' from file name pattern 'var/log/app_%d{yyyy-MM-dd}.%i.log'. 20:50:55,603 |-INFO in ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP@419c5f1a - Roll-over at midnight. 20:50:55,607 |-INFO in ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP@419c5f1a - Setting initial period to Thu Sep 19 20:50:54 UTC 2019 20:50:55,607 |-WARN in ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP@419c5f1a - SizeAndTimeBasedFNATP is deprecated. Use SizeAndTimeBasedRollingPolicy instead 20:50:55,608 |-WARN in ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP@419c5f1a - For more information see http://logback.qos.ch/manual/appenders.html#SizeAndTimeBasedRollingPolicy 20:50:55,611 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property 20:50:55,613 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[FILE] - Active log file name: var/log/app.log 20:50:55,613 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[FILE] - File property is set to [var/log/app.log] 20:50:55,615 |-INFO in ch.qos.logback.classic.joran.action.RootLoggerAction - Setting level of ROOT logger to INFO 20:50:55,615 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@5e853265 - Propagating INFO level on Logger[ROOT] onto the JUL framework 20:50:55,615 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [FILE] to Logger[ROOT] 20:50:55,622 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - End of configuration. 20:50:55,622 |-INFO in ch.qos.logback.classic.joran.JoranConfigurator@96def03 - Registering current configuration as safe fallback point Can anyone help determine what's going on? The two questions are: 1) What is it that's causing the DEBUG logging to be on? (I like that it's on, but don't understand why it's on.) 2) Why is the filter filtering INFO lines but not filtering DEBUG lines? (I want it filtering DEBUG lines.) Thanks, Mike

1 1