- logback-user - mailman3.qos.ch

Bridging Log4J over SLF4J and the lack of Log4J Logger.setLevel()
by Mark Petrovic 07 Jan '13

07 Jan '13

[Originally posted on 12/26/2012, but it apparently did not make it to the list archives. msp] Hi. Thank you for SLF4J and Logback. I have this line of code that just today came in from an upstream dependency out of my control: private static final Logger logger = Logger.getLogger(FooImpl.class); static { logger.setLevel(Level.DEBUG); <<<<<<<<<<<<<<<< } Unfortunately, this is logging code I had been successfully bridging, but this setLevel() call on a Log4J logger breaks it. Do I have any elegant recourse beyond asking the developers of the line of code to not do this? Thanks. -- Mark

3 3

Pointing logback at a symbolic soft link
by Antony Stubbs 07 Jan '13

07 Jan '13

Loback doesn't seem to be able to see the file, it just carries on like there was no config file. And because of the debug system, I get no debug information. Can logback be pointed at a soft symbolic link file? ----- ___________________________ http://stubbisms.wordpress.com http://stubbisms.wordpress.com -- View this message in context: http://old.nabble.com/Pointing-logback-at-a-symbolic-soft-link-tp34863570p3… Sent from the Logback User mailing list archive at Nabble.com.

2 4

Logback design question
by Mark Petrovic 07 Jan '13

07 Jan '13

In Logback, Levels are final, meaning one cannot extend them to create new levels. I have no problem with this, but my users are wondering about it. Can you explain? Thank you. -- Mark

3 4

Incorrect rolling of log file
by Viens, Mike 03 Jan '13

03 Jan '13

I am using Logback to create a daily rolling log file. It does rename the existing log file and creates a new one, however it is not doing it correctly (or I am telling something incorrectly). Below is the logback.xml file I am using: <?xml version="1.0" encoding="UTF-8"?> <configuration> <timestamp key="today" datePattern="yyyyMMdd"/> <appender name="ScreenAppender" class="ch.qos.logback.core.ConsoleAppender"> <filter class="ch.qos.logback.classic.filter.ThresholdFilter"> <level>debug</level> </filter> <encoder> <pattern>%date{HH:mm:ss.SSS} %-5level %logger{20} [%file:%line] - %msg%n</pattern> </encoder> </appender> <appender name="UpdateAppender" class="ch.qos.logback.core.rolling.RollingFileAppender"> <append>true</append> <filter class="ch.qos.logback.classic.filter.ThresholdFilter"> <level>info</level> </filter> <file>${CATALINA_HOME}/logs/update-server.log</file> <encoder> <pattern>%date{HH:mm:ss.SSS} %-5level %logger{40} [%file:%line] - %msg%n</pattern> </encoder> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <fileNamePattern>update-server.%d{yyyy-MM-dd}.zip</fileNamePattern> <maxHistory>180</maxHistory> </rollingPolicy> </appender> <root level="debug"> <appender-ref ref="ScreenAppender"/> <appender-ref ref="UpdateAppender"/> </root> </configuration> The log file does get created as update-server.log. And when the day rolls over, the next generated message for logging does result in that log file being renamed, but not as I expect it to. The resulting name is update-server.log1161295506996864.tmp. And, the file itself is not ZIPped, just renamed. I would expect the file to be named update-server.20120103.log and to have that file ZIPped. Does anyone know why? As a second (minor) issue, I would like the original log file to be called update-server-YYYYMMDD.log, but when I tried to do that, the log file created stays the same and at midnight, the file is overwritten. I used the line below, but it appears that Logback does not increment the ${today} value: <file>${CATALINA_HOME}/logs/update-server-${today}.log</file> Mike Viens Sr. Software Engineer K-12 Technology 10911 White Rock Road, Suite 100 Rancho Cordova, CA 95670 D: (916)288-1651 M: (916)524-3663 E: mike.viens(a)pearson.com <mailto:michael.viens@pearson.com> Pearson Always Learning Learn more at www.pearsonschoolsystems.com <http://www.pearsonschoolsystems.com/>

1 0

Writing logs to ByteArrayStream programmatically
by Dan Filimon 02 Jan '13

02 Jan '13

Hi! I've been trying for the past couple of hours to log to a ByteArrayStream that I then convert to String and process. This is the code I came up with [1], that's sadly not working. I read an older e-mail about this [2], but I still can't get it working. I added some asserts to make sure I'm starting the objects properly and to my surprise the PatternLayoutEncoder's isStarted() method (actually the one in LayoutWrappingEncoder) always returns false, despite started being configurable. And, in any case, even removing the offending assert, I still can't write anything to the byte stream. It doesn't output anything now (after I call reset() on the LoggerContext object), otherwise it prints to the console (I don't have any config file set up). What am I doing wrong? Thanks! [1] https://gist.github.com/4436581 [2] http://old.nabble.com/Programmatic-configuration-of-OutputStreamAppender-tt…

1 0

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