December 2012 - logback-user

Logback code equivalent to adding log4j WriterAppender?
by Fred Toth 18 Dec '12

18 Dec '12

Hi folks, I have a batch application that is using native log4j calls to capture WARN and ERROR events to a StringWriter, using their WriterAppender. At the end of the batch run, we retrieve the buffer and send an email. I'm converting this to Logback and I've been looking for examples of how to do something similar. I don't really want to use SMTPAppender, because my existing email code is working and builds custom emails, handles address lists, etc. I've got two problems, really: 1. What's the closest thing to WriterAppender with a StringWriter? 2. What's the simplest way to add this appender at runtime (startup)? Can anyone point me to the Logback equivalent of this log4j code or suggest an alternative? static void initLogBuf() { Logger superLog = Logger.getLogger("org.project.my"); Enumeration<Appender> e = Logger.getRootLogger().getAllAppenders(); // Take the first layout we can find and use it Layout defaultLayout = null; while (e.hasMoreElements()) { Appender app = e.nextElement(); defaultLayout = app.getLayout(); break; } WriterAppender wApp = new WriterAppender(); wApp.setWriter(logBufWriter); wApp.setName(LOG_BUF); wApp.setLayout(defaultLayout); wApp.setThreshold(Level.WARN); //log.info("WAPP: " + wApp.getThreshold()); superLog.addAppender(wApp); } Many thanks, Fred

1 0

Error when <Property> name and value attributes are present, but value attribute is empty ("")
by Shane Kelly 15 Dec '12

15 Dec '12

Folks, I define a number of locally scoped properties in my logback configuration which are reused throughout the remainder of the file. For example: <property name="LOG_DATE_FORMAT" value="'yyyy-MM-dd HH:mm:ss,SSS Z'" /> <property name="LOG_TIMEZONE" value="" /> <property name="LOG_BASEDIR" value="${catalina.base}/logs/myappname" /> ... ... ... <appender name="MyAppName-RFA" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>${LOG_BASEDIR}/myappname.log</file> <filter class="ch.qos.logback.classic.filter.ThresholdFilter"> <level>DEBUG</level> </filter> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">  <fileNamePattern>${LOG_BASEDIR}/archive/%d{yyyy,aux}/myappname.%d{MM}.log.gz</fileNamePattern> <maxHistory>24</maxHistory> </rollingPolicy> <encoder> <pattern>%d{${LOG_DATE_FORMAT},${LOG_TIMEZONE}} %-6p [%X{MyAppName-UUID}] %c:%M - %m%n</pattern> <outputPatternAsHeader>false</outputPatternAsHeader> </encoder> </appender> I have multiple rolling file appenders, so rather than define the values manually for each appender, I define the local property and reuse as appropriate. However, by default the LOG_TIMEZONE value is empty - I only want this value to be populated when a specific timezone is required. However, as a result of defining this property but specifying no value I get the following error message at startup: 18:30:41,402 |-ERROR in ch.qos.logback.core.joran.action.PropertyAction - In <property> element, either the "file" attribute alone, or the "resource" element alone, or both the "name" and "value" attributes must be set. I assume from this error message that a property cannot have a NULL/empty value - i.e. this is expected behaviour? I guess I could remove/comment the property if it is not being used in the current configuration - although I'd rather not remove it from the configuration file completely, since its presence also acts as a visual reminder of which properties can be set. Regards, Shane

1 0

Re : Re: Assigning a log level to an appender
by Benoît Thiébault 15 Dec '12

15 Dec '12

Great! Exactly what I was looking for. Thanks Ralph Goers <rgoers(a)apache.org> a écrit : > >See http://logback.qos.ch/manual/filters.html#levelFilter > >Ralph > >On Dec 14, 2012, at 6:40 AM, Benoît Thiébault wrote: > >> Hi everyone, >> >> I have developed a custom LogBack appender and I would like it to receive only log messages of a given level. I don't want to hard code it in the class, but to set it in the XML configuration file. >> >> I thought something like this would work (but it doesn't): >> <root level="trace"> >> <appender-ref ref="FILE" /> >> <appender-ref ref="MyTraceAppender" /> >> <appender-ref ref="MyInfoAppender" level="info"/> >> </root> >> >> I also tried something like: >> <appender name="MyTraceAppender" class="org.test.MyLogger1"/> >> <appender name="MyInfoAppender" class="org.test.MyLogger2" level="info"/> >> >> No luck either. >> >> It seems only loggers can be assigned a threshold level. So I though about something like this: >> <logger name="test" level="info"> >> <appender-ref ref="MyInfoAppender" /> >> </logger> >> >> but this would only log messages sent by classes whose package is test. *... And I want to log anything. >> >> Can anyone help? >> >> Thanks >> Ben >> _______________________________________________ >> Logback-user mailing list >> Logback-user(a)qos.ch >> http://mailman.qos.ch/mailman/listinfo/logback-user > > >_______________________________________________ >Logback-user mailing list >Logback-user(a)qos.ch >http://mailman.qos.ch/mailman/listinfo/logback-user

1 0

Assigning a log level to an appender
by Benoît Thiébault 15 Dec '12

15 Dec '12

Hi everyone, I have developed a custom LogBack appender and I would like it to receive only log messages of a given level. I don't want to hard code it in the class, but to set it in the XML configuration file. I thought something like this would work (but it doesn't): <root level="trace"> <appender-ref ref="FILE" /> <appender-ref ref="MyTraceAppender" /> <appender-ref ref="MyInfoAppender" level="info"/> </root> I also tried something like: <appender name="MyTraceAppender" class="org.test.MyLogger1"/> <appender name="MyInfoAppender" class="org.test.MyLogger2" level="info"/> No luck either. It seems only loggers can be assigned a threshold level. So I though about something like this: <logger name="test" level="info"> <appender-ref ref="MyInfoAppender" /> </logger> but this would only log messages sent by classes whose package is test. *... And I want to log anything. Can anyone help? Thanks Ben

3 2

Flume appender for logback?
by DeCarlo, Thom 14 Dec '12

14 Dec '12

I haven't been able to find any recent comments about a logback appender for Apache Flume. There is a log4j appender, but I am already using logback and don't really want to change that. Has there been any development of an appender for flume? -- Thom DeCarlo

2 1

How to release appender resources on applicationend/undeployment
by jvm.pointer 14 Dec '12

14 Dec '12

Thank You for ultra fast replay. No it works like a charm. Just as I thought my assumptions were incorrect.

1 0

How to release appender resources on application end/undeployment
by jvm.pointer 14 Dec '12

14 Dec '12

Hi, I`m writing an appender that sends log messages to RabbitMQ. The appender extends ch.qos.logback.core.AppenderBase<ILoggingEvent>, obtains connection to RabbitMQ in start() method, sends a message to RabbitMQ in append(ILoggingEvent event) and releases that connection in the stop() method. The sending part works well but I`ve a problem with logback not calling appenders` stop() method when all desktop application` threads end or when the web app is undeployed. I don`t know if it`s a bug or (more probably) I`m missing something but the end result is that the stop() method is not being called, so the connection to RabbitMQ is not released and the desktop application never terminates and web applications cause memory leaks because of that hanging connection. For example tomcat reports the following: org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [/context_name] appears to have started a thread named [AMQP Connection 127.0.0.1:5672] but has failed to stop it. This is very likely to create a memory leak. I'll be grateful for any suggestions and tips on how to release appender resources on application end / undeployment. If it`s not my wrong assumption that logback should call stop() method to stop/deregister the appender I`ll fill in a JIRA issue.

2 1

Problems with 'logback.XML to Groovy' translator (website)
by Heinz Romirer | TAC GmbH 14 Dec '12

14 Dec '12

Hey there, just wanted to make a comment on the 'logback.XML to Groovy translator' webpage. It seems that ampersands ("&") are not HTML escaped an therefore, if you have some logical expression within your XML like this: <expression> marker != null && marker.contains("SMTP_TRIGGER") </expression> You will see the following error: // XML parsing failure // org.xml.sax.SAXParseException: The entity name must immediately follow the '&' in the entity reference. So you have to escape the ampersands yourself ("&"), like this: <expression> marker != null && marker.contains("SMTP_TRIGGER") </expression> To make it work. Just wanted to let you know ;)

1 0

can not populate the beagle view
by Junior 12 Dec '12

12 Dec '12

Hello all, i am quite new to logging. I find beagle cool and i want to use it. I have done what i found on the home page (i.e adding the tag <consolePlugin/>). But i can not populate the beagle view. I tried the following : <appender name="SOCKET" class="ch.qos.logback.classic.net.SocketAppender"> <port>4321</port> <remoteHost>localHost</remoteHost> <reconnectionDelay>10000</reconnectionDelay> <includeCallerData>true</includeCallerData> </appender> <root level="DEBUG"> <appender-ref ref="SOCKET"/> </root> This also don't work. Can someone give me an hint Thanks so much Junior

2 1

using "default" logback.properties and "override" logback.properties in logback.xml
by Gena Makhomed 08 Dec '12

08 Dec '12

Hello, All! is it possible with logback create "default" properties file with default settings, which can be overwritten in extra config? for example: /opt/tomcat/webapps/app/WEB-INF/classes/logback.xml /opt/tomcat/webapps/app/WEB-INF/classes/logback.properties - "default" (read only) properties, deployed from war-file /opt/tomcat/webapps.config/app/logback.properties - local "override" properties with same names as in "default" config. for example, in "default" logback.properties: log.level.spring = INFO log.flush = true log.rotate = 9 log.size = 1MB in "override" logback.properties: log.level.spring = DEBUG and logback.xml in this case will use ${log.level.spring} from "override" config. if "override" config not exists, or this property in "override" config not exists - then use "default" value from default config, for example, for ${log.size} or ${log.rotate} with Spring Framework this is possible, AFAIK/AFAIU. it will be very useful configure logback in same way. I am try many variants in logback.xml: <property resource="${catalina.base}/webapps.config/app/logback.properties" /> <property resource="logback.properties" /> <property resource="logback.properties" /> <property resource="${catalina.base}/webapps.config/app/logback.properties" /> and so on, but nothing works. can you help me? or this is not possible with logback at all?.. -- Best regards, Gena

1 0