- logback-dev - mailman3.qos.ch

[JIRA] Updates for LOGBACK-1699: com.sun.mail:javax.mail no longer optional
by QOS.CH (JIRA) 17 Oct '22

17 Oct '22

logback / LOGBACK-1699 [Open] com.sun.mail:javax.mail no longer optional ============================== 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-1699 ============================== Issue created ------------------------------ Joe Barnett created this issue on 17/Oct/22 4:23 PM Summary: com.sun.mail:javax.mail no longer optional Issue Type: Bug Affects Versions: 1.3.2 Assignee: Logback dev list Components: logback-classic Created: 17/Oct/22 4:23 PM Priority: Major Reporter: Joe Barnett Description: per LOGBACK-1410, com.sun.mail:javax.mail was optional in logback-classic 1.3.0 and 1.3.1, but the optional qualifier seems to have disappeared since 1.3.2. ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for LOGBACK-1698: "Nested appenders are not allowed" warning using SiftingAppender
by QOS.CH (JIRA) 17 Oct '22

17 Oct '22

logback / LOGBACK-1698 [Open] "Nested appenders are not allowed" warning using SiftingAppender ============================== 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-1698 ============================== Issue created ------------------------------ albertus82 created this issue on 17/Oct/22 11:19 AM Summary: "Nested appenders are not allowed" warning using SiftingAppender Issue Type: Bug Affects Versions: 1.4.4 Assignee: Logback dev list Created: 17/Oct/22 11:19 AM Environment: Relevant part of the XML configuration: {code:xml} <appender name="MY_LOG_APPENDER" class="ch.qos.logback.classic.sift.SiftingAppender">  <discriminator> <key>dummy</key> <defaultValue>dummy</defaultValue> </discriminator>  <sift> <appender name="MY_LOG_APPENDER_SIFT" class="ch.qos.logback.core.rolling.RollingFileAppender"> <rollingPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedRollingPolicy"> <fileNamePattern>${logs.directory}/mylog.%d.%i.log</fileNamePattern> <maxFileSize>25MB</maxFileSize> <maxHistory>30</maxHistory> <totalSizeCap>250MB</totalSizeCap> <cleanHistoryOnStart>true</cleanHistoryOnStart> </rollingPolicy> <encoder> <pattern>%d{MMM dd HH:mm:ss} %hostaddr %msg%n</pattern> </encoder> </appender> </sift> </appender> {code} Labels: SiftingAppender Priority: Major Reporter: albertus82 Description: Hi, I'm migrating from 1.2 to 1.4 and I have a {{SiftingAppender}} configured like the example shown in the manual (appender > sift > appender): [https://logback.qos.ch/manual/appenders.html#SiftingAppender] Nevertheless I'm getting the warning "As of logback version 1.3, nested appenders are not allowed", which causes Logback to print its full initalization log. Am I missing something? Thank you. ---- {color:#403294}_Original post: [https://github.com/qos-ch/logback/discussions/604]_{color} ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] (LOGBACK-267) FixedWindowRollingPolicy performs compression on the logging thread
by QOS.CH (JIRA) 17 Oct '22

17 Oct '22

1 0

[JIRA] (LOGBACK-1695) Modular export missing for ch.qos.logback.core.layout
by QOS.CH (JIRA) 15 Oct '22

15 Oct '22

1 0

[JIRA] (LOGBACK-1610) Jetty 10 support
by QOS.CH (JIRA) 14 Oct '22

14 Oct '22

1 0

[JIRA] (LOGBACK-1696) Log timestamps incorrect month format on en_AU.UTF-8
by QOS.CH (JIRA) 14 Oct '22

14 Oct '22

1 0

[JIRA] (LOGBACK-1229) byte count for tomcat is wrong when transfer encoding is chunked
by QOS.CH (JIRA) 12 Oct '22

12 Oct '22

1 0

Logback access issue JIRA LOGBACK-1229
by Daphne Hsieh 12 Oct '22

12 Oct '22

hello logback community, I am recently using logback access valve with tomcat server and running into this issue in the JIRA ticket. https://jira.qos.ch/browse/LOGBACK-1229 The PR is in the ticket. This ticket has been pushed back for almost 2 years and am wondering if this is on track to be fixed in logback 1.4.5. Thank you Daphne

1 0

[JIRA] Updates for LOGBACK-1697: Blocked when many exceptions happen
by QOS.CH (JIRA) 08 Oct '22

08 Oct '22

logback / LOGBACK-1697 [Open] Blocked when many exceptions happen ============================== 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-1697 ============================== Issue created ------------------------------ Chenzhe Mao created this issue on 08/Oct/22 3:31 AM Summary: Blocked when many exceptions happen Issue Type: Improvement Affects Versions: 1.2.11 Assignee: Logback dev list Components: logback-classic Created: 08/Oct/22 3:31 AM Labels: logging Priority: Major Reporter: Chenzhe Mao Description: I use version 1.2.11, but the latest version still exists this problem. I use jdk proxy, but classes starting with sun. reflect cannot hit the cache when loading.When many exceptions happen, the request will be blocked like this cpu flame diagram.Classes not load should be cached. !https://user-images.githubusercontent.com/49109627/193023993-6e0bea07-b988-400b-9327-61a6a2fcd100.png|width=945,height=456! ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] (LOGBACK-1680) Unable to use JULHelper with Java Modules
by QOS.CH (JIRA) 07 Oct '22

07 Oct '22

1 0