July 2019 - logback-dev - mailman3.qos.ch

[JIRA] (LOGBACK-1475) SyslogOutputStream ignores IP address changes for Syslog DNS host
by QOS.CH (JIRA) 04 Jul '19

04 Jul '19

Simon Dean created LOGBACK-1475: ----------------------------------- Summary: SyslogOutputStream ignores IP address changes for Syslog DNS host Key: LOGBACK-1475 URL: https://jira.qos.ch/browse/LOGBACK-1475 Project: logback Issue Type: Bug Components: logback-core Affects Versions: 1.2.3 Reporter: Simon Dean Assignee: Logback dev list The SyslogOutputStream converts the syslogHost to an IP address within its constructor. This means that it only performs a DNS resolution for the Syslog host once, at start up. If the IP address of the System host changes (and is updated in the DNS system) this class will never pick up the change. The suggested fix is to move the DNS resolution from the constructor into the flush method. -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-1474) GEventEvaluator not working in logback 1.3.0-alpha4 (due to groovy issue)
by QOS.CH (JIRA) 01 Jul '19

01 Jul '19

1 0

[JIRA] (LOGBACK-1474) GEventEvaluator not working in logback 1.3.0-alpha4 (due to groovy issue)
by QOS.CH (JIRA) 01 Jul '19

01 Jul '19

Dean Hiller created LOGBACK-1474: ------------------------------------ Summary: GEventEvaluator not working in logback 1.3.0-alpha4 (due to groovy issue) Key: LOGBACK-1474 URL: https://jira.qos.ch/browse/LOGBACK-1474 Project: logback Issue Type: Bug Components: logback-classic Affects Versions: 1.3.0-alpha4, 1.3.0-alpha3, 1.3.0-alpha1 Environment: any Reporter: Dean Hiller Assignee: Logback dev list Due to a groovy issue(I need to create or find one and link here), GEventEvaluator is not supported. To reproduce, you can follow these steps * git clone [https://github.com/deanhiller/webpieces.git] * cd webpieces * git checkout logbackBugs * import into Intellij OR Eclipse via gradle (both are tested often and work) * Open DevelopmentServer.java and run it You will see this exception 09:21:00,636 |-ERROR in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Could not create component [evaluator] of type [ch.qos.logback.classic.boolex.GEventEvaluator] java.lang.ClassNotFoundException: ch.qos.logback.classic.boolex.GEventEvaluator at java.lang.ClassNotFoundException: ch.qos.logback.classic.boolex.GEventEvaluator at at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:583) at at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178) at at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521) at at ch.qos.logback.core.util.Loader.loadClass(Loader.java:120) at at ch.qos.logback.core.joran.action.NestedComplexPropertyIA.begin(NestedComplexPropertyIA.java:102) at at ch.qos.logback.core.joran.spi.Interpreter.callBeginAction(Interpreter.java:269) at at ch.qos.logback.core.joran.spi.Interpreter.startElement(Interpreter.java:145) at at ch.qos.logback.core.joran.spi.Interpreter.startElement(Interpreter.java:128) at at ch.qos.logback.core.joran.spi.EventPlayer.play(EventPlayer.java:50) at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:165) at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:152) at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:110) at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:53) at at ch.qos.logback.classic.util.ContextInitializer.configureByResource(ContextInitializer.java:82) at at ch.qos.logback.classic.util.ContextInitializer.autoConfig(ContextInitializer.java:157) at at ch.qos.logback.classic.spi.LogbackServiceProvider.initializeLoggerContext(LogbackServiceProvider.java:49) at at ch.qos.logback.classic.spi.LogbackServiceProvider.initialize(LogbackServiceProvider.java:40) at at org.slf4j.LoggerFactory.bind(LoggerFactory.java:151) at at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:139) at at org.slf4j.LoggerFactory.getProvider(LoggerFactory.java:417) at at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:403) at at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:352) at at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:378) at at WEBPIECESxPACKAGE.DevelopmentServer.<clinit>(DevelopmentServer.java:8) -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-1473) %caller broken for lambdas in latest alpha release
by QOS.CH (JIRA) 01 Jul '19

01 Jul '19

Dean Hiller created LOGBACK-1473: ------------------------------------ Summary: %caller broken for lambdas in latest alpha release Key: LOGBACK-1473 URL: https://jira.qos.ch/browse/LOGBACK-1473 Project: logback Issue Type: Bug Components: logback-core Affects Versions: 1.3.0-alpha4, 1.3.0-alpha3, 1.3.0-alpha1, 1.3.0-alpha0 Environment: Any, easy to reproduce Reporter: Dean Hiller Assignee: Logback dev list %caller is an amazing feature!!! We install logback/slf4j as the defacto standard in [https://github.com/deanhiller/webpieces] AND more importantly, on the DevelopmentServer (recompiles code live as the server is running), we use the pattern %caller such that Developers can 'click' on any log statement and it takes them in their IDE right to that class file and log line. This works in intellij and in Eclipse wonderfully. So, off the branch logbackBugs, we have this class with line numbers [https://github.com/deanhiller/webpieces/blob/logbackBugs/webserver/webpiece…] We have the following pattern [https://github.com/deanhiller/webpieces/blob/logbackBugs/webserver/webpiece…] which is %date\{ISO8601} [%thread][%X\{socket}] [%X\{txId}-%X\{user}] *%caller\{1}* %-4level: %message%n The output of running that program is 2019-07-01 09:21:00,716 [main][] [-] Caller+0 at WEBPIECESxPACKAGE.DevelopmentServer.main(DevelopmentServer.java:17) INFO: Starting Development Server under java version=11.0.3 2019-07-01 09:21:00,720 [main][] [-] Caller+0 at org.slf4j.spi.DefaultLoggingEventBuilder.logViaPublicLoggerAPI(DefaultLoggingEventBuilder.java:120) INFO: testing out %caller\{1} 2019-07-01 09:21:00,721 [main][] [-] Caller+0 at org.slf4j.spi.DefaultLoggingEventBuilder.logViaPublicLoggerAPI(DefaultLoggingEventBuilder.java:120) NOTICE that the first log line is correct. Our log is from line 17 in DevelopmentServer.java. The second line is logging incorrectly(ie. I personally think logback should adjust for this as it can tell if the lambda method was called or not as it already is looking at the stack trace). We would love to upgrade to slf4j2 but this was a huge feature in using our DevelopmentServer. It works like ruby where you just keep coding and never restart the server and COMBINED with this amazing caller feature, you can click any logs to go right to the log statement which has been amazing. NOTES: If you like, it is very easy to run the above program yourself like so * git clone [https://github.com/deanhiller/webpieces.git] * cd webpieces * git checkout logbackBugs * import into Intellij OR Eclipse via gradle (both are tested often and work) * Open DevelopmentServer.java and run it -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0