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

Logback extensions missing debug info
by Aleksandr Dubinsky 27 Nov '15

27 Nov '15

Please include debugging info when compiling source code (in particular, Logback Spring extension), so that stepping through logback source code is possible when debugging.

3 2

Any way to turn off MDC inheritance?
by White, Joshua A A6IT 31 Aug '15

31 Aug '15

Hello, I am using logback version 1.1.3. I have a situation where the MDC is getting copied over to thread pools that I don't manage and filling my logs with log statements that contain MDC information that is no longer valid. Because I don't manage these thread pools, I am not able to copy the correct values to that thread pool when threads get used/re-used). Does anyone have a solution for this problem? -Joshua ------------------------------------------------------------------------------ CONFIDENTIALITY NOTICE: If you have received this email in error, please immediately notify the sender by e-mail at the address shown. This email transmission may contain confidential information. This information is intended only for the use of the individual(s) or entity to whom it is intended even if addressed incorrectly. Please delete it from your files if you are not the intended recipient. Thank you for your compliance. Copyright (c) 2015 Cigna ==============================================================================

2 2

What would cause "java.lang.NoClassDefFoundError: ch/qos/logback/classic/spi/ThrowableProxy" in long running daemon
by Fred Toth 31 Aug '15

31 Aug '15

Hi, We have multiple production processes that run 24 hours a day, 7 days a week. All use slf4j/logback and recently we had several of these (seemingly coincidentally) spew: java.lang.NoClassDefFoundError: ch/qos/logback/classic/spi/ThrowableProxy These are long running processes where nothing has changed recently. Obviously the logback jars are available, in the right place, etc. I'm stumped. There are some hints of some possible system related problem (like missing NFS mount, possibly). Does logback dynamically load the above class? Again, this error is out of the blue, from a process that may have been running for days or weeks. Any ideas? We're using version logback 1.0.13. If I google the above, there are some references to "Spring Boot" which we are not using. However, we are using Spring Integration, in case that matters. Any ideas? Thanks, Fred

5 8

Turn the log of android spring to debug
by Money Dai 24 Aug '15

24 Aug '15

Hi all, I have a Android project which is using logback+slf4j. I am able to get the logs of the my classes, which have slf4j loggers. But is it possible to enable the debug log for the 3-party library. Specifically, I want to turn the log of android spring to debug. I tried the configuration as below but it does not work: <appender name="file" class="ch.qos.logback.core.FileAppender"> <file>/data/data/com.example/files/log/foo.log</file> <encoder> <pattern>%d{HH:mm:ss.SSS} [%thread] %-5level %logger{36} - %msg%n</pattern> </encoder> </appender> <logger name="org.springframework" level="DEBUG" additivity="false"> <appender-ref ref="file" /> </logger> Any advice? -- Best regards, Jinge Dai

2 1

ch.qos.logback.access.AsyncAppender missing
by Aleksandr Dubinsky 20 Aug '15

20 Aug '15

Please implement AsyncAppender for logback-access.

1 0

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