- logback-user - mailman3.qos.ch

Some loggers do not display anything
by Martial Lapeyre 17 Mar '20

17 Mar '20

Hello, I have created the following configuration <?xml version="1.0" encoding="UTF-8" ?> <configuration scan="true"> <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender"> <encoder> <pattern>%d{HH:mm:ss.SSS} [%-18.18thread] %highlight(%-5level) %-30.30logger - %msg%n</pattern> </encoder> </appender> <logger name="events.B" level="trace"> <appender-ref ref="STDOUT"/> </logger> <logger name="events.A" level="trace" > <appender-ref ref="STDOUT"/> </logger> <root level="info"/> </configuration> When i use the following main public static void main(String[] args) throws InterruptedException { Logger loggerA = LoggerFactory.getLogger("events.A"); Logger loggerB = LoggerFactory.getLogger("events.B"); loggerA.trace("I am A"); loggerB.trace("I am B"); Thread.sleep(1000); } It displays only 15:22:11.746 [main ] TRACE events.A - I am A Process finished with exit code 0 I do not understand why the entry from the second logger is not displayed Note: I use the system property logback.configurationFile for setting the configuration file. Thank you for your help. -- Martial Lapeyre Courriel: lapeyre.martial(a)gmail.com Tél: 06.75.15.31.72

1 0

RollingFileAppender maxFileSize doesn't work properly
by Mouhammad Kahwaji 01 Mar '20

01 Mar '20

Hi all, I have a RollingFileAppender defined as follows: appender("test", RollingFileAppender) { file = "${logDir}/logFile.log" encoder(PatternLayoutEncoder) { pattern = log_pattern_prod } rollingPolicy(FixedWindowRollingPolicy) { fileNamePattern = "${logDir}/logFile%i.log" minIndex = 1 maxIndex = 3 } triggeringPolicy(SizeBasedTriggeringPolicy) { maxFileSize = FileSize.valueOf("10KB") } } root(DEBUG, ['test']) I'm testing it, I get 3 archived files but the size of the files is not limited to 10KB as you can see in the attachment Why is this happening? The size of the files shouldn't exceed 10KB, how rolling is working in this case? Thanks in advance, Mhd

2 3

Logback Threads Blocked: https://jira.qos.ch/browse/LOGBACK-1421?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel
by Prabhash Rathore 03 Feb '20

03 Feb '20

Hello, I have run into the same issue as documented in this Jira: https://jira.qos.ch/browse/LOGBACK-1421?page=com.atlassian.jira.plugin.syst… I notice most application threads are blocked with following stack trace. Looking at Jira, it seems fix for this was planned to be included as part of 1.3.0-alpha6 but I didn't find this release tag on Logback Github repo. Are there any plans to have a fix for this issue? I see we run into issue under high load. We run Java 11 on Linux RHEL 7. "ForkJoinPool.commonPool-worker-705" #29535 daemon prio=10 os_prio=0 cpu=11.37ms elapsed=343.90s tid=0x00007fd5dc197590 nid=0x2ad83 waiting for monitor entry [0x00007fccdadeb000] java.lang.Thread.State: BLOCKED (on object monitor) at ch.qos.logback.core.util.CachingDateFormatter.format(CachingDateFormatter.java:45) - waiting to lock <0x000008206586ad18> (a ch.qos.logback.core.util.CachingDateFormatter) at ch.qos.logback.classic.pattern.DateConverter.convert(DateConverter.java:61) at ch.qos.logback.classic.pattern.DateConverter.convert(DateConverter.java:23) at ch.qos.logback.core.pattern.FormattingConverter.write(FormattingConverter.java:36) at ch.qos.logback.core.pattern.PatternLayoutBase.writeLoopOnConverters(PatternLayoutBase.java:115) at ch.qos.logback.classic.PatternLayout.doLayout(PatternLayout.java:141) at ch.qos.logback.classic.PatternLayout.doLayout(PatternLayout.java:39) at ch.qos.logback.core.encoder.LayoutWrappingEncoder.encode(LayoutWrappingEncoder.java:115) at ch.qos.logback.core.OutputStreamAppender.subAppend(OutputStreamAppender.java:230) at ch.qos.logback.core.rolling.RollingFileAppender.subAppend(RollingFileAppender.java:235) at ch.qos.logback.core.OutputStreamAppender.append(OutputStreamAppender.java:102) at ch.qos.logback.core.UnsynchronizedAppenderBase.doAppend(UnsynchronizedAppenderBase.java:84) at ch.qos.logback.core.spi.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:51) at ch.qos.logback.classic.Logger.appendLoopOnAppenders(Logger.java:270) at ch.qos.logback.classic.Logger.callAppenders(Logger.java:257) at ch.qos.logback.classic.Logger.buildLoggingEventAndAppend(Logger.java:421) at ch.qos.logback.classic.Logger.filterAndLog_0_Or3Plus(Logger.java:383) at ch.qos.logback.classic.Logger.info(Logger.java:579) Thank you for your help! Prabhash Rathore

1 0

MDC and GDPR
by dominique.villard＠orange.com 20 Jan '20

20 Jan '20

Hi, I don't know if this topic has already been addressed (found no reference). With MDC some applicative logs may leak personal data. Would it make sense to add a putDigest method to the MDC class that would put a digest (irreversible) of the 'val' parameter ? Thx. /DV _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.

2 1

Filter at the end
by A N 17 Dec '19

17 Dec '19

Hi, I want to create a logging system in QA world. First scenario, if test passed, then I want to print only information like TEST_STARTED: <test name> TEST_SUCCESSFUL: <test name> Second scenario, if test failed, then I want to print everything that was captured like TEST_STARTED: <test name> INFO: blah blah DEBUG: blah blah ERROR: blah blah Am I misunderstanding that logback filter marker event at the time it was generated? I am looking to filter out events at certain point in time, not just when a event is generated? Any help is appreciated!! Thanks

1 0

has problem with 'multi process append log to one file', need help!
by Aruforce 28 Nov '19

28 Nov '19

Hi： same as the title; recently,Our system has been transformed into a distributed system with all log append to same file; （ELK need more machine,can not take it） but only one service can log success ,(others all failed,but can lot catalina.out) <configuration debug="true">, but Unable to track problem with logback self logs（has no log about filelock）; reviewed Code `FileAppender.safeWrite()` ,it has file lock ; here is some linxu echos , may help; thanks a lot!

2 1

Unsubscribe
by Quentin Campbell 20 Nov '19

20 Nov '19

On Wed, Nov 20, 2019, 6:00 AM <logback-user-request(a)qos.ch> wrote: > Send logback-user mailing list submissions to > logback-user(a)qos.ch > > To subscribe or unsubscribe via the World Wide Web, visit > http://mailman.qos.ch/mailman/listinfo/logback-user > or, via email, send a message with subject or body 'help' to > logback-user-request(a)qos.ch > > You can reach the person managing the list at > logback-user-owner(a)qos.ch > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of logback-user digest..." > > > Today's Topics: > > 1. logback 1.3.0-alpha5 NPE (Rolf Schumacher) > 2. Re: logback 1.3.0-alpha5 NPE (Ceki) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 19 Nov 2019 23:23:24 +0100 > From: Rolf Schumacher <rolf(a)august.de> > To: logback-user(a)qos.ch > Subject: [logback-user] logback 1.3.0-alpha5 NPE > Message-ID: <1d91697c-8bc3-db36-d40b-91aeea319061(a)august.de> > Content-Type: text/plain; charset="utf-8"; Format="flowed" > > I've reduced my problem to a very simple maven project, located here as > zip-file: > > /https://www.file-upload.net/download-13793489/deeschd.zip.html/ > > doing a /mvn test/ runs fine with Java-11. > > uncommenting > > /// requires transitive ch.qos.logback.classic;/ > > in /src/main/jave/module-info.java/ > > and running /mvn test/ again leads to an NPE. > > > Why does the mentioning of an existing module in /module-info.java /lead > to an NPE? > // > > This source code is a reduction of an existing project. It has been has > been moved from Java-8 to Java-11. > > The source code contains a /LogbackConfigurator.java/ (implementing > ch.qos.logback.classic.spi.Configurator). > > /LogbackConfigurator.java/ needs /ch.qos.logback.classic/ in > /module-info.java/ in order to compile. > > Am I doing something wrong, or is this a bug? > > Any help welcome > > Rolf > >

1 0

logback 1.3.0-alpha5 NPE
by Rolf Schumacher 19 Nov '19

19 Nov '19

I've reduced my problem to a very simple maven project, located here as zip-file: /https://www.file-upload.net/download-13793489/deeschd.zip.html/ doing a /mvn test/ runs fine with Java-11. uncommenting /// requires transitive ch.qos.logback.classic;/ in /src/main/jave/module-info.java/ and running /mvn test/ again leads to an NPE. Why does the mentioning of an existing module in /module-info.java /lead to an NPE? // This source code is a reduction of an existing project. It has been has been moved from Java-8 to Java-11. The source code contains a /LogbackConfigurator.java/ (implementing ch.qos.logback.classic.spi.Configurator). /LogbackConfigurator.java/ needs /ch.qos.logback.classic/ in /module-info.java/ in order to compile. Am I doing something wrong, or is this a bug? Any help welcome Rolf

2 1

Doubt on exception as last parameter behavior
by Fabio Cechinel Veronez 14 Nov '19

14 Nov '19

Hello all, I have a question regarding the behavior of an exception as last parameter. It is very well known that an exception placed as last parameter will have a special handling, having its stack trace printed available in the final output. Ex: ``` logger.warn("Printing a value {} with exception's stacktrace", 23, new Exception("some message")); ``` Outputs something like: ``` 11:35:01.696 [main] WARN App - Printing a value 23 with exception's stacktrace java.lang.Exception: some message at App.main(App.java:7) ~[classes/:na] ``` My question is: what if the message string contains an interpolation expression for that exception parameter? Example: ``` logger.warn("Printing a value {} with an inlined exception {}", 23, new Exception("some message")); ``` Personally I would expect that in this case the exception would be printed just like any other regular parameter, not having its stracktrace printed. Basically, I would expected an exception to have a special handling only when it is the "+1" parameter. It seems to have been the case up to logback-classic:1.0.13 (slf4j-api:1.7.5). Using this version the log statement above prints: ``` 11:35:01.699 [main] WARN App - Printing a value 23 with an inlined exception java.lang.Exception: some message ``` While using logback-classic:1.2.3 (slf4j-api:1.7.25) it prints: ``` 11:38:02.150 [main] WARN App - Printing a value 23 with an inlined exception {} java.lang.Exception: some message at App.main(App.java:8) ``` Apparently the behaviour changed from logback:1.1.0 onwards. Is this a new expected behavior? Unfortunately I couldn't find in the documentation where the expected behavior of this particular situation is explained in more details. So I thought it to be a bit ambiguous. If there one, please, let me know. Thanks in advance. -- Fabio Cechinel Veronez

2 1

Fwd: logback issue
by Yaer Dili 03 Nov '19

03 Nov '19

---------- Forwarded message --------- From: Yaer Dili <yedili(a)thoughtworks.com> Date: Sat, Nov 2, 2019 at 6:22 PM Subject: Re: [logback-user] logback issue To: Ceki <ceki(a)qos.ch> thank you for your reply Ceki, we also believe that logback design in this way, but in our case logback stop our application from successfully launch, I added some details in the following section and you may be able to reproduce this issue we configure all the logback configurations in the `logback-spring.xml` file like this <?xml version="1.0" encoding="UTF-8"?> <configuration> <include resource="org/springframework/boot/logging/logback/defaults.xml"/> <appender name="console" class="ch.qos.logback.core.ConsoleAppender"> <encoder> <pattern> %d{dd-MM-yyyy HH:mm:ss.SSS} %magenta([%thread]) %highlight(%-5level) %logger %M %line - [traceID: %X{X-B3-TraceId}] - [RequestId: %X{RequestId}] - [ClientId: %X{ClientId}] - %message %exception{full} %n </pattern> </encoder> </appender> <springProfile name="local,dev"> <root level="DEBUG"> <appender-ref ref="console"/> </root> </springProfile> as you can see from the above code snippet we create an appender and attach this to local, dev spring profile. after this, we try to create a new spring profile called dev2 and activate this profile by the following configuration in `application.yml` file profiles: active: dev2 so we have three environment property file in our project [image: image.png] after we try to start our application, it failed to start without any error message, we only can see the following message no other output [image: image.png] and as I said in the previous email we can fix this by adding the `dev2` env profile name to the logback configuration file like this <springProfile name="local,dev,dev2"> at this point, we are not sure whether we encounter this issue, is it because of our configuration or is it an existing issue of logback? Regards, yaer On Sat, Nov 2, 2019 at 12:07 PM Ceki <ceki(a)qos.ch> wrote: > Hi Yaer, > > Logback is designed to isolate the application from any errors that it > (logback) might encounter. I very much doubt that logback would prevent > an application from starting. Do you have any further details to provide? > > Best, > -- > Ceki Gülcü > > On 02.11.2019 04:46, Yaer Dili wrote: > > hi there, > > we are using logback in our spring boot application and all our logback > > related configuration is in the `logback-spring.xml` file ad we > > configure `springProfile` for different environments in the xml file > > like this > > > > <springProfile name="local,dev"> > > <root level="DEBUG"> > > <appender-ref ref="console"/> > > </root> > > </springProfile> > > > > after this configuration if we want to add other environment property, > > it must be added to this `springProfile` first otherwise our application > > failed to start with newly added property file. > > > > for example if I just add a new property file called > > `application-uat.yml` and directly start the application with this > > property file, our application failed to start. for fixing this I need > > to add this property name in the `SpringProfile` configuration like this > > `<springProfile name="local,dev,uat">` > > > > we think logback rather than directly block our app start should have a > > default value for newly added property file, do you have anything to > > share with us? thank you > > > > regards, > > yaer > > > > _______________________________________________ > > logback-user mailing list > > logback-user(a)qos.ch > > http://mailman.qos.ch/mailman/listinfo/logback-user > > > > -- > -- > Ceki Gülcü >

1 0