May 2013 - logback-user - mailman3.qos.ch

RollingFileAppender with SizeBasedTriggeringPolicy keeps writing to rotated file
by Rolando Segura 24 May '13

24 May '13

Hi I have an RollingFileAppender with a triggering policy of rotating by size when the log reaches 32MB and a maxIndex of 1, configuration below. It happens that after rotation logback keeps writing to both files. Is this expected? My understanding from documentation is that it will stop writing to the current log, rename it and starts writing a to a new file with the name of the File parameter. I'd appreciate your clarification if I'm not understanding well the RollingFileAppender and SizeBasedTriggering behavior. Thanks, Rolando <appender name="lognocrlf" class="ch.qos.logback.core.rolling.RollingFileAppender"> <File>/opt/log/file.nocrlf.log</File> <encoder> <pattern>[%d{ISO8601}] %5p [%t] $%logger$ - %replace(%m){'\r?\n',''}%n</pattern> </encoder> <rollingPolicy class="ch.qos.logback.core.rolling.FixedWindowRollingPolicy"> <maxIndex>1</maxIndex> <FileNamePattern>/opt/log/file.nocrlf.log.%i</FileNamePattern> </rollingPolicy> <triggeringPolicy class="ch.qos.logback.core.rolling.SizeBasedTriggeringPolicy"> <MaxFileSize>32MB</MaxFileSize> </triggeringPolicy> </appender>

3 6

What is the equivalent to org.apache.log4j.SimpleLayout?
by Neil Hart 24 May '13

24 May '13

We are converting some homegrown SNMP appenders and I wanted to find out what the SimpleLayout translates too. Thanks

2 1

SyslogAppender header with timestamp? Jan 01 01:00:00
by Andreas Kruthoff 22 May '13

22 May '13

Hi I'm using the SyslogAppender and am writing to a remote syslogd, using a local1.info facility and a logfile. All messages in syslog have the timestamp "Jan 01 01:00:00". As I can't influence the layout of this appender (http://logback.qos.ch/codes.html#syslog_layout) I wonder where this timestamp comes from. I've used wireshark and seen that logback is sending this date to syslogd. Is this a defect or am I missing something? I've checked log4j with wireshark. The header isn't created, and there's no timestamp in the transmitted message. Syslog is filling in its own timestamp in this case, which is correct. logback 1.0.12 solaris 10. thx -andreas This email and any attachment may contain confidential information which is intended for use only by the addressee(s) named above. If you received this email by mistake, please notify the sender immediately, and delete the email from your system. You are prohibited from copying, disseminating or otherwise using the email or any attachment.

1 1

Programmatically add OutputStreamAppender to all loggers
by Markos Fragkakis 21 May '13

21 May '13

Hi, I am building a simple web application that can be used to preview the pattern layout of log files. The application aims to give you an idea of what your log files will look like if you use a pattern layout. Here you can see it working for the Log4j PatternLayout (still in progress): http://log-preview.appspot.com/ Feel free to play around with, it is self explanatory. I want to add support for Logback as well. The idea is that I have a simple API, that is a servlet that receives a pattern as a parameter. I then create an appender with that pattern layout and attach it to the loggers of some classes. The appender actually appends to the response stream, so the logs are actually the response of the API. So, as I used a WriterAppender for log4j, I suppose an OutputStreamAppender is the equivalent for Logback. Unfortunately, I have not managed to append anything to the result stream. Could you see what is wring with my code? It was dead simple with Log4j, but I am still getting trouble here. Thanks! P.S. This is stripped down version that I think should be printing a log in the response package com.markos.logpreview; import java.io.IOException; import javax.servlet.http.HttpServlet; import javax.servlet.http.HttpServletRequest; import javax.servlet.http.HttpServletResponse; import org.slf4j.LoggerFactory; import ch.qos.logback.classic.Logger; import ch.qos.logback.classic.LoggerContext; import ch.qos.logback.classic.PatternLayout; import ch.qos.logback.classic.spi.ILoggingEvent; import ch.qos.logback.core.OutputStreamAppender; @SuppressWarnings("serial") public class Log_previewServlet extends HttpServlet { @Override public void doGet(HttpServletRequest req, HttpServletResponse resp) throwsIOException { resp.setContentType("text/plain"); LoggerContext loggerContext = (LoggerContext) LoggerFactory.getILoggerFactory(); loggerContext.reset(); OutputStreamAppender<ILoggingEvent> outputStreamAppender = newOutputStreamAppender<ILoggingEvent>(); outputStreamAppender.setContext(loggerContext); outputStreamAppender.setOutputStream(resp.getOutputStream()); PatternLayout pl = new PatternLayout(); pl.setPattern("%d %5p %t [%c:%L] %m%n)"); pl.setContext(loggerContext); pl.start(); outputStreamAppender.setLayout(pl); outputStreamAppender.start(); Logger logbackLogger = loggerContext.getLogger(Logger.ROOT_LOGGER_NAME); logbackLogger.addAppender(outputStreamAppender); * logbackLogger.error("I should show up in the response!");* } } -- Sent from my iPhone

1 0

Sending log files to user's home directory
by Donald McLean 16 May '13

16 May '13

I'm using a TimeBasedRollingPolicy for an app that may be run under different user names and I need the files to go to a "logs" directory in the running user's home directory "~/logs". Using "~/logs/" doesn't work in the <fileNamePattern>, but is there anything that will work? Thank you, Donald

3 2

Using JNDIBasedContextDiscriminator with access SiftingAppender
by Xavier Dury 16 May '13

16 May '13

Hi, I would like to do something like this in my logback-access.xml: <appender name="FILE" class="ch.qos.logback.access.sift.SiftingAppender"> <discriminator class="ch.qos.logback.classic.sift.JNDIBasedContextDiscriminator" /> <sift> <appender class="ch.qos.logback.core.FileAppender"> <file>/logs/${contextName}/access.log</file> <encoder class="ch.qos.logback.access.PatternLayoutEncoder"> <pattern>%h %l %u %user %date "%r" %s %b</pattern> </encoder> </appender> </sift> </appender> but it doesn't work because I'm using a discriminator from logback-classic (JNDI). As the only discriminator in logback-access is AccessEventDiscriminator, is there another way to split access logs in multiple files (one per application)? Thanks, Xavier

1 0

Send output to bit bucket?
by Donald McLean 14 May '13

14 May '13

Is there a way to set up logback so that everything is turned off by default? Thank you, Donald

2 1

Re: [logback-user] SMTPAppender with Amazon SES
by Jason Bennett 14 May '13

14 May '13

> It's most likely coming from a stack trace generated by your application. > The JavaMail API is vulnerable to header injection via the Subject header, > and you're probably seeing that phenomenon (though by accident). > > For my own application, I wrote a subclass of SMTPAppender that truncates > the Subject header at the first EOL character, which prevents this issue > from occurring. > > Thanks, I figured it was something like this, but I didn't realize the problem with the subject line. Would this be appropriate to file as a JIRA issue? jason -- Jason Bennett, jasonab(a)acm.org E pur si muove! Get Firefox! - http://getfirefox.com

2 1

Setting log levels per context
by Daniel López 14 May '13

14 May '13

Hi there, I have been able to separate the different logs of differents web applications in a shared host using a sift appender like this one: <appender name="SIFT" class="ch.qos.logback.classic.sift.SiftingAppender"> <discriminator class="ch.qos.logback.classic.sift.JNDIBasedContextDiscriminator"> <defaultValue>unknown</defaultValue> </discriminator> <sift> <appender name="FILE-${contextName}" class="ch.qos.logback.core.FileAppender"> <file>${catalina.base}/logs/logback-${contextName}.log</file> <append>true</append> ... </appender> </sift> </appender> And so far, it works great. My question now would be if it is possible to set different levels for the different contexts in an easy way. I know I can copy the library on each application and use a different configuration file per webapp (not using logback for the global Tomcat then) and I have been able to use Filter to simulate the level setting per context by setting the level to the Max and then filtering out the levels by context... but I was wondering if there is no easier way to do it, as adding filter code for each webapp makes the configuration look fragile and bloated. I have 28 small-medium apps in this host, so that's why I'm trying to find the simplest way :). So I guess I'm looking for something like.. <logger name="org.whatever" level="INFO" context="MyApp"...> Does something like that exist and I was unable to find it? If no, do you think it would be intesting? I might give it it shot if that's the case. Cheers! D. ------------------------------------------- Daniel Lopez Janariz (D.Lopez(a)uib.es) Web Services Balearic Islands University (SPAIN) -------------------------------------------

1 0

SMTPAppender with Amazon SES
by Jason Bennett 14 May '13

14 May '13

I'm using Amazon SES with SSL to send emails via Logback's SMTPAppender. It usually works, but sometimes I receive the following error: 0:01:51,863 |-ERROR in ch.qos.logback.classic.net.SMTPAppender[EMAIL] - Error occurred while sending e-mail notification. com.sun.mail.smtp.SMTPSendFailedException: 554 Transaction failed: Illegal header 'Caused by'. at com.sun.mail.smtp.SMTPSendFailedException: 554 Transaction failed: Illegal header 'Caused by'. at at com.sun.mail.smtp.SMTPTransport.issueSendCommand(SMTPTransport.java:2114) at at com.sun.mail.smtp.SMTPTransport.finishData(SMTPTransport.java:1900) at at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:1122) at at javax.mail.Transport.send0(Transport.java:195) at at javax.mail.Transport.send(Transport.java:124) at at ch.qos.logback.core.net.SMTPAppenderBase.sendBuffer(SMTPAppenderBase.java:395) at at ch.qos.logback.core.net.SMTPAppenderBase$SenderRunnable.run(SMTPAppenderBase.java:690) at at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at at java.lang.Thread.run(Thread.java:679) I'm aware that Amazon only allows emails with legal headers through SES, but I have no idea where Amazon is getting this header from. Has anyone else seen this? jason -- Jason Bennett, jasonab(a)acm.org E pur si muove! Get Firefox! - http://getfirefox.com

2 1