August 2011 - logback-user - mailman3.qos.ch

Is MDC thread safe?
by Odd Man 28 Aug '11

28 Aug '11

I've read that logback is thread safe, but I got exception using MDC. Is it bug or MDC access should be syncronized? java.util.ConcurrentModificationException: null at java.util.HashMap$HashIterator.nextEntry(HashMap.java:793) ~[na:1.6.0_26] at java.util.HashMap$EntryIterator.next(HashMap.java:834) ~[na:1.6.0_26] at java.util.HashMap$EntryIterator.next(HashMap.java:832) ~[na:1.6.0_26] at java.util.HashMap.putAll(HashMap.java:523) ~[na:1.6.0_26] at ch.qos.logback.classic.util.LogbackMDCAdapter.duplicateAndInsertNewMap(LogbackMDCAdapter.java:69) ~[logback-classic-0.9.29.jar:na] at ch.qos.logback.classic.util.LogbackMDCAdapter.put(LogbackMDCAdapter.java:95) ~[logback-classic-0.9.29.jar:na] at org.slf4j.MDC.put(MDC.java:112) ~[slf4j-api-1.6.1.jar:1.6.1]

3 2

Exception and error safe logging
by Adam Fitzgerald 27 Aug '11

27 Aug '11

Hello, For a project I'm working on we would like to be able to attempt recovery after the occurrence exceptions and some errors, and are investigating methods of integrating the use of logback into this strategy. In the case of exceptions, does logback make any guarantee about what will/won't be thrown from the message logging methods? Is there anything like a 'safe' logging API that will not throw? Secondly we want to catch OOM errors that may occur in a call to logback. The simplest (but tedious) approach would be to wrap the calls in a try-catch block. Alternatively we are considering proxying the logger and wrapping the calls to the real logger in a try catch within the proxy. Can anyone forsee any issues with doing this? Does any kind of functionality like this already exist? Thanks in advance, Adam

4 10

RollingFileAppender won't continue when log file is deleted
by rlambert-den 26 Aug '11

26 Aug '11

In development, our application generates an enormous amount of logging. For that reason it was handy with logback 0.9.28 to be able to just delete a log file and let the app continue and just start writing a to a new file. Unfortunately, in logback 0.9.29, that doesn't work. If I delete the current log file, logback does not create a new one. It just stops logging altogether. I'd be grateful for any tips on how to fix this and restore the old behavior (sorry, going back to 0.9.28 is not an option for political reasons). Our configuration has not changed and it is a pretty trivial RollingFileAppender (config is appended). <?xml version="1.0" encoding="UTF-8"?> <configuration debug="false">  <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender"> <encoder> <pattern>LEVEL:%-5level - %msg%n</pattern> </encoder> </appender> <appender name="FILE" class="ch.qos.logback.core.rolling.RollingFileAppender"> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">  <fileNamePattern>NetworkService.%d{yyyy-MM-dd}.log</fileNamePattern>  <maxHistory>7</maxHistory> </rollingPolicy> <encoder> <pattern>%d{HH:mm:ss.SSS} THREAD:[%thread] LEVEL:%-5level - %msg%n</pattern> </encoder> </appender> <logger name="NetworkService" level="DEBUG"> <appender-ref ref="FILE" /> <appender-ref ref="STDOUT" /> </logger> </configuration> -- View this message in context: http://old.nabble.com/RollingFileAppender-won%27t-continue-when-log-file-is… Sent from the Logback User mailing list archive at Nabble.com.

2 1

Thanks : All error in a separate file
by DECHOUX Bertrand 22 Aug '11

22 Aug '11

Indeed! The tresholdFilter seems to be what I need : http://logback.qos.ch/manual/filters.html#thresholdFilter. I skipped the filter part when I was reading for general purpose information. I thought it was for very advanced user. Thanks, Bertrand Dechoux --------------------------------- Hello, You can create 2 appenders : - one for your specific file (only errors) and the other with all levels - use filters in the first one : http://logback.qos.ch/manual/filters.html the way the 1st appender log only the logs with level.isEquals error level --------------------------------- Hi, I am new to logback configuration. I have read the online manual but clearly not in depth. I would like to log in a separate file all ERROR logs but keep these logs at the same time where they are supposed to be. I understand I could use root with an ERROR level and a file appender but then I woul lose all the details (logs lower than ERROR). Is there any obvious way that I might have missed? Regards, Bertrand Dechoux

1 0

Help needed for File inclusion in logback with relative path
by Renuka Pathak 22 Aug '11

22 Aug '11

> > Hi All, > > I am looking for help in including outside file in logback.xml. It works > when I use absolute path but does not work when I use relative path. I am > using logback version 0.9.20. Below is the suedo code I am writing. > LOGBACK_FILE_PATH is defined in env.properties. I also tried with <include > resource=" "> but it does not work either. > > <configuration> > <property resource="env.properties" /> > <include file="${LOGBACK_FILE_PATH}/backendlogback.xml"/> > > </configuration> > > Any help is appreciated. > > Thanks & Regards, > Renuka >

2 1

SyslogAppender failing silently
by Daniel Serodio (lists) 19 Aug '11

19 Aug '11

I'm trying to setup SyslogAppender to log to a virtual machine that's running rsyslog, and because of a firewall rule on the VM, SyslogAppender wasn't connecting to rsyslog, but I didn't see any errors or warnings from Logback, even after setting a OnConsoleStatusListener. If I change the "syslogHost" parameter to a non-existing name, I get an error message on the console, but the same doesn't happen for a refused connection. I expected to see some sort of notification about this problem. Regards, Daniel Serodio

4 4

help needed for File inclusion in logback with relative path
by Renuka Pathak 19 Aug '11

19 Aug '11

Hi All, I am looking for help in including outside file in logback.xml. It works when I use absolute path but does not work when I use relative path. I am using logback version 0.9.20. Below is the suedo code I am writing. LOGBACK_FILE_PATH is defined in env.properties. I also tried with <include resource=" "> but it does not work either. <configuration> <property resource="env.properties" /> <include file="${LOGBACK_FILE_PATH}/backendlogback.xml"/> </configuration> Any help is appreciated. Thanks & Regards, Renuka

1 0

All error in a separate file
by DECHOUX Bertrand 19 Aug '11

19 Aug '11

Hi, I am new to logback configuration. I have read the online manual but clearly not in depth. I would like to log in a separate file all ERROR logs but keep these logs at the same time where they are supposed to be. I understand I could use root with an ERROR level and a file appender but then I woul lose all the details (logs lower than ERROR). Is there any obvious way that I might have missed? Regards, Bertrand Dechoux

2 1

Integration with Tomcat 7 with SLF4J & Logback
by Jun Victorio 15 Aug '11

15 Aug '11

I've noticed that the latest slf4j & logback have a problem integrating with latest tomcat 7 release. I know also there is third party that tried to solve this problem (https://github.com/grgrzybek/tomcat-slf4j-logback) I'm just wondering if you plan to fix this issue in the future. Thanks. Jun Victorio Starcom Computer Corp. 21520 30th Dr. SE, Suite 101 Bothell, WA 98021 425.486.6464 x209

2 2

Best practices for FATAL errors...
by Leon Rosenberg 15 Aug '11

15 Aug '11

Hi, since logback doesn't support log level FATAL I'm wondering how you guys are separating between 'normal' errors and 'really bad' errors. Example: Warning: tried to insert statement into db, found key conflict, resolved it (somehow). Normal errors: couldn't insert the statement into db because the encoding is invalid (or couldn't read user's file because its corrupt) - affects one user. Really bad errors: have no connection to db, so my further existence is rather meaningless. So how do you guys log fatal errors without fatal? .-) best regards Leon

5 6