- logback-user - mailman3.qos.ch

TeeFilter modifies the encoding of the dataes
by Olivier Faucheux 02 Sep '11

02 Sep '11

Hello *, I have observed that the use of TeeFilter corrupts the accents in my http webpages. Surely we have the same problem as the one described for the RequestDumpValve in the bug https://issues.apache.org/bugzilla/show_bug.cgi?id=40177. Can somebody confirm it? Is it possible to bypass the problem? Tanks Olivier Faucheux forcont business technology gmbh

3 3

Programmatically create loggers for hibernate, spring ...
by BAKHTI Mohammed 01 Sep '11

01 Sep '11

Hello again :) Can i programmatically create loggers for spring , hibernate and other frameworks? means something like : logfactory.getlogger("org.springframework"); and then set the apropriate level ? Is this possible? because i tried it but don't really think it works Thanks for help

2 1

Getting the error code to print using LogBack.
by Vivek M.V 30 Aug '11

30 Aug '11

Hi , I'm trying to implement the SLF4J +LogBack logging solution to implement logging in my application . I've modified the Pattern Expression in the logback.xml as below. <Pattern>%d{dd MMM yyyy HH:mm:ss.SSS} %logger{36} %M-%msg%n</Pattern> And its working fine . However I'd like to print the 'error code ' as well in my log say 404 or 500 as well . Any ideas on how I should be modifying my pattern expression for this? Thanks. <font Face='Arial' style='font-size:9pt'>This e-mail, and any attachments are strictly confidential and may also contain legally privileged information. It is intended for the addressee(s) only. If you are not the intended recipient, please do not print, copy, store or act in reliance on the e-mail or any of its attachments. Instead, please notify the sender immediately and then delete the e-mail and any attachments. Unless expressly stated to the contrary, the views expressed in this e-mail are not necessarily the views of Enzen Technologies (P) Limited or any of its subsidiaries or affiliates (Group Companies), and the Group Companies, their directors, officers and employees makes no representation and accept no liability for the accuracy or completeness of this e-mail. You are responsible for maintaining your own virus protection and the Group Companies do not accept any liability for viruses. Enzen reserves the right to monitor and review the content of all messages sent to or from this e-mail address. Messages sent to or from this e-mail address may be stored on the Enzen e-mail system.</font>

4 4

Glassfish + OSGi + slf4j + logback
by cinhtau 30 Aug '11

30 Aug '11

Dear logback experts, I created a thread on Glassfish Mailinglist of a ugly error. http://old.nabble.com/HybridApplication-WeldBootstrap-Error-td32335499.html… I want to use logback over slf4j in OSGi (Apache Felix). Glassfish itselfs has put some slf4j api specifications in their bundle org.glassfish.weld.WeldDeployer. Has anybody a working workaround to log with logback and Glassfish as osgi bundles? -- View this message in context: http://old.nabble.com/Glassfish-%2B-OSGi-%2B-slf4j-%2B-logback-tp32340532p3… Sent from the Logback User mailing list archive at Nabble.com.

2 6

ch.qos.logback.classic.filter.LevelFilter has not minLevelMatch????
by zuxiong lin 30 Aug '11

30 Aug '11

ch.qos.logback.classic.filter.LevelFilter has not minLevelMatch???? why?? just onMatch and onMismatch .... linzuxiong

1 1

why could log4j %F:%L find the sources in eclipse console , logback not??
by zuxiong lin 29 Aug '11

29 Aug '11

why could log4j %F:%L find the sources in eclipse , logback not?? Log4j prints the infos in the eclipse console. The color is blue and underline. logback has no the feature.. Can add it ?

1 0

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