August 2020 - logback-dev - mailman3.qos.ch

[JIRA] Updates for LOGBACK-1524: SyslogAppender does not send FQDN hostname
by QOS.CH (JIRA) 31 Aug '20

31 Aug '20

logback / LOGBACK-1524 [Open] SyslogAppender does not send FQDN hostname ============================== Here's what changed in this issue in the last few minutes. This issue has been created This issue is now assigned to you. View or comment on issue using this link https://jira.qos.ch/browse/LOGBACK-1524 ============================== Issue created ------------------------------ Mats Adolfsson created this issue on 31/Aug/20 1:58 PM Summary: SyslogAppender does not send FQDN hostname Issue Type: Improvement Assignee: Logback dev list Components: logback-classic Created: 31/Aug/20 1:58 PM Environment: The SyslogAppender uses the SyslogStartConverter which only sends the hostname without domain name to the syslog server. To be able to differentiate between servers with the same name in different domains I propose to change getHostName() to getCanonicalHostName(). Priority: Minor Reporter: Mats Adolfsson ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

Evaluator error - getting ch.qos.logback.classic.Level could not be found
by RAJESH SIRIPURAPUKANDALA 23 Aug '20

23 Aug '20

Team, I am facing one error with my evaluator filter. I included SLFJ-API(1.7.25), logback-core, logback-classic (1.2.3) jars. Also added janino jar (3.1.1). In my logback.xml file belowis what I wrote. <appender name="syslogappender" class="ch.qos.logback.classic.net.SyslogAppender"> <filter class=ch.qos.logback.core.filter.EvaluatorFilter"> <evaluator> <expression> if (level == ERROR && formattedMessage.contains("NullPointerException") ) { return true; } return false; </expression> </evaluator> <onMismatch> NEUTRAL</onMismatch> <onMatch>ACCEPT</onMatch> </filter> </appender> and I amhaving sysloghost, facility and suffixpattern tags as well passed in the above appender. my logger for the above appender is <logger additiity=false level="INFO"> <appender-ref ref=" syslogappender> </logger> <root> <level value="INFO" /> <appender-ref ref="syslogappender" </root> with this above, Iam deploying my app to IBM Mainframe WAS server. During deployment I am getting below error. org.codehaus.commons.compiler.CompileException a class ch.qos.logback.classic.Level could not be found. Please help me how to correct this issue. Thanks.

1 0

[JIRA] (LOGBACK-204) file appender that rolls on startup
by QOS.CH (JIRA) 20 Aug '20

20 Aug '20

1 0

[JIRA] (LOGBACK-736) Logging stops when a context is restarted
by QOS.CH (JIRA) 19 Aug '20

19 Aug '20

1 0

[JIRA] Updates for LOGBACK-1523: Re-Introduce Groovy config support (Groovy Support for Java >= 9 works)
by QOS.CH (JIRA) 17 Aug '20

17 Aug '20

logback / LOGBACK-1523 [Open] Re-Introduce Groovy config support (Groovy Support for Java >= 9 works) ============================== Here's what changed in this issue in the last few minutes. This issue has been created This issue is now assigned to you. View or comment on issue using this link https://jira.qos.ch/browse/LOGBACK-1523 ============================== Issue created ------------------------------ Robert Oschwald created this issue on 17/Aug/20 3:46 PM Summary: Re-Introduce Groovy config support (Groovy Support for Java >= 9 works) Issue Type: Improvement Assignee: Logback dev list Created: 17/Aug/20 3:46 PM Environment: Groovy supports Java >= 9 since versions 2.5.0 / 3.0.0. See [https://issues.apache.org/jira/browse/GROOVY-8471] So the commits to remove Groovy support should be reverted. See [https://github.com/qos-ch/logback/search?q=java+9&type=Commits] Priority: Major Reporter: Robert Oschwald ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[qos-ch/logback] bbc783: added Antonio Tomac to CLAs
by Ceki Gulcu 12 Aug '20

12 Aug '20

Branch: refs/heads/master Home: https://github.com/qos-ch/logback Commit: bbc783e6d68482abe8e7dff0d06708175e971b91 https://github.com/qos-ch/logback/commit/bbc783e6d68482abe8e7dff0d06708175e… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2020-08-12 (Wed, 12 Aug 2020) Changed paths: M src/main/clas/signed-clas.txt Log Message: ----------- added Antonio Tomac to CLAs

1 0

[JIRA] Updates for LOGBACK-1522: SocketAppender blocks ReconfigureOnChangeTask
by QOS.CH (JIRA) 11 Aug '20

11 Aug '20

logback / LOGBACK-1522 [Open] SocketAppender blocks ReconfigureOnChangeTask ============================== Here's what changed in this issue in the last few minutes. This issue has been created This issue is now assigned to you. View or comment on issue using this link https://jira.qos.ch/browse/LOGBACK-1522 ============================== Issue created ------------------------------ Wolfgang Deifel created this issue on 11/Aug/20 1:42 PM Summary: SocketAppender blocks ReconfigureOnChangeTask Issue Type: Bug Affects Versions: 1.3.0-alpha4 Assignee: Logback dev list Components: logback-classic Created: 11/Aug/20 1:42 PM Environment: Windows 10 Pro Priority: Critical Reporter: Wolfgang Deifel Description: When logback.xml configures a scan period it starts a repeating thread ReconfigureOnChangeTask using context.getScheduledExecutorService(). When starting a SocketAppender it uses the same getContext().getScheduledExecutorService() (in AbstractSocketAppender) to run the background Thread. Unfortuntely, this scheduledExecutorService has only one thread in its core pool and cannot add additional workers. So when starting the socketAppender the ReconfigureOnChangeTask is blocked an will never check the configuration file for updates. ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] (LOGBACK-1520) threadname not correctly resolved in SocketAppender
by QOS.CH (JIRA) 11 Aug '20

11 Aug '20

1 0

[JIRA] Updates for LOGBACK-1521: MDCFilter for appenders
by QOS.CH (JIRA) 10 Aug '20

10 Aug '20

logback / LOGBACK-1521 [Open] MDCFilter for appenders ============================== Here's what changed in this issue in the last few minutes. This issue has been created This issue is now assigned to you. View or comment on issue using this link https://jira.qos.ch/browse/LOGBACK-1521 ============================== Issue created ------------------------------ Wolfgang Deifel created this issue on 10/Aug/20 2:07 PM Summary: MDCFilter for appenders Issue Type: Improvement Affects Versions: 1.3.0-alpha4 Assignee: Logback dev list Attachments: MDCFilter.java Components: logback-classic Created: 10/Aug/20 2:07 PM Environment: Windows 10 Pro Labels: filter Priority: Trivial Reporter: Wolfgang Deifel Description: It would be nice to provide an MDCFilter for appenders, like it is currectly already available as TurboFilter. See attached file. That would be a performance enhancement for e.g. SocketAppender so they don't need to send LoggingEvents that are possibly unwanted. ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for LOGBACK-1520: threadname not correctly resolved in SocketAppender
by QOS.CH (JIRA) 10 Aug '20

10 Aug '20

logback / LOGBACK-1520 [Open] threadname not correctly resolved in SocketAppender ============================== Here's what changed in this issue in the last few minutes. This issue has been created This issue is now assigned to you. View or comment on issue using this link https://jira.qos.ch/browse/LOGBACK-1520 ============================== Issue created ------------------------------ Wolfgang Deifel created this issue on 10/Aug/20 1:59 PM Summary: threadname not correctly resolved in SocketAppender Issue Type: Bug Affects Versions: 1.3.0-alpha4 Assignee: Logback dev list Components: logback-classic Created: 10/Aug/20 1:59 PM Environment: Windows 10 Pro Priority: Major Reporter: Wolfgang Deifel Description: When using SocketAppender as the only appender for a certain Logger the threadName from the logging event is not evaluated in the calling thread as expected but in the writing thread which does the serialization. This leads to a wrong threadName on consumer side. If there are other appenders attached to a certain logger, the threadName is resolved and cached in the LoggingEvent in the calling thread and so it is correct. ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0