October 2013 - logback-user

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

Any way to use all syslog level with syslog appender?
by Erik Steffl 31 Oct '13

31 Oct '13

Is there any way to use all syslog levels (see e.g. http://en.wikipedia.org/wiki/Syslog#Severity_levels) when using Syslog appender? I see the constants for them defined in: https://github.com/qos-ch/logback/blob/master/logback-core/src/main/java/ch… but I don't see all of them used. Thanks, erik

1 0

getting a null logger level
by gaston sponer 30 Oct '13

30 Oct '13

I'm getting a null logger level when I change the level of the logger from Logback.xml: Logger logger = (Logger) LoggerFactory.getLogger(event.getLoggerName()); logger.getLevel(); ----> getLevel == null. First time i run my app logger.getLevel() I get a successful "INFO" Logback.xml: <logger name="com.HomePageAction" level="INFO" /> but when i change it to "debug" and redeploy my app, logger.level is null. Logback.xml: <logger name="com.HomePageAction" level="DEBUG" /> Any idea what could be wrong here ? Thanks

1 0

Setting the log file file size with RollingFileAdapter does not work
by adriana lima 30 Oct '13

30 Oct '13

Hello everyone, I am trying to specify the size of my log file in my Java code. However, no file is written in the specified directory. Using a FileAppender without a triggering policy works fine. But I would like to specify the max. log file size. Any help is appreciated :) Thanx in advance! Here is my code: LoggerContext loggerContext = (LoggerContext) LoggerFactory.getILoggerFactory(); RollingFileAppender<ILoggingEvent> fileAppender = new RollingFileAppender<ILoggingEvent>(); fileAppender.setContext(loggerContext); fileAppender.setFile("C:\\log\\log.txt"); SizeBasedTriggeringPolicy<ILoggingEvent> triggeringPolicy = new SizeBasedTriggeringPolicy<ILoggingEvent>(); triggeringPolicy.setMaxFileSize("5MB"); triggeringPolicy.start(); PatternLayoutEncoder encoder = new PatternLayoutEncoder(); encoder.setContext(loggerContext); encoder.setPattern("%d %level %logger: %msg%n"); encoder.start(); fileAppender.setEncoder(encoder); fileAppender.setTriggeringPolicy(triggeringPolicy); fileAppender.start(); Logger logbackLogger = loggerContext.getLogger("ExportMapToFile"); ((ch.qos.logback.classic.Logger) logbackLogger).addAppender(fileAppender); logbackLogger.info(info); fileAppender.stop(); triggeringPolicy.stop(); encoder.stop();

2 1

Logs are written in wrong file when changing log level.
by Harsimranjit singh Kler 29 Oct '13

29 Oct '13

Hi I am using slf4j 1.7.5,logback 1.0.3. In my app i am using application context to set app name as per given example. http://logback.qos.ch/faq.html Is it possible for multiple JEE applications to share the same configuration file but without stepping on each other's toes?<http://logback.qos.ch/faq.html#sharedConfiguration> Every thing is fine intially and one common xml file is writing in different log files but when i am changing log level its not reading applicationName and start writing in "application-name_IS_UNDEFINED1.log" File. Why this behaviour?

2 1

SMTPAppender subject PARSER_ERROR
by mirandes 28 Oct '13

28 Oct '13

Hi, the subject of my SMTPAppender in logback access always displays a %PARSER_ERROR, unless I put plain text in the subject. For the subject line: <subject>TESTING: %logger{20} - %m</subject> I'm getting this as subject: TESTING: %PARSER_ERROR[logger] - %PARSER_ERROR[m] I'm using the 1.0.13 version in Jetty and my logback-access.xml is as follows: <appender name="SMTP" class="ch.qos.logback.access.net.SMTPAppender"> <layout class="ch.qos.logback.access.PatternLayout"> <encoder> <pattern>%fullRequest%n%n%fullResponse</pattern> </encoder> </layout> <Evaluator class="ch.qos.logback.access.net.URLEvaluator"> <URL>index</URL> </Evaluator> <from>blahz(a)blah.com</from> <subject>TESTING: %logger{20} - %m</subject> <smtpHost>localhost</smtpHost> <to>zzz(a)blah.com</to> </appender> <appender-ref ref="SMTP" /> Any ideas? -- View this message in context: http://logback.10977.n7.nabble.com/SMTPAppender-subject-PARSER-ERROR-tp1299… Sent from the Users mailing list archive at Nabble.com.

3 2

logback receiver configuration issue
by George Richardson 22 Oct '13

22 Oct '13

I am trying to run the logback example 'ReceiverExample.java' using the provided config file receiver1.xml. When the application is started I get the following error messages: 12:24:13,190 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.ConsoleAppender] 12:24:13,190 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [CONSOLE] 12:24:13,202 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property 12:24:13,209 |-INFO in ch.qos.logback.classic.joran.action.RootLoggerAction - Setting level of ROOT logger to DEBUG 12:24:13,209 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [CONSOLE] to Logger[ROOT] 12:24:13,212 |-ERROR in ch.qos.logback.core.joran.spi.Interpreter@19:76 - no applicable action for [receiver], current pattern is [[configuration][receiver]] 12:24:13,212 |-ERROR in ch.qos.logback.core.joran.spi.Interpreter@20:11 - no applicable action for [port], current pattern is [[configuration][receiver][port]] 12:24:13,212 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - End of configuration. I don't understand what the issue with the receiver element in the config file. The configutrration file is: <configuration debug="true"> <appender name="CONSOLE" class="ch.qos.logback.core.ConsoleAppender"> <encoder> <pattern>%d{HH:mm:ss.SSS} [%thread] %-5level %logger - %msg%n</pattern> </encoder> </appender> <root level="DEBUG"> <appender-ref ref="CONSOLE" /> </root> <receiver class="ch.qos.logback.classic.net.server.ServerSocketReceiver"> <port>6000</port> </receiver> </configuration> George Richardson Software Developer ________________________ ____ _____ COMRAD. Radiology Information Solutions DDi +64 3 353 1445 e-mail: georger(a)comrad.co.nz<mailto:rickg@comrad.co.nz>

2 2

Can MDC values take a default
by Amit Mohan 21 Oct '13

21 Oct '13

I have this pattern and it's working : <pattern>%d{HH:mm:ss} %-5p [%t] [%c{1}] [%X{amtrac.serviceName}] [%X{amtrac.method}] [%X{amtrac.clientProcessName}] [%X{identity_user_context_guid}] [%X{identity_user_context_username}] [%X{identity_user_context_partner_id}] [%X{amtrac.tx}] MESSAGE=[%m]%n</pattern> However, I would like to replace a NULL if any of the MDC is null as a default value so... <pattern>%d{HH:mm:ss} %-5p [%t] [%c{1}] [%X{amtrac.serviceName*:-NULL*}] [%X{amtrac.method*:-NULL*}] [%X{amtrac.clientProcessName*:-NULL*}] [%X{identity_user_context_guid*:-NULL*}] [%X{identity_user_context_username}] [%X{identity_user_context_partner_id}] [%X{amtrac.tx}] MESSAGE=[%m]%n</pattern> I tried it but it seems like it totally stops logging anything. Thanks in advance! -Amit Mohan

1 0

Does Logback remove ANSI codes from messages? - 1.0.9
by Howard Lewis Ship 21 Oct '13

21 Oct '13

I'm using Logback 1.0.9. I've been doing a bit of work to make use of ANSI graphics renditions in the text I'm outputting; what I'm seeing is that when the ANSI-enhanced text passes through Logback, the ANSI formatting is stripped out. [image: Inline image 1] As you can see in the above snapshot; if I print the text to System.out, the ANSI codes (to make some of the text red) are honored. When the same string is passed to Logback, the ANSI does not appear. I did a look through the Logback code and could not find anything that would explain this. Perhaps I missed it, or missed something in the JDK libraries. In any case, what I'd like is to be able to see the ANSI-enhanced text in the console, when the output is triggered by Logback. -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com

1 0