- logback-user - mailman3.qos.ch

Issue with LoggerFactory on Java 9
by Mark Raynsford 09 Feb '18

09 Feb '18

Hello. It seems that LoggerFactory misbehaves when used from a modular project: I have a very simple repro case here: https://github.com/io7m/logback-bug-20180209 The error is: Exception in thread "main" java.util.ServiceConfigurationError: ch.qos.logback.classic.spi.Configurator: module ch.qos.logback.classic does not declare `uses` at java.base/java.util.ServiceLoader.fail(ServiceLoader.java:588) at java.base/java.util.ServiceLoader.checkCaller(ServiceLoader.java:574) at java.base/java.util.ServiceLoader.<init>(ServiceLoader.java:503) at java.base/java.util.ServiceLoader.load(ServiceLoader.java:1639) at ch.qos.logback.classic/ch.qos.logback.classic.util.EnvUtil.loadFromServiceLoader(EnvUtil.java:48) at ch.qos.logback.classic/ch.qos.logback.classic.util.ContextInitializer.autoConfig(ContextInitializer.java:155) at ch.qos.logback.classic/ch.qos.logback.classic.spi.LogbackServiceProvider.initializeLoggerContext(LogbackServiceProvider.java:49) at ch.qos.logback.classic/ch.qos.logback.classic.spi.LogbackServiceProvider.initialize(LogbackServiceProvider.java:40) at org.slf4j/org.slf4j.LoggerFactory.bind(LoggerFactory.java:153) at org.slf4j/org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:141) at org.slf4j/org.slf4j.LoggerFactory.getProvider(LoggerFactory.java:419) at org.slf4j/org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:405) at org.slf4j/org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:354) at org.slf4j/org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:380) at com.io7m.bugs.logback/com.io7m.bugs.logback.Main.<clinit>(Main.java:8) The code simply calls: private static final Logger LOG = LoggerFactory.getLogger(Main.class); ... with a module descriptor: module com.io7m.bugs.logback { requires org.slf4j; } -- Mark Raynsford | http://www.io7m.com

2 2

Poll regarding upgrading logback to Java 8
by Ceki 29 Jan '18

29 Jan '18

Hi All, I just created a poll regarding upgrading logback to Java 8. Please vote and make your voice heard. https://doodle.com/poll/s7n3wk59694pmnbs -- Ceki

1 0

Spring and Logback : 8 threads (logback-1 to logback-8) are created.. why 8 ?
by Muelsa Prinarnod 20 Jan '18

20 Jan '18

Dear all, *first of all, excuse me if you receive this issue 2 times, but I've sent it before subscribing and I was not sure it was accepted.* I have deployed 10 applications in Tomcat/Spring and each one contains logback in order to have a different log file for each application. When I look at tomcat threads, I see 8 threads per application (named logback-1 to logback-8). Does anyone know why 8 and how to reduce that number ? (and the consequencies) ? 8x10 is much ... thanks in advance for any help, Samuel

2 1

How to add less than (<) and greater than (>) in logback.xml
by Debraj Manna 19 Jan '18

19 Jan '18

Crossposting from stackoverflow <https://stackoverflow.com/questions/48341348/how-to-add-less-than-and-great…> Can someone let me know how can I add less than (<) and greater than (>) sign in logback.xml? I want to have a encoder.pattern like below <encoder> <pattern>%p [%d{yyyy-MM-dd HH:mm:ss,SSS}] %c{3}:[%C{1}:%M:%L] - [%t] - %replace(%.-20480m){'[^A-Za-z0-9=<>:@\\-\\[\\]\n\\s!]','_'}%n </pattern><encoder> But this is failing because of the presence of <> ? Thanks, Debraj

2 2

Release of logback version 1.3.0-alpha0
by Ceki 18 Jan '18

18 Jan '18

Hello all, I am happy to announce the release of logback version 1.3.0-alpha0. The 1.3.x series is Jigsaw/Java0 modularized and requires slf4j-api version 1.8.x. Given that all currently available versions of Groovy are incompatible with Java 9, at least when built with Maven, we have momentarily dropped support for Groovy configuration, a.k.a Gaffer. The 1.3.x series requires Java 7 at runtime. If you wish to build logback from source, you will need Java 9. Please refer to the news page for precise details. http://logback.qos.ch/news.html You can receive logback related announcements by subscribing to the QOS.ch announce mailing list. To subscribe to QOS.ch announce list, please visit the following URL. http://www.qos.ch/mailman/listinfo/announce You may also receive announcements via twitter by following: https://twitter.com/qos_ch Enjoy, -- Ceki Gülcü

1 0

Logback configuration is coming as null
by Debraj Manna 15 Jan '18

15 Jan '18

I am using logback 1.2.3. I am passing the logback configuration as -Dlogback.configurationFile=$SERVICE_PATH/restapilayer.logback.xml My restapilayer.logback.xml looks like below <?xml version="1.0" encoding="UTF-8"?><configuration> <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender"> <layout class="ch.qos.logback.classic.PatternLayout"> <Pattern> %d{yyyy-MM-dd HH:mm:ss} [%thread] %-5level %logger{36} - %msg%n </Pattern> </layout> </appender> <root level="DEBUG"> <appender-ref ref="STDOUT" /> </root> </configuration> In my logs also I am seeing the configuration file being loaded. 16:25:32,564 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Found resource [/home/ubuntu/build-target/restapilayer/restapilayer.logback.xml] at [file:/home/ubuntu/build-target/restapilayer/restapilayer.logback.xml]16:25:32,705 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - debug attribute not set16:25:32,706 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.ConsoleAppender]16:25:32,716 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [STDOUT]16:25:32,798 |-WARN in ch.qos.logback.core.ConsoleAppender[STDOUT] - This appender no longer admits a layout as a sub-component, set an encoder instead.16:25:32,798 |-WARN in ch.qos.logback.core.ConsoleAppender[STDOUT] - To ensure compatibility, wrapping your layout in LayoutWrappingEncoder.16:25:32,798 |-WARN in ch.qos.logback.core.ConsoleAppender[STDOUT] - See also http://logback.qos.ch/codes.html#layoutInsteadOfEncoder for details16:25:32,799 |-INFO in ch.qos.logback.classic.joran.action.RootLoggerAction - Setting level of ROOT logger to DEBUG16:25:32,799 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [STDOUT] to Logger[ROOT]16:25:32,800 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - End of configuration.16:25:32,801 |-INFO in ch.qos.logback.classic.joran.JoranConfigurator@76707e36 - Registering current configuration as safe fallback point 2018-01-12 16:25:32 [main] INFO com.vnera.common.utils.CommonUtils - adding uncaught exception handler hook... log4j: Default initialization of overridden by log4j.defaultInitOverrideproperty. log4j:WARN No appenders could be found for logger (org.jboss.logging). log4j:WARN Please initialize the log4j system properly. log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. INFO [2018-01-12 16:25:34] o.e.j.u.log:[?:?:?] - [main] - Logging initialized @1909ms Then while trying to log I am seeing the logback configuration as null and it seems logback is running with default config INFO [2018-01-12 16:25:34] c.v.r.c.v.r.VneraBackendService:[?:?:?] - [main] - Logback used _null_ as the configuration file_ I am using the below code to get the logback config logger.debug("Testing Debug logging");LoggerContext loggerContext = ((ch.qos.logback.classic.Logger)logger).getLoggerContext(); URL mainURL = ConfigurationWatchListUtil.getMainWatchURL(loggerContext);System.out.println(mainURL);// or even logger.info("Logback used '{}' as the configuration file.", mainURL); Can someone let me know what is going wrong? How can I debug this issue?

2 6

Re: [logback-user] Delaying debug logs until an error occurs
by Friso Vrolijken 15 Jan '18

15 Jan '18

Hi all, >> I’m wondering if there is a way to have logback “save” debug messages and only log them if an error is logged at some point later on in the same transaction. > That sounds like a feature you should bake into your codebase, instead of pushing it to logback. As I have had the same thought a couple of times before, I disagree. Why should everyone fix the same problem in their own codebase? Isn’t that what libraries are for? Groeten, Friso

1 0

logback line number is not showing up in logs
by Debraj Manna 12 Jan '18

12 Jan '18

I am using logback 1.2.3 . I have added the below dependency to my pom.xml <dependency> <groupId>ch.qos.logback</groupId> <artifactId>logback-classic</artifactId> <version>1.2.3</version> </dependency> My configuration looks like below <configuration> <appender name="CONSOLE" class= "ch.qos.logback.core.ConsoleAppender"> <Target>System.out</Target> <encoder> <pattern>%p [%d{yyyy-MM-dd HH:mm:ss,SSS}] %c{3}:[%C{1}:%M:%L] - [%t] - %m%n </pattern> </encoder> </appender> <root level="INFO"> <appender-ref ref= "CONSOLE"/> <appender-ref ref="datadog"/> </root> </configuration> Filename & line number is not showing up. A question mark is coming. INFO [2018-01-12 07:06:54] c.v.s.f.FlowStoreWarmer:[?:?:?] - [FlowStoreWarmer_flow_cache_warmup_thread] - no work to do for cid 19099 Can some one let me know what is going wrong? Do I have add logback-core also as dependency? Thanks,

2 2

Setter after parsing config file in logback appender
by Debraj Manna 12 Jan '18

12 Jan '18

In log4j there is a method activateOptions which is called after log4j has parsed the configuration file and called any associated setters. Is there any similar method in logback which is called after logback has parsed the configuration file and called the associated setters?

2 3

GELF support
by Guido Wimmel 03 Jan '18

03 Jan '18

Hi, we want to use Logback to send logs to a Graylog server using the GELF format. The only third-party framework supporting GELF listed on the official logback site seems to be Logback-gelf (see https://logback.qos.ch/download.html ), which is no longer maintained. Is anyone using one of the alternatives (see https://marketplace.graylog.org/addons?kind=gelf&tag=logback ) and can share their experiences? There are currently no plans to include GELF support into Logback proper (as in Log4j2), right? Thanks in advance, cheers, Guido

2 1