January 2014 - 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

release of logback version 1.1.0
by Ceki Gulcu 29 Jan '14

29 Jan '14

Hello all, The logback team is happy to announce the release of logback version 1.1.0. It contains many bug fixes and improvements. It should hit the Maven central repository by the time you read this message. Please refer to the news page for precise details about this release. 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

Logs getting mixed in log file
by Sumit Anvekar 24 Jan '14

24 Jan '14

Hi, I have 2 web applications which use log back for logging. I'm referring to the logback jars in both applications using a single shared library. each application has its own log file. Most of the logs work fine (i.e, they go to the required log files) but some others get mixed up, e.g. consider applications as A and B, sometime logs from application A are present in application B log files. I'm not sure what is causing this. Let me know if i'm missing anything. Sumit.

2 1

Introducing Whisper - a suppression capable logback appender
by Karthik Abram 13 Jan '14

13 Jan '14

Hello Logback users, I wanted to make you all aware of a new Logback appender that I have released called Whisper. Whisper is a delegating appender that can suppress error messages when they exceed a configured threshold. During the suppression period, Whisper will send you a digest of messages that were suppressed. Once the frequency drops back to normal, message flow will continue as usual. 1. Where do I find it? http://eclecticlogic.github.io/whisper/ 2. What's the main use case for this? In conjunction with SMTP appender for error emails to prevent error email span when things go bad.3. What kind of license? Apache 2.04. Does Whisper suppress all messages? No, it only suppresses those messages that have exceeded the threshold. 5. What if my messages are similar but only vary by a couple of parameters? If you use the SLF4j api and use the parameterized log message format, then Whisper will suppress across parameterized messages. ThanksKA

1 0

ReconfigureOnChangeFilter does not reuse context properties?
by Mike Müller 09 Jan '14

09 Jan '14

Hi I'm using a config file wich looks like this: <?xml version="1.0" encoding="UTF-8"?> <configuration scan="true" scanPeriod="60 seconds" > <appender name="cms" class="ch.qos.logback.core.FileAppender"> <file>${pathToLogs}mysign-cms.log</file> <Append>false</Append> <encoder> <pattern>%d %30.30t %-5p %45.45c - %m%n</pattern> </encoder> </appender> <appender name="R" class="ch.qos.logback.core.FileAppender"> <file>${pathToLogs}log.log</file> <Append>false</Append> <encoder> <pattern>%d %30.30t %-5p %45.45c - %m%n</pattern> </encoder> </appender> <logger name="ch.mysign" additivity="false" level="INFO"> <appender-ref ref="cms"/> </logger> <root level="WARN"> <appender-ref ref="R"/> </root> </configuration> The parameter ${pathToLogs} comes from the following code: LoggerContext context = (LoggerContext) LoggerFactory.getILoggerFactory(); try { JoranConfigurator configurator = new JoranConfigurator(); configurator.setContext( context ); context.reset(); context.putProperty( "pathToLog", "my-path-to-the-external-logs" ); configurator.doConfigure("my-logback-config.xml" ); } catch ( JoranException je ) { System.out.println( je.getMessage() ); } If I change the config file, the property "pathToLog" gets lost. Is this the same issue as descibed in [1]? If yes, is it a problem to reuse the context or at least the properties of the old context? [1] http://jira.qos.ch/browse/LOGBACK-592 best regards Mike

2 4

SyslogAppender
by Jason Dusek 02 Jan '14

02 Jan '14

Hi All, I am trying to use the SyslogAppender. One problem I am having is that the program name is absent, and the PID seems to be "main". I assume this is because the program name is generically set to "main" and the PID is actually omitted. I wanted to confirm this by browsing the source but I am having some trouble understanding the underlying details. In particular, what does this code do? // http://logback.qos.ch/xref/ch/qos/logback/classic/net/SyslogAppender.html#1… layout.getInstanceConverterMap().put("syslogStart", SyslogStartConverter.class.getName()); I am not as familiar with Java idioms as I could be; and I've lost the trail at around "syslogStart". I would like to try working off of SyslogAppenderBase to get a syslog appender that understands UNIX sockets. Is that something the project would welcome? -- Jason Dusek

1 0