June 2010 - logback-user - mailman3.qos.ch

Custom filter - ClassNotFoundException
by Florian Neumeyer 19 Jun '10

19 Jun '10

Hello, I'm trying to set up a simple configuration with different log files used depending on the logger name. Not wanting to use Joran, because this is a quite frequently accessed log, I tried to set up a custom logback filter for my Maven2/jetty7/JDK 1.6/logback-0.9.21 project. I added <filter class="de.mycorp.LoggerNameFilter" /> to my logback.xml, whereas de.mycorp is the package where all my other classes reside. LoggerNameFilter.java: [..] public class LoggerNameFilter extends Filter<ILoggingEvent> { @Override public FilterReply decide(ILoggingEvent event) { if (event.getLoggerName().equals("chat-message")) { return FilterReply.ACCEPT; } else { return FilterReply.DENY; } } } Unfortunately Maven throws an error: -ERROR in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Could not create component [filter] of type [de.mycorp.LoggerNameFilter] java.lang.ClassNotFoundException: de.mycorp.LoggerNameFilter at java.lang.ClassNotFoundException: de.mycorp.LoggerNameFilter at at java.net.URLClassLoader$1.run(URLClassLoader.java:202) at at java.security.AccessController.doPrivileged(Native Method) at at java.net.URLClassLoader.findClass(URLClassLoader.java:190) at at java.lang.ClassLoader.loadClass(ClassLoader.java:307) at at org.codehaus.classworlds.RealmClassLoader.loadClassDirect(RealmClassLoader.java:195) at at org.codehaus.classworlds.DefaultClassRealm.loadClass(DefaultClassRealm.java:255) at at org.codehaus.classworlds.DefaultClassRealm.loadClass(DefaultClassRealm.java:274) at at org.codehaus.classworlds.RealmClassLoader.loadClass(RealmClassLoader.java:214) at at java.lang.ClassLoader.loadClass(ClassLoader.java:248) at at ch.qos.logback.core.util.Loader.loadClass(Loader.java:110) Maybe there's even a better approach to this? Thanks a lot! Kind regards, Florian Neumeyer

1 1

Filter does not work on tomcat
by Sager, Patrick 16 Jun '10

16 Jun '10

Hello I'm using a filter expression to determine the format of my log message. When running the configuration within my JUnit tests, the filter works perfectly. However, when running on a tomcat v6.0 server (within eclipse), the filter gets ignored and all log entries are written twice. Here's the extract of my logback.xml file:  <appender name="ROLLING_LOG_WITH_SOURCE" class="ch.qos.logback.core.rolling.RollingFileAppender">  <filter class="ch.qos.logback.core.filter.EvaluatorFilter"> <evaluator> <expression>(mdc.get("source") != null) && !((String)mdc.get("source")).isEmpty()</expression> </evaluator> <OnMatch>ACCEPT</OnMatch> <OnMismatch>DENY</OnMismatch> </filter> <file>/etc/foe/logs/LogFile.log</file> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">  <fileNamePattern>TestLogFile-%d{yyyy-MM}.%i.zip</fileNamePattern> <maxHistory>12</maxHistory> <timeBasedFileNamingAndTriggeringPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP">  <maxFileSize>1MB</maxFileSize> </timeBasedFileNamingAndTriggeringPolicy> </rollingPolicy> <encoder> <pattern>%-5level %date{yyyy-MM-dd HH:mm:ss.SSS} [%thread] [%X{source}] %msg%n</pattern> </encoder> </appender>  <appender name="ROLLING_LOG_WITHOUT_SOURCE" class="ch.qos.logback.core.rolling.RollingFileAppender">  <filter class="ch.qos.logback.core.filter.EvaluatorFilter"> <evaluator> <expression>(mdc.get("source") != null) && !((String)mdc.get("source")).isEmpty()</expression> </evaluator> <OnMatch>DENY</OnMatch> <OnMismatch>ACCEPT</OnMismatch> </filter> <file>/etc/foe/logs/LogFile.log</file> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">  <fileNamePattern>TestLogFile-%d{yyyy-MM}.%i.zip</fileNamePattern> <maxHistory>12</maxHistory> <timeBasedFileNamingAndTriggeringPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP">  <maxFileSize>1MB</maxFileSize> </timeBasedFileNamingAndTriggeringPolicy> </rollingPolicy> <encoder> <pattern>%-5level %date{yyyy-MM-dd HH:mm:ss.SSS} [%thread] [%file:%line] %msg%n</pattern> </encoder> </appender> Is this a known issue, that LogBack does not support filters under tomcat? Thanks for any help -- Patrick

2 1

Glassfish v3 and logback.xml ignored
by Mike Weeda 09 Jun '10

09 Jun '10

Hi, After moving from NetBeans 6.5 / Tomcat 6.0.18 to NetBeans 6.8 / GlassFish v3, my logback.xml file seems to be ignored. Messages now appear in the GlassFish console, but not in the file configured in logback.xml. In fact, the file configured in logback.xml is not even created under GlassFish. Aside from logback.xml being ignored, there are no other issues or errors. This link https://glassfish.dev.java.net/issues/show_bug.cgi?id=11683 discusses a similar situation, but it is not clear how the fix described there is applicable to my situation. My logback.xml file is in the <project>/src directory. Some information from the web suggests that perhaps it needs to be somewhere else, but nothing is very definite. This behavior occurs under both logback 9.14 / slf4j 1.5.6, and logback 9.21 / slf4j 1.6.0. Any suggestions would be appreciated. Thanks. Regards, Mike

1 0

Where did WriterAppender go?
by HamletDRC 09 Jun '10

09 Jun '10

I was using LogBack 0.9.9 and the WriterAppender class. In my upgrade to 0.9.21 the class disappeared. Where did it go? ----- -- Hamlet D'Arcy -- View this message in context: http://old.nabble.com/Where-did-WriterAppender-go--tp28776288p28776288.html Sent from the Logback User mailing list archive at Nabble.com.

2 2

JMSAppender NameNotFoundException
by buzzterrier 08 Jun '10

08 Jun '10

I am trying to get the JMSAppender to work, without success The producer app has the following appender <appender name="JMS" class="ch.qos.logback.classic.net.JMSQueueAppender"> <InitialContextFactoryName> org.apache.activemq.jndi.ActiveMQInitialContextFactory </InitialContextFactoryName> <ProviderURL>tcp://xw8-025:61616</ProviderURL> <QueueConnectionFactoryBindingName>ConnectionFactory</QueueConnectionFactoryBindingName> <QueueBindingName>metrics.queue</QueueBindingName> </appender> The consumer app is wired for JMS using Spring: <bean id="metricsMessageListener" class="foo.bar.metrics.service.MetricsMessageListener" p:metricsService-ref="metricsServiceImpl"/>  <bean id="jmsContainer" class="org.springframework.jms.listener.DefaultMessageListenerContainer"> <property name="connectionFactory" ref="connectionFactory"/> <property name="destination" ref="metricsDestination"/> <property name="messageListener" ref="metricsMessageListener" /> </bean> <bean id="metricsDestination" class="org.apache.activemq.command.ActiveMQQueue"> <constructor-arg index="0" value="metrics.queue"/> </bean> <bean id="connectionFactory" class="org.apache.activemq.ActiveMQConnectionFactory" p:brokerURL="tcp://xw8-025:61616" /> When I start the producer webapp I get: 15:01:24,571 |-ERROR in ch.qos.logback.classic.net.JMSQueueAppender[JMS] - Could not find name [metrics.queue]. 15:01:24,571 |-ERROR in ch.qos.logback.classic.net.JMSQueueAppender[JMS] - Error while activating options for appender named [JMS]. javax.naming.NameNotFoundException: metrics.queue at javax.naming.NameNotFoundException: metrics.queue at at org.apache.activemq.jndi.ReadOnlyContext.lookup(ReadOnlyContext.java:225) at at javax.naming.InitialContext.lookup(InitialContext.java:392) If I wire in a spring JMS template on the producer side, it connects to the metrics.queue without issue. Kind of stumped. Back to using the DBAppender, but was hoping that someone might have an idea. ----- Buzzterrier http://buzzterrier.blogspot.com/ View my blog: Ordinary Average Developer... -- View this message in context: http://old.nabble.com/JMSAppender-NameNotFoundException-tp28823755p28823755… Sent from the Logback User mailing list archive at Nabble.com.

1 0

Trouble with MaxHistory when using TimeBasedRollingPolicy
by Jesse Bexten 02 Jun '10

02 Jun '10

Hello group! Our company has been a long time user of log4j and JCL and recently I have discovered Logback and SLF4J. I am extremely pleased with the quality of this product thus far. SLF4j immediately resolves the class loader trouble we had been having with our applications using log4j under WAS. Moving forward with this project I had hoped to switch our logging implementation to logback using the RollingFileAppender and TimeBasedRollingPolicy. It exactly meets a new requirement I've been given regarding automatic compression and deletion of archived logs. Here's the trouble. The archive remover is a little to specific about which files it deletes at rollover. It computes the name of the file to be deleted based on the current time regardless of the age of the oldest file. So for example my log file pattern is ${AppLogPath}\app.%d{yyyy-MM-dd-HH-mm}.zip max history is 5. my log directory contains app.2010-06-02-10-29.zip app.2010-06-02-10-30.zip app.2010-06-02-10-31.zip app.2010-06-02-10-32.zip app.2010-06-02-10-33.zip If there is no logging activity until 10:37 then DefaultArchiveRemover subtracts the 6 minutes from the current time and computes the name of the file to be deleted as forms.2010-06-02-10-31.zip. The older files app.2010-06-02-10-29.zip, app.2010-06-02-10-30.zip will never be deleted because the rollover time that would have deleted them has already past. I was testing with a 1 minute rollover period which I know is unrealistic,however we still split our logs hourly for our applications. During business hours this problem will not affect us, but we usually have several hours of inactivity later in the evening. Thus we would have hours in the day when rollover doesn't occur and some of our archived logs will not be cleaned up. I would like to see a solution that deletes the oldest entry at rollover or all files older than a certain threshold, or at least some solution or option that won't leave some logs stranded. One final note we have been achieving the automatic deletion of logs using a custom log4j appender that reads the last modified date of the file and deletes all files older than a specified age that meet the pattern of our log file. I was hoping to be able to replace this with a more efficient method using logback. Thanks for any help. Sorry my first post is such a long one, but I have see this issue documented in other posts and a few JIRA logs but they do not contain the amount detail I have given which is perhaps why they have been addressed. I feel this a significant problem which makes the maxhistory portion of TimeBasedRollingPolicy unusable for most purposes. Jesse

1 0

missing end of line character
by Rostislav Matl 01 Jun '10

01 Jun '10

Hi, I'm using logback 0.9.21. Unfortunately it prints all messages to single line, there is no end of line character, even wrong one. I've got the pattern set right AFAIK: <pattern>%d{HH:mm:ss.SSS} %-5level %class (%thread) [%logger{36}] -- %msg%n</pattern> I run it on Windows 7 at the time. Thanks for any hint, R.Matl

1 0