- logback-user - mailman3.qos.ch

ch.qos.logback.access.pattern.ResponseHeaderConverter should be able to print all headers
by Aleksandr Dubinsky 20 Aug '15

20 Aug '15

Please copy the functionality of ch.qos.logback.access.pattern.RequestHeaderConverter to return all headers when no key is specified.

1 0

Stop & Start Appender?
by Martin Vávra 16 Aug '15

16 Aug '15

Hi, Short version: If the creation of the appender fails (permission denied), how do I explicitly re-attempt to create it when the problems with the permissions are resolved. I am using XML configuration. I would like to do this without re-starting my process. Longer version: I am using Logback on Android (logback-android). I am logging to a directory on the external storage, which means that if the user connects the device to the PC and enables mass-storage, the file system of the directory will be unmounted. If the application is started, while the directory is not available, I inform the user but since the loggers are defined as static fields ... private static final Logger LOG = LoggerFactory.getLogger(MyApplication.class); ... logback attempts to create the appender anyway and fails. Because of how Android works, the application process continues running even when the user leaves all screens of my application (for example goes to the home screen) and so the appender will never be re-attempted to be created. Is there some way to reset the appender from the config? If so, I could attempt to reset logback if necessary whenever the user enters the initial screen of my application. I tried to stop it using ... LoggerContext loggerContext = (LoggerContext) LoggerFactory.getILoggerFactory(); if (loggerContext != null) loggerContext.stop(); ... which seems to work fine but I don't seem to be able to re-start it: loggerContext.start() This does not seem to re-create the appender. Many thanks in advance for help. Martin

1 0

TeeFilter fullResponse not logging for particular response
by Scott Koranda 10 Aug '15

10 Aug '15

Hello, I am using Logback-access 1.1.2 with Jetty 9.2 and have configured the TeeFilter filter in order to capture both the full request and full response for a (non-production) webapp. For the most part the module is working as I expect. I see the full request logged and also the full response (except for images, which are sensibly rendered with [IMAGE CONTENTS SUPPRESSED]). For one particular response, however, the module is not logging the response contents. It is the response sent to the browser as part of a SAML2 HTTP-POST flow and it has the form <!DOCTYPE html> <html> <head> <meta charset="utf-8" /> </head> <body onload="document.forms[0].submit()"> <noscript> <p> <strong>Note:</strong> Since your browser does not support JavaScript, you must press the Continue button once to proceed. </p> </noscript> <form action="https://server.edu/Shibboleth.sso/SAML2/POST" method="post"> <div> <input type="hidden" name="RelayState" value="ss:mem:d0cc80da13dd9a454f8eea89fa76289e14b01a4022760603480766b7db5a9dfc"/> <input type="hidden" name="SAMLResponse" value="QUITE LONG ENCODED STRING"/> </div> <noscript> <div> <input type="submit" value="Continue"/> </div> </noscript> </form> </body> </html> For some reason only the HTTP headers for the response are logged and not the actual response content. The content is properly delivered to the browser so I do not think TeeFilter is interfering with the webapp. Any ideas on why this particular response is not logged? Is it because the "QUITE LONG ENCODED STRING" is roughly 11K in size (10,713 characters)? Thanks, Scott K

1 0

can't understand cast error
by pedro rijo 02 Aug '15

02 Aug '15

Hey, I'm not sure if this is a logback or slf4j issue, so sorry if it's a slf4j issue. My question is posted on stackoverflow ( http://stackoverflow.com/questions/31772577/org-slf4j-helpers-substitutelog… ) but I will paste it here: I've seen some questions very similar to this one ( http://stackoverflow.com/questions/15483309/org-slf4j-helpers-noploggerfact…)) but none of them received a good answer, or at least one that explained or solved this problem I was able to create a very small project (basically 2 Scala classes - each with a logger - and 2 test classes) with a similar structure to my real project where I found the problem. The example is available here: https://bitbucket.org/pedrorijo91/logger-exp The problem happens when I run `sbt test`, resulting in the following error: {14:43:41} (#47) ~/Desktop/logger-exp/log-exp@pedrorijo(master) $ sbt test Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=384m; support was removed in 8.0 [info] Loading global plugins from /Users/pedrorijo/.sbt/0.13/plugins [info] Loading project definition from /Users/pedrorijo/Desktop/git/scala/logger-exp/log-exp/project [info] Set current project to log-exp (in build file:/Users/pedrorijo/Desktop/git/scala/logger-exp/log-exp/) [info] HelloTest: [info] Exception encountered when attempting to run a suite with class name: HelloTest *** ABORTED *** [info] java.lang.ExceptionInInitializerError: [info] at HelloTest$$anonfun$1.apply$mcV$sp(HelloTest.scala:8) [info] at HelloTest$$anonfun$1.apply(HelloTest.scala:8) [info] at HelloTest$$anonfun$1.apply(HelloTest.scala:8) [info] at org.scalatest.Transformer$$anonfun$apply$1.apply$mcV$sp(Transformer.scala:22) [info] at org.scalatest.OutcomeOf$class.outcomeOf(OutcomeOf.scala:85) [info] at org.scalatest.OutcomeOf$.outcomeOf(OutcomeOf.scala:104) [info] at org.scalatest.Transformer.apply(Transformer.scala:22) [info] at org.scalatest.Transformer.apply(Transformer.scala:20) [info] at org.scalatest.FunSuiteLike$$anon$1.apply(FunSuiteLike.scala:166) [info] at org.scalatest.Suite$class.withFixture(Suite.scala:1122) [info] ... [info] Cause: java.lang.ClassCastException: org.slf4j.helpers.SubstituteLogger cannot be cast to ch.qos.logback.classic.Logger [info] at com.example.Hello$.<init>(Hello.scala:8) [info] at com.example.Hello$.<clinit>(Hello.scala) [info] at HelloTest$$anonfun$1.apply$mcV$sp(HelloTest.scala:8) [info] at HelloTest$$anonfun$1.apply(HelloTest.scala:8) [info] at HelloTest$$anonfun$1.apply(HelloTest.scala:8) [info] at org.scalatest.Transformer$$anonfun$apply$1.apply$mcV$sp(Transformer.scala:22) [info] at org.scalatest.OutcomeOf$class.outcomeOf(OutcomeOf.scala:85) [info] at org.scalatest.OutcomeOf$.outcomeOf(OutcomeOf.scala:104) [info] at org.scalatest.Transformer.apply(Transformer.scala:22) [info] at org.scalatest.Transformer.apply(Transformer.scala:20) [info] ... SLF4J: The following set of substitute loggers may have been accessed SLF4J: during the initialization phase. Logging calls during this SLF4J: phase were not honored. However, subsequent logging calls to these SLF4J: loggers will work as normally expected. SLF4J: See also http://www.slf4j.org/codes.html#substituteLogger SLF4J: com.example.Hello$ 14:43:52.846 [pool-6-thread-4-ScalaTest-running-WorldTest] INFO com.example.World$ - LOGGING [info] WorldTest: [info] - test [info] Run completed in 456 milliseconds. [info] Total number of tests run: 1 [info] Suites: completed 1, aborted 1 [info] Tests: succeeded 1, failed 0, canceled 0, ignored 0, pending 0 [info] *** 1 SUITE ABORTED *** [error] Error during tests: [error] HelloTest [error] (test:test) sbt.TestsFailedException: Tests unsuccessful [error] Total time: 1 s, completed Aug 2, 2015 2:43:52 PM but if I run each of the tests individually through: `sbt "testOnly HelloTest"` and `sbt "testOnly WorlTest"` I get no error. As far as I've seen this is not just a Scala issue, it seems that in Java is also possible to happen. Furthermore, I've read that during initialization the loggers are substituted by a Substitute Logger ( http://www.slf4j.org/codes.html#substituteLogger) But I can't understand: 1. why it only happens in tests, and when running both tests? 2. why it happens? 3. how to debug/solve this problem? As I said before, I've created a repository with a working example (working, meaning with the error happening) here: https://bitbucket.org/pedrorijo91/logger-exp -- Kind Regards, Pedro Rijo

2 1

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