July 2015 - logback-user - mailman3.qos.ch

Java 9 compatibility with Logback
by Christopher BROWN 29 Jul '15

29 Jul '15

Hello, I've just run the "jdeps" tool against logback classic 1.1.2, and it identified an incompatible JDK9 dependency upon "sun.reflect". Is it planned to fix this, to remain fully compatible? Thanks, Christopher

1 0

Character encoding problem with ch.qos.logback.access.servlet.TeeFilter
by Christopher Holt 27 Jul '15

27 Jul '15

Hello, After a long process of elimination, I've discovered that the TeeFilter (ch.qos.logback.access.servlet.TeeFilter) is causing problems with page encoding. Logback: 1.0.13, Tomcat: 7.0.61, Java: 1.7_0_51 (and 1.6.0_39). At the top of my jsp pages I have this line: <%@ page language="java" contentType="text/html; charset=UTF-8" pageEncoding="UTF-8"%> setting the character set to UTF-8. When I have the TeeFilter installed in the web.xml, unicode characters do not encode correctly. The resulting html page claimed to be UTF-8 in its header, but did not appear correctly when interpreted as UTF-8 or iso-8859-1. (I don't know what encoding it was actually using). For now, my workaround is to remove the TeeFilter since my dependence on it is very low, but I would like to be able to add it back if needed. Another detail about this that confuses me even more, is that it would fail 100% of the time when tomcat was first started. But if I redeployed the .war files, it would start working and the pages would be encoded correctly. (This made tracking the problem down a much longer process). Has anyone else run into this or is there a setting on the TeeFilter to specify an encoding? -- Chris Holt Director of Development Healthcare Control Systems (877)877-8795 ext 115

1 0

SyslogAppender: "Will try to reconnect later"
by Chris Martin 27 Jul '15

27 Jul '15

I'm perusing SyslogAppenderBase and noticed something that seems wrong. If createOutputStream throws SocketException, the warning says "Failed to bind to a random datagram socket. Will try to reconnect later." But it doesn't increment errorCount, super.start gets called, and as far as I can tell the `append` method will then throw NullPointerException attempting to dereference `sos`. I see no code that tries to reconnect as the warning message says it should. Does this look like a mistake, or am I misreading something?

1 0

How to configure Logback to filter out anything that does not have a specific marker
by Robert Krüger 26 Jul '15

26 Jul '15

This must be a simple thing, but I am not getting it. I have a marker, say "performance" that I use when logging. Also, I often use isDebugEnabled() etc. when log messages become expensive to build. Now I want to configure logback that I can do these two things: 1) Log all statements in Logger foo.Bar that are debug or higher and use the marker "performance" 2) Log all statements across all Loggers that use the marker "performance" To achieve 1) I tried this: <turboFilter class="ch.qos.logback.classic.turbo.MarkerFilter"> <Marker>index-control-flow</Marker> <OnMatch>ACCEPT</OnMatch> </turboFilter> <logger name="foo.Bar" level="DEBUG"/> Then also all log messages that are not tagged with this marker appear in the log. To achieve 2) I tried omitting the logger line above and got only log messages with the marker, however, all log messages protected by a check of isDebugEnabled() are omitted. I must be missing a general concept here. Thanks in advance, Robert

2 2

How to log messages from different packages to different appenders with logback
by amit shah 22 Jul '15

22 Jul '15

I am trying to log messages from third party libraries to different file with the below logback extract <appender name="CONSOLE" class="ch.qos.logback.core.ConsoleAppender"> <encoder> <pattern>%d{HH:mm:ss.SSS} %-5level [%.45(%thread)][%.32(%logger{32})] %msg%n</pattern> </encoder> </appender> <timestamp key="byDay" datePattern="yyyyMMdd'T'HHmmss"/> <appender name="FILE" class="ch.qos.logback.core.FileAppender"> <file>F:\v1\devel\logs\app-${byDay}.txt </file> <append>true</append> <encoder> <pattern>%d{HH:mm:ss.SSS} %-5level [%.45(%thread)][%.32(%logger{32})] %msg%n</pattern> </encoder> </appender>  <root level="INFO"> <appender-ref ref="CONSOLE"/> </root>  <logger name="org.hibernate" level="TRACE" additivity="false"> <appender-ref ref="FILE"/> </logger> I want hibernate TRACE level logs to be logged to a file while other INFO messages should go to the console. The above xml config isn't working for me. Nothing gets logged to the file. Any suggestions? Thanks, Amit

2 2

Failover/reconfigure JMSAppender on JNDI InitialContext
by Rutger Saalmink 20 Jul '15

20 Jul '15

Hi, I am running into an issue when using the JMSQueueAppender on Weblogic application server, where application code talks to SLF4j with Logback as the underlying logging framework (core+classic).Below my logback.xml configuration. In this scenario, SLF4j is being initialized before the JNDI context is available from Weblogic, thus resulting an error like:1:01:19,348 |-ERROR in ch.qos.logback.classic.net.JMSQueueAppender[JMSQueue] - Error while activating options for appender named [JMSQueue]. javax.naming.NoInitialContextException: JNDI subsystem is not ready for use at javax.naming.NoInitialContextException: JNDI subsystem is not ready for use at weblogic.jndi.WLInitialContextFactoryDelegate.newLocalContext(WLInitialContextFactoryDelegate.java:569)... stacktrace omitted ... Is there any reconnection/retrycount property that can be set on the JMSQueueAppender (can't find documentation about it online manual)? Or any other way of re-initialization? (N.b. a workaround would be: define scan="true" scanPeriod="10 seconds", perform a unix 'touch' on logback.xml manually, which will reconfigure the appender. But by then we might have missed a lot of critical logging not being sent to the JMS queue). Copy of JMS appender definition in logback.xml: <appender name="JMSQueue" class="ch.qos.logback.classic.net.JMSQueueAppender"> <InitialContextFactoryName> weblogic.jndi.WLInitialContextFactory </InitialContextFactoryName> <ProviderURL>t3://localhost:7001</ProviderURL> <QueueConnectionFactoryBindingName> weblogic.jms.ConnectionFactory </QueueConnectionFactoryBindingName> <QueueBindingName>jms/foo/barQueue</QueueBindingName> </appender>.... <logger name="foo.bar.baz" level="INFO"> <appender-ref ref="JMSQueue"/> </logger> Thanks in advance! Kind regards, Rutger

1 0