December 2012 - 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

Replacing Tomcat7 Logging with Logback?
by James Carr 17 Sep '13

17 Sep '13

Hi All, Is there a good tutorial or documentation on replacing Tomcat's default logging with logback? So far my searches turn up http://logback.qos.ch/access.html which only seems to work with access logs, not the actual server logging itself. Thanks, James

4 3

(Important) Dynamically change the scan period
by Yihya Hugirat 08 Apr '13

08 Apr '13

hi all, i have migrated to logback to be able to change the log levels dynamically. i'm testing it now with calssfish 3.01 and somehow it is not working when i change the levels in logback.xml there nothing happens. by deploying from netbeans i get the following: |-INFO in ch.qos.logback.classic.turbo.ReconfigureOnChangeFilter@11bfee0 - Will scan for changes in [[C:\Dokumente und Einstellungen\user_Home\Eigene Dateien\NetBeansProjects\WS-LDAP\build\web\WEB-INF\classes\logback.xml]] every 15 seconds. but when i change the levels in this file nothing happens Any help will be appreciated Hugirat -- إِنَّ الَّذِينَ يُحِبُّونَ أَنْ تَشِيعَ الْفَاحِشَةُ فِي الَّذِينَ آمَنُوا لَهُمْ عَذَابٌ أَلِيمٌ فِي الدُّنْيَا وَالآخِرَةِ وَاللَّهُ يَعْلَمُ وَأَنْتُمْ لا تَعْلَمُونَ My public key please use it when you contact me: هذا مفتاحي العام الرجاء أستخدامه عند الإتصال بي: 09BA B710 4B98 ECDA 8C0A 6CB1 2E1E CF88 6A12 F2C3

3 4

Externalized Logback configuration for web applications
by Perryn Fowler 01 Feb '13

01 Feb '13

Hello, I have a logging use case that I would think was relatively common, but that does not seem to be supported particularly well by logback. I wanted to see what the logback community thinks/advises. The details of the use case - I am writing java web apps to be deployed to JEE web containers. - I want the logging config to be external to the wars, so that I can use the same wars in different environments, but configure logging differently. - I want to be able to deploy several different wars to the same web container and have them use different logging configurations. The logback documentation seems to push towards either packaging the logback config in the wars, or sharing an external logging config between them. (Whereas I want separate external logging configuration for each war) I hope that makes sense. The JNDI support described here: http://logback.qos.ch/manual/loggingSeparation.html looks like it might be of use, but it does seem to require that the config files are placed in WEB-INF/classes and I would prefer they are completely external to the war. I have found a number of people who have coded up their own solutions, notably: http://blog.iprofs.nl/tag/logback/ and https://bowerstudios.com/node/896 That doesn't look too bad, but wondering what the community thinks of these approaches -- ----------------------- Perryn Fowler

6 10

AUTO: Manfred Kuhlmann is out of office. (Rückkehr am 07.01.2013)
by manfred.kuhlmann＠steria-mummert.de 28 Dec '12

28 Dec '12

Ich werde ab dem 22.12.2012 nicht im Büro sein. Ich kehre zurück am 07.01.2013. I will be out of the office starting 22.12.2012. I will be back on 07.01.2013. Ihre Nachricht werde ich nach meiner Rückkehr beantworten. Mit freundlichen Grüßen Manfred Kuhlmann Hinweis: Dies ist eine automatische Antwort auf Ihre Nachricht " [logback-user] Hostname or process ID in log messages" gesendet am 28.12.2012 17:15:09. Diese ist die einzige Benachrichtigung, die Sie empfangen werden, während diese Person abwesend ist. Steria Mummert Consulting AG Vorsitzender des Aufsichtsrates: Jürgen Sponnagel - Vorstand: Dr. Fritz Moser (Vors.), Dr. Reinhard Liedl Gesellschaftssitz: Hamburg - HR B 61 116 Amtsgericht Hamburg - USt-ID-Nr.: DE118671351 Bitte denken Sie an Ihre Verantwortung gegenüber der Umwelt: Jede ausgedruckte E-Mail verursacht ca. 0,3 Gramm CO2 pro Seite. Diese Nachricht kann vertrauliche Informationen enthalten und ist allein für den Adressaten bestimmt. Wenn Sie nicht der rechtmäßige Empfänger sind, sind der Zugriff, die Weiterleitung, das Kopieren, die Veröffentlichung oder anderweitige Verwendung des Inhalts untersagt. In diesem Fall bitten wir Sie, den Absender unverzüglich zu informieren und diese E-Mail sowie sämtliche Kopien dieser E-Mail zu löschen. Der Inhalt von E-Mails innerhalb des Netzwerks kann überprüft werden, um die Übereinstimmung mit den geltenden Firmenrichtlinien und Vorgehensweisen zu gewährleisten. E-Mails können auf dem Transportweg von Dritten verändert werden, so dass deren Vollständigkeit und Echtheit nicht garantiert werden können. This e-mail communication may contain confidential information and is intended only for the recipient. If you are not the intended recipient you are not allowed to read, copy, distribute, publicize or use the content of this e-mail in any way. Please notify the sender and delete the e-mail and any copies of it. The content of e-mails within our network may be monitored to ensure compliance with company policies and procedures. E-mails can be alterated by third parties in transit. Therefore any e-mail is susceptible to alteration and its integrity cannot be assured.

1 0

Hostname or process ID in log messages
by Daniel Ferber 28 Dec '12

28 Dec '12

Hi, I am wondering if Logback has a solution to identify the process or the host that is running the application. This would be relevant for applications with instances running in parallel, but writing their log to a central repository (eg using DBAppender to a common database). A typical scenario would be load balancing a web application in the cloud, or a heavy computation split over several processors. If an instance fails, I would be important to have the log message to distinguish this instance among others. I think that MDC could do this job. However, this would work only for threads that are under my control. Is it possible to add some log meta-data globally to the logger context? Best regards, Daniel Felix Ferber

1 0

no applicable action for [encoder], with SMTPAppender
by Eugen Paraschiv 21 Dec '12

21 Dec '12

Hi, I am using logback 1.0.9 (along with slf4j 1.7.2); I have defined the following appender: <appender name="EMAIL" class="ch.qos.logback.classic.net.SMTPAppender">  <filter class="ch.qos.logback.classic.filter.ThresholdFilter"> <level>ERROR</level> </filter> <smtpHost>email-smtp.us-east-1.amazonaws.com</smtpHost> <username>AKIAJI6XLSOAQX3IW6HQ</username> <password>AuSWMdcNObKqGGT550SR/6vDrgh50vxgFrqZHwR2tTED</password> <SSL>true</SSL> <to>hanriseldon(a)gmail.com</to> <from>info(a)applieddatalabs.com</from> <subject>${launchpad.origin}: %logger{20} - %m</subject> <encoder class="ch.qos.logback.classic.encoder.PatternLayoutEncoder"> <pattern>prov - |${launchpad.origin}| %date [%thread] %-5level %logger{36} - %message%n</pattern> </encoder> <cyclicBufferTracker class="ch.qos.logback.core.spi.CyclicBufferTrackerImpl"> <bufferSize>1000</bufferSize> </cyclicBufferTracker> </appender> And I am now getting: 20:41:10,925 |-ERROR in ch.qos.logback.core.joran.spi.Interpreter@32:72 - no applicable action for [encoder], current pattern is [[configuration][appender][encoder]] 20:43:04,138 |-ERROR in ch.qos.logback.core.joran.spi.Interpreter@33:13 - no applicable action for [pattern], current pattern is [[configuration][appender][encoder][pattern]] Not sure why that is - I am doing anything wrong on the appender setup? Thanks. Eugen. -- Eugen Paraschiv Senior Java Programmer, Optaros Mobile: +40728896170 Blog: www.baeldung.com Twitter: https://twitter.com/baeldung

2 2

Log Message regardless of Log Level
by Shane Kelly 21 Dec '12

21 Dec '12

Folks, Just wondering if there is a capability within Logback for writing a log message regardless of whatever log level has been set in configuration. Consider the scenario where I want my web application to output some diagnostic information at startup or shutdown - for example, the Web Application version, build date etc. If I were to set the log level of these messages to be TRACE, DEBUG, or INFO then its possible they may never be displayed since the app may typically be configured to run with a log level of WARN. Similarly, I don't want to set the log level of the messages to WARN, ERROR or FATAL in order to ensure that they do get displayed since they're not really error messages, and if we monitor the log files for WARN, ERROR or FATAL messages then this would trigger a false positive. So, is there some way to force a message to be logged at all times, independently of log level? Or some way to achieve this effect via existing configuration. Arguably I suppose this is bending the rules slightly, in that it could be abused - why offer the ability to filter certain log levels if an application can override/ignore them - but perhaps this is something which could be configurable/switchable? Regards, Shane

5 9

SyslogAppender - UDP only
by Juergen Weber 21 Dec '12

21 Dec '12

Hi, you might document that SyslogAppender is UDP only (which is implicit by RFC 3195, I guess), but still syslog-ng can listen on TCP, too, also syslog4j.org supports TCP, so I was suprised that SyslogAppender messages did not arrive at the syslog-ng TCP port.. http://logback.qos.ch/manual/appenders.html#SyslogAppender Thanks, Juergen -- View this message in context: http://old.nabble.com/SyslogAppender---UDP-only-tp34823801p34823801.html Sent from the Logback User mailing list archive at Nabble.com.

1 0