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

LOGBACK-1742 cause compatibility issues when use custom LoggerContext
by 胡子杰(致节) 27 Jul '23

27 Jul '23

Dear sir： I update logback form 1.4.7 to 1.4.8, then I find the logback logger could'n print log, the console print: LOGBACK: No context given for ch.qos.logback.core.ConsoleAppender[CONSOLE] I found an NPE (NullPointerException) here： Then I found this pr: https://github.com/qos-ch/logback/commit/9c318804cf8bbc27eac20513887fa42649… <https://github.com/qos-ch/logback/commit/9c318804cf8bbc27eac20513887fa42649… >. In my case, the LogContext is not created by LogbackLoggerSpaceFactory, it's created by myself. so the MDCAdapter in loggerContext is null, then cause NullPointerException. I think this is an incompatible change, as some users may customize LogContext in certain scenarios, which will cause the custom LogContexts to be unusable. I hope LogBack can consider fixing this compatibility issue, for example, to ensure backward compatibility by obtaining MDCAdapter from MDC when MDCAdapter obtained from LogContext is null. Thanks

1 0

size based rollback unexpected behaviour
by Hakan Küçük 20 Jul '23

20 Jul '23

I have a basic spring boot application with the logback.xml below <configuration> <appender name="ROLLING" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>mylog.txt</file> <rollingPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedRollingPolicy"> <fileNamePattern>mylog-%d{yyyy-MM-dd}.%i.txt</fileNamePattern> <maxFileSize>1MB</maxFileSize> <maxHistory>60</maxHistory> <totalSizeCap>1GB</totalSizeCap> </rollingPolicy> <encoder> <pattern>%d{yyyy-MM-dd HH:mm:ss.SSS} %-4relative [%thread] %-5level %logger{35} - %msg%n</pattern> </encoder> </appender> <root level="DEBUG"> <appender-ref ref="ROLLING"/> </root> </configuration> I created logs with the following code to test the rolling. @Slf4j @SpringBootApplication public class LogbackApplication implements CommandLineRunner { public static void main(String[] args) { SpringApplication.run(LogbackApplication.class, args); } @Override public void run(String... args) throws Exception { for (int i = 0; i < 100000; i++) { log.debug("This is DEBUG"); log.info("This is INFO"); log.warn("This is WARN"); } } } I observed a log file of more than 25 MB. It is not rolling. If I put some sleep statements inside logging, it rolls. Is it a bug? or am I misconfiguring it? or expected behavior because of performance reasons?

1 0

Can LoggerContext take an MDCAdapter instead of a LogbackMDCAdapter
by jim-logback＠spudsoft.co.uk 07 Jul '23

07 Jul '23

Hi, At the moment LoggerContext works specifically with the LogbackMDCAdapter. This makes it difficult to replace it with an alternative implementation (I'm working with Vertx, thread-local isn't much use for me). Could LoggerContext work with the MDCAdapter interface instead? Thanks Jim

2 1

Custom appender: output of addWarn() not showing
by Ton van Bart 07 Jul '23

07 Jul '23

Hello, I have created a custom Logback appender which sends the log events to a Kafka topic. In order to verify if producing to Kafka was successful, I check the result and do an addWarn("Failed to produce logging", e) if there was an exception. Similarly, I tried to add an addInfo("produced offset:" + matadata.offset()) when a produce is successful. I'm using this appender in Kafka Connect, where I have wrapped it in an AsyncAppender; however, neither message is showing. I also tried printing to System.out / System.err from within the appender with the same (lack of) result: during start up of Connect, I do see addInfo() messages, but during normal processing, everything goes silent. No messages appear on the topic so I assume something went wrong; when testing the setup in a local docker compose, it works, so there must be some problem somewhere. I understand that this may be due to the combination with Kafka Connect, my question is: should I expect addInfo() etc. to show up in normal appender processing (i.e. calling it from within append() or is this internal logging for use only in appender start() ? What would be the standard way for an appender to report errors during append()? Note: due to circumstances beyond my control, I'm currently stuck on Logback 1.2.11 . Thanks in advance for any tips, kind regards, Ton

2 3

OSGi Application: Janino on classpath?
by Benno Luthiger 02 Jul '23

02 Jul '23

Hello everybody I want to use conditional processing in my logback.xml of my OSGi application. I learnt that I have to add the Janino library (and the Janino commons-compiler) to the application's classpath. I do that and let the OSGi container (*equinox*) start these libraries. However, I still get the error '*ERROR in ch.qos.logback.core.model.processor.conditional.IfModelHandler - Could not find Janino library on the class path. Skipping conditional processing.*'. What is the proper way to add the Janino library to the classpath (in an OSGi application)? Note: I've also downloaded and added 'janino-fragment' from logback-contrib. Still the same result. Best, Benno

1 0