- logback-dev - mailman3.qos.ch

[JIRA] (LOGBACK-1502) Janino no longer works with 1.3.0-alpha5
by QOS.CH (JIRA) 07 Feb '20

07 Feb '20

Jeremy Landis created LOGBACK-1502: -------------------------------------- Summary: Janino no longer works with 1.3.0-alpha5 Key: LOGBACK-1502 URL: https://jira.qos.ch/browse/LOGBACK-1502 Project: logback Issue Type: Bug Components: logback-classic, logback-core Affects Versions: 1.3.0-alpha5 Environment: janino stopped working with this release resulting in creation of unknown log location files. It works up through alpha4 without issues and no changes. Can this please be fixed? Reporter: Jeremy Landis Assignee: Logback dev list -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-1501) Make checker framework which is really, really old, optional
by QOS.CH (JIRA) 07 Feb '20

07 Feb '20

Jeremy Landis created LOGBACK-1501: -------------------------------------- Summary: Make checker framework which is really, really old, optional Key: LOGBACK-1501 URL: https://jira.qos.ch/browse/LOGBACK-1501 Project: logback Issue Type: Bug Components: logback-classic Affects Versions: 1.3.0-alpha5 Environment: This release started requiring a really old checker framework that conflicts with newer one as group id changed. If the really old version is necessary, please make it optional. Reporter: Jeremy Landis Assignee: Logback dev list -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-1410) Make com.sun.mail:javax.mail optional
by QOS.CH (JIRA) 07 Feb '20

07 Feb '20

1 0

[JIRA] (LOGBACK-1500) SizeAndTimeBasedRollingPolicy misbehavior after %i index reaches 999
by QOS.CH (JIRA) 06 Feb '20

06 Feb '20

George Yanev created LOGBACK-1500: ------------------------------------- Summary: SizeAndTimeBasedRollingPolicy misbehavior after %i index reaches 999 Key: LOGBACK-1500 URL: https://jira.qos.ch/browse/LOGBACK-1500 Project: logback Issue Type: Bug Components: logback-classic, logback-core Affects Versions: 1.2.3 Environment: OS: Ubuntu 18.04.4 LTS java: java version "1.8.0_181" Java(TM) SE Runtime Environment (build 1.8.0_181-b13) Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode) Reporter: George Yanev Assignee: Logback dev list Attachments: logback-test.rar I'm using SizeAndTimeBasedRollingPolicy. When '%i' file index reaches 999 it stops deleting the old files and totalSizeCap is not respected any more. This soon leads to disk full issues (as logging in my case was fast enough) I'm attaching a java example with a simple logging configuration to demonstrate this. You have to run it just for a couple off minutes to reach file index 999 Use maven install to build. Untar the generated tar.gz file to some place and run the example with java -jar testartifact-1.0.0-20200206.jar -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-1406) Seems all threads blocked
by QOS.CH (JIRA) 04 Feb '20

04 Feb '20

1 0

[JIRA] (LOGBACK-1499) Syslog appender documentation update
by QOS.CH (JIRA) 30 Jan '20

30 Jan '20

Ceki Gülcü created LOGBACK-1499: ----------------------------------- Summary: Syslog appender documentation update Key: LOGBACK-1499 URL: https://jira.qos.ch/browse/LOGBACK-1499 Project: logback Issue Type: Improvement Environment: Syslog appender documentation here: http://logback.qos.ch/manual/appenders.html#SyslogAppender It would be great to add a note that Syslog appender works over *UDP *protocol only, Reporter: Ceki Gülcü Assignee: Logback dev list Priority: Minor Fix For: 1.3.0-alpha6 -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-1498) When skipping lines with ThrowableProxyConverter the exception origin may be lost.
by QOS.CH (JIRA) 23 Jan '20

23 Jan '20

1 0

[JIRA] (LOGBACK-1498) When skipping lines with ThrowableProxyConverter the exception origin may be lost.
by QOS.CH (JIRA) 23 Jan '20

23 Jan '20

1 0

[JIRA] (LOGBACK-1498) When skipping lines with ThrowableProxyConverter the exception origin may be lost.
by QOS.CH (JIRA) 23 Jan '20

23 Jan '20

Mark created LOGBACK-1498: ----------------------------- Summary: When skipping lines with ThrowableProxyConverter the exception origin may be lost. Key: LOGBACK-1498 URL: https://jira.qos.ch/browse/LOGBACK-1498 Project: logback Issue Type: Improvement Components: logback-classic Affects Versions: 1.3.0-alpha5 Reporter: Mark Assignee: Logback dev list The ability to exclude lines from the stacktrace is little known and extremely helpful, especially when using frameworks that use proxies and have deeply nested calls and exceptions. We are using this feature with the configuration below in Spring Boot but we lose some information if the Exception originates in some of the framework code. For example if the exception is thrown from "org.springframework.web.filter" the location of the problem is suppressed! In ThrowableProxyConverter a single line change will improve this. I have made the change locally and provided a new junit test method in ThrowableProxyConverterTest. If you are receptive to the change I will create a PR. thank you, Mark {code:xml} <pattern>%-4relative [%thread] %-5level %logger{35} - %msg %n%ex{1000000, com.sun.proxy., java.lang.reflect., javax.servlet., org.springframework.cglib., org.springframework.aop., org.springframework.transaction.interceptor.TransactionAspectSupport., org.springframework.validation.beanvalidation.MethodValidationInterceptor., org.springframework.boot.actuate.web.trace., org.springframework.security.web., org.springframework.boot.actuate., org.springframework.web.servlet., org.springframework.web.method., org.springframework.web.filter., org.apache.coyote., org.apache.catalina., org.apache.tomcat., sun.reflect.} {code} -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-1492) AppenderBase is deadlock prone
by QOS.CH (JIRA) 22 Jan '20

22 Jan '20

1 0