July 2020 - logback-user - mailman3.qos.ch

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