November 2019 - logback-user

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

logback issue
by Yaer Dili 02 Nov '19

02 Nov '19

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

1 0

About FileAppender in Logback
by Hasan.Birol＠ing.com.tr 01 Nov '19

01 Nov '19

Dear Logback Team; Have a problem with logback . Have a logback.xml file find it below. Each thread has a single log file. However, cant recognize file is done or thread is done with looking the file. File is not locked or something (tried to lock the file by extending fileappender but cant succeed) . I don't would like to write a code to get content of file which I mean, dont wanna write a some symbol to find out file is done. I also used, triggeringPolicy cant succeed.. <appender name="SIFT" class="XXXXX.SiftingAppender"> <discriminator> <key>fileLocation</key> <defaultValue>${user.home}\start.log</defaultValue> </discriminator> <sift> <appender name="FILE-${fileLocation}" class="ch.qos.logback.core.FileAppender"> <file>${fileLocation}</file> <append>false</append> <encoder> <pattern>%msg%n</pattern> </encoder> </appender> </sift> </appender> I just would like to change extension when thread is done .log to .xml, or lock the file while end of the thread, or move the file end of the thread. Many many thanks. Have a nice day, Hasan Birol Yaz?l?m Dan??man? - Software Consultant Yaz?l?m Geli?tirme Sistemleri ve Platform Uygulamalar? B?l?m? - Software Development Frameworks and Platform Applications T: E: Hasan.Birol(a)ing.com.tr [http://image.ing.com.tr/EmailBanner/ING_LOGO_89x42px-02.png]<https://www.ing.com.tr> Kisiye ozel bu mesaj ve icerigindeki bilgiler gizlidir. ING bu mesajin icerigi ve ekleri ile ilgili olarak hukuksal hicbir sorumluluk kabul etmez.Yetkili alicilardan biri degilseniz, bu mesajin herhangi bir sekilde ifsa edilmesi, kullanilmasi, kopyalanmasi,yayilmasi veya mesajda yeralan hususlarla ilgili olarak herhangi bir islem yapilmasinin kesinlikle yasak oldugunu bildiririz.Boyle bir durumda lutfen hemen mesajin gondericisini bilgilendiriniz ve mesaji sisteminizden siliniz.Internet ortaminda gonderilen e-posta mesajlarindaki hata ve/veya eksikliklerden veya viruslerden dolayi mesajin gondericisi herhangi bir sorumluluk kabul etmemektedir.Tesekkur ederiz. The information contained in this communication may contain confidential or legally privileged information. ING doesn't accept any legal responsibility for the contents and attachments of this message. If you are not the intended recipient you are hereby notified that any disclosure, use, copying, distribution or taking any action in reliance on the contents of this information is strictly prohibited. If you have received this communication in error, please notify the sender immediately by responding to this e-mail and then delete it from your system. The sender does not accept any liability for any errors or omissions or any viruses in the context of this message which arise as a result of internet transmission. Thank you.

2 2

Appending an hourly log line when idle
by Mat Schaffer 01 Nov '19

01 Nov '19

Hello all, I have a service which sits idle sometimes for days and doesn't log anything. This sometimes creates confusion that the process (or log collection) isn't working, but it actually just doesn't have work to do. Is there any logback feature that I could leverage to send an hourly "MARK" if nothing has gone through the appender? Or should I just add something in the app itself? Thanks in advance! -Mat

2 2