- logback-user - mailman3.qos.ch

[Question]why logback hanging
by 森分俊祐 20 Jan '21

20 Jan '21

Dear all. Hi, I'm developer of java application, and I have a question about logback. Our application uses logback and it stopped processing several times during the log output. But this problem is not reproducible and difficult to solve, so please help us. This is the part of jstack I got when the problem occurred. --------------------------------------- "main" #1 prio=5 os_prio=0 tid=0x0000000001d33800 nid=0x2320 waiting on condition [0x0000000001d2e000] java.lang.Thread.State: WAITING (parking) at sun.misc.Unsafe.park(Native Method) - parking to wait for <0x00000000f9498208> (a java.util.concurrent.locks.ReentrantLock$NonfairSync) at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836) at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(AbstractQueuedSynchronizer.java:870) at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(AbstractQueuedSynchronizer.java:1199) at java.util.concurrent.locks.ReentrantLock$NonfairSync.lock(ReentrantLock.java:209) at java.util.concurrent.locks.ReentrantLock.lock(ReentrantLock.java:285) at java.util.concurrent.ArrayBlockingQueue.remainingCapacity(ArrayBlockingQueue.java:468) at ch.qos.logback.core.AsyncAppenderBase.isQueueBelowDiscardingThreshold(AsyncAppenderBase.java:134) at ch.qos.logback.core.AsyncAppenderBase.append(AsyncAppenderBase.java:126) at ch.qos.logback.core.UnsynchronizedAppenderBase.doAppend(UnsynchronizedAppenderBase.java:88) at ch.qos.logback.core.spi.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:48) at ch.qos.logback.classic.Logger.appendLoopOnAppenders(Logger.java:273) at ch.qos.logback.classic.Logger.callAppenders(Logger.java:260) at ch.qos.logback.classic.Logger.buildLoggingEventAndAppend(Logger.java:442) at ch.qos.logback.classic.Logger.filterAndLog_0_Or3Plus(Logger.java:396) at ch.qos.logback.classic.Logger.debug(Logger.java:523) --------------------------------------- Is this a bug? Or if this is not a bug, could you please tell me what was happening internally? =================================== [version information of our application] logback-core: 1.1.0 logback-classic:1.1.0 java8 =================================== Best regards

1 0

Logback EOL Versions?
by Symphoni Bush - NOAA Affiliate 16 Dec '20

16 Dec '20

Good morning, I am trying to figure out what versions of Logback are EOL and if so, what dates these versions became EOL. If there is somewhere this information is stored, please let me know. Thanks

1 0

Using external logback file
by Joud Kassem 10 Dec '20

10 Dec '20

Hello all, I need to use an external logback file for the logging configuration in my grails4 project. As I see the external logback file replaces completely the logback file in the project. Is there a way that it overrides it instead of replacing it? Which means the external logback file can be an extension to the internal one... we have this case that each customer has his own logging config but we still have our basic logging config that needs to be used for all customers so to avoid repeating it in the external logback file, it would be good if there's a way to override the internal logback file instead of replacing it.. Thanks in advance! All the best, Joud

1 0

Advice for dynamically adding loggers
by Norbert Kiesel 09 Dec '20

09 Dec '20

Hi, I want to dynamically add (and eventually remove again) loggers to a system. The idea is that based on specific events (e.g. a flag in a HTTP REST request header), the logs for this request are written to a separate file (in addition to writing to the usual log file). I also want to modify the log-level for this request to TRACE - ideally just for the messages written to the dedicated log file. Is configuring a SiftingAppender the correct approach for that? And does anyone have some sample code they could share? Any help/feedback is greatly appreciated! </nk> --- Norbert Kiesel Systems Architect, Engineering E: nkiesel(a)metricstream.com<mailto:sonia.sharma@metricstream.com> W: www.metricstream.com

2 1

No output written to file
by Donald McLean 05 Nov '20

05 Nov '20

Hi, I have this really confusing issue where the log file is created, but empty. Below is the configuration I'm using (which is almost exactly the one given in the logback manual in the section on file appenders). Any help or suggestions on how to debug this would be much appreciated. Donald <configuration> <timestamp key="bySecond" datePattern="yyyyMMdd'T'HHmmss"/> <appender name="FILE" class="ch.qos.logback.core.FileAppender"> <file>UnitTest-${bySecond}.log</file> <append>true</append>  <immediateFlush>true</immediateFlush>  <encoder> <pattern>%-4relative [%thread] %-5level %logger{35} - %msg%n</pattern> </encoder> </appender> <root level="TRACE"> <appender-ref ref="FILE" /> </root> </configuration>

1 0

Create a new log file only if the default one is open
by Olivier Cailloux 13 Oct '20

13 Oct '20

Dear list, I’d like to set up logback so that it always records the log to the file out.log, except when a process is already busy writing to out.log when my program start. (I expect such a process will simply be another instance of my program; when multiple instances run in parallel, I want to have multiple log files, one per instance.) I know that logback can be asked to create uniquely named files ( http://logback.qos.ch/manual/appenders.html#uniquelyNamed) but I do not want that: most of the time, only one instance of my program is running, in which case, it is fine to replace the log file, using the default name (out.log), instead of creating a new one at each run. I’d like to deviate from the default name only when the default one is busy. It is possible to detect (at least under Linux, but, I suppose, in other OSes as well) that a process has a file open, so this seems feasible, at least in principle; and it seems like a natural requirement for programs designed to allow parallel instances. I am surprised I didn’t see anything related to this in the logback manual. Is there a reason not to want what I want? I realize that a race condition could happen, in principle: if someone creates a second instance of my program immediately after the first one, the second one could decide to use out.log because that file is not yet open by the first one, ending up with both processes logging to the same file. I am ready to live with that risk. This question was also asked on SO ( https://stackoverflow.com/q/64184299) to no avail. -- Olivier

2 2

Logback-access pollutes logs with binary file content
by Gediminas Rimša 21 Sep '20

21 Sep '20

Hello. We have a Spring boot app exposing a RESTful API that runs on embedded Tomcat (latest versions) and uses logback-access (also latest 1.2.3). Recently I noticed that access logs include raw binary content of images/PDF files. Example from logs: > POST /projects/projectId/images HTTP/1.1 | status code: 200 | elapsed time: 664 | request: GIF89a� d �[[ most content ommitted ]]g�� w�� ; | response: {"id":"877f2338-293d-403b-99fb-09fc631ce7b3"} > GET /projects/projectid/images/877f2338-293d-403b-99fb-09fc631ce7b3 HTTP/1.1 | status code: 200 | elapsed time: 538 | request: | response: [IMAGE CONTENTS SUPPRESSED] What's the best way to configure suppression of request and response bodies (preferably based on content type)? Looking at the code, image content suppression happens in `ch.qos.logback.access.spi.AccessEvent#getResponseContent`, but it only checks if content type starts with `image/`. I also do not see any code for binary content suppression in `ch.qos.logback.access.spi.AccessEvent#getRequestContent`. I traced response image content suppression was added with this commit: https://github.com/qos-ch/logback/commit/69290e182f8db6589eadd5a3c485a37255… (all the way back in 2007). Our config: <configuration> <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender"> <filter class="ch.qos.logback.core.filter.EvaluatorFilter"> <evaluator class="ch.qos.logback.access.net.URLEvaluator"> <URL>/ping</URL> </evaluator> <OnMismatch>NEUTRAL</OnMismatch> <OnMatch>DENY</OnMatch> </filter> <encoder> <pattern>%requestURL | status code: %statusCode | elapsed time: %elapsedTime | request: %magenta(%requestContent) | response: %cyan(%responseContent)</pattern> </encoder> </appender> <appender-ref ref="STDOUT"/> </configuration> Thanks, Gediminas

1 0

RollingFileAppender not writing to disk...
by grosin＠cox.net 27 Jul '20

27 Jul '20

Using logback 1.2.3 in Spring Boot 2.3.2. What I'm seeing is that upon startup, the file is created with size 0 and doesn't flush. The default buffer size is 8k, no? Shouldn't it flush every 8k? If I close my app, then the logfile is written (about 17k). Logback-spring.xml is below. This is on Windows 10 x64. <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE configuration> <configuration> <include resource="org/springframework/boot/logging/logback/base.xml" /> <appender name="FILE" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>${LOG_PATH}/${LOG_FILE}.log</file> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <fileNamePattern>${LOG_PATH}/${LOG_FILE}.%d{yyyy-MM-dd}.log</fileNamePattern > <maxHistory>7</maxHistory> </rollingPolicy> <encoder> <pattern>${FILE_LOG_PATTERN}</pattern> </encoder> </appender> <root level="INFO"> <appender-ref ref="CONSOLE" /> <appender-ref ref="FILE" /> </root> </configuration>

1 0

Appender class name variable substitution
by Pavel Dionisev 07 Jul '20

07 Jul '20

Hey All! I’m trying to configure a custom appender, and I need to make appender class customisable via properties. In `ch.qos.logback.core.joran.action.AppenderAction` I see, that `className` is not substituted. It’s strange, cause just a few lines below we use `name` attribute to define appenderName, and we substitute it. So, questions are: 1. Why are we doing it this way? 2. What else can I do, to achieve my goal of having appender class externalised? Can you help, please? Context, I’m writing a library, that should do most of logging configurations automatically, and I would like users of the library to be able to extend some behaviour that is only available if we let them have custom appenders. `<appender class=“${myClass}" name=“some name”>` Using `logback 1.2.3` Cheers, Pavel

1 0

Avoid error on undefined JNDI variable
by Brian Xinger 01 Jul '20

01 Jul '20

Hi, sorry if this is a noob question. I really searched but could not find a way. I have a war-packaged application. I have configured logback to get an variable from JNDI with "insertFromJNDI" and placed the definition of that variable in a tomcat context XML. All of this works just fine when I deploy the application the way I want. Now, when running the application for tests or development, I would like to be able to have a default value for this variable. I can work with the :- operator when I define the log file name, but the problem I am having is that the missing JNDI parameter is causing an error and an abort of the application startup. The error shows: java.lang.IllegalStateException: Logback configuration error detected: ERROR in ch.qos.logback.classic.joran.action.InsertFromJNDIAction - [java:comp/env/instanceName] has null or empty value This happens with Eclipse and a Tomcat server managed by the IDE and on a Spring Boot embedded tomcat as well. I imagine many might reply suggesting ways to define the JNDI parameter in those situations, something I am open too and would appreciate, but deep down my question is: should the missing parameter really be an error? shouldn't it just issue a warning at most and not throw the exception, leaving the variable undefined just like any other env variable to be used with ":-"? Is that something that can be configured by any chance? Thanks!

1 0