- logback-dev - mailman3.qos.ch

[JIRA] (LOGBACK-1442) Adding "originalFileName" token to FileNamePattern or TimeBasedRollingPolicy
by QOS.CH (JIRA) 28 Nov '18

28 Nov '18

Anton Pryamostanov created LOGBACK-1442: ------------------------------------------- Summary: Adding "originalFileName" token to FileNamePattern or TimeBasedRollingPolicy Key: LOGBACK-1442 URL: https://jira.qos.ch/browse/LOGBACK-1442 Project: logback Issue Type: Improvement Components: logback-classic Environment: Let's consider the below example: {code:xml} <appender name="OutputInfo" class="ch.qos.logback.classic.sift.SiftingAppender"> <filter class="ch.qos.logback.classic.filter.LevelFilter"> <level>ERROR</level> <onMatch>ACCEPT</onMatch> <onMismatch>DENY</onMismatch> </filter> <discriminator> <key>automaticThreadName</key> <defaultValue>Unnamed Thread</defaultValue> </discriminator> <discriminator> <key>inputQueueName</key> <defaultValue>APP</defaultValue> </discriminator> <discriminator> <key>outputQueueName</key> <defaultValue>APP</defaultValue> </discriminator> <sift> <appender name="${automaticThreadName}" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>./LOGS/${inputQueueName}/${outputQueueName}/ERROR/${automaticThreadName}_ERROR_TODAY.log</file> <encoder class="ch.qos.logback.classic.encoder.PatternLayoutEncoder"> <Pattern>%d{yyyy-MM-dd HH:mm:ss} %mdc [%thread] %level %logger{35} - %msg%n</Pattern> </encoder> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <FileNamePattern>./LOGS/${inputQueueName}/${outputQueueName}/ERROR/ARCHIVE/%d{yyyyMMdd, aux}/${automaticThreadName}_%d{yyyyMMdd}_ERROR.zip</FileNamePattern> </rollingPolicy> </appender> </sift> </appender> {code} It is not a valid example because FileNamePattern of TimeBasedRollingPolicy does not support MDC tokens like the SiftingAppender supports. This is causing a significant limitation for SiftingAppender log archiving - a diversity of file names of SiftingAppender can be archived only into a narrow list of archives due to TimeBasedRollingPolicy not supporting MDC tokens. This can be easily fixed just by adding 3 tokens into TimeBasedRollingPolicy FileNamePattern, which will represent: - %q - qualified file name of original physical file, e.g. ./logs/thread1/20181115/thread1_errors.log - %f - only file name of original physical file, e.g. "thread1_errors.log" - %p - only path of original physical file, e.g. "./logs/thread1/20181115/" Therefore the above config will look like: {code} <appender name="OutputInfo" class="ch.qos.logback.classic.sift.SiftingAppender"> <filter class="ch.qos.logback.classic.filter.LevelFilter"> <level>ERROR</level> <onMatch>ACCEPT</onMatch> <onMismatch>DENY</onMismatch> </filter> <discriminator> <key>automaticThreadName</key> <defaultValue>Unnamed Thread</defaultValue> </discriminator> <discriminator> <key>inputQueueName</key> <defaultValue>APP</defaultValue> </discriminator> <discriminator> <key>outputQueueName</key> <defaultValue>APP</defaultValue> </discriminator> <sift> <appender name="${automaticThreadName}" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>./LOGS/${inputQueueName}/${outputQueueName}/ERROR/${automaticThreadName}_ERROR_TODAY.log</file> <encoder class="ch.qos.logback.classic.encoder.PatternLayoutEncoder"> <Pattern>%d{yyyy-MM-dd HH:mm:ss} %mdc [%thread] %level %logger{35} - %msg%n</Pattern> </encoder> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <FileNamePattern>%q.zip</FileNamePattern> </rollingPolicy> </appender> </sift> </appender> {code} Reporter: Anton Pryamostanov Assignee: Logback dev list -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-1027) Circular Referenced Suppressed Exception Throws StackOverflowError
by QOS.CH (JIRA) 27 Nov '18

27 Nov '18

1 0

[JIRA] (LOGBACK-1441) Name of ThresholdFilter given in logback.xml is ignored
by QOS.CH (JIRA) 27 Nov '18

27 Nov '18

1 0

[JIRA] (LOGBACK-1441) Name of ThresholdFilter given in logback.xml is ignored
by QOS.CH (JIRA) 27 Nov '18

27 Nov '18

Máté Kovács created LOGBACK-1441: ------------------------------------ Summary: Name of ThresholdFilter given in logback.xml is ignored Key: LOGBACK-1441 URL: https://jira.qos.ch/browse/LOGBACK-1441 Project: logback Issue Type: Bug Affects Versions: 1.3.0-alpha4 Environment: Reporter: Máté Kovács Assignee: Logback dev list Priority: Minor I have a logback.xml. A fragment of it is: <filter name="FileAppenderThresholdFilter" class="ch.qos.logback.classic.filter.ThresholdFilter"> <level>${LOGGER_SDK_FILE_APPENDER_LOGLEVEL:-OFF}</level> </filter> If I obtain the ThresholdFilter object from java code, the name of it is null. I am sure I find the right object. -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-1440) ajouter mesaj özeticisi
by QOS.CH (JIRA) 23 Nov '18

23 Nov '18

Ceki Gülcü created LOGBACK-1440: ----------------------------------- Summary: ajouter mesaj özeticisi Key: LOGBACK-1440 URL: https://jira.qos.ch/browse/LOGBACK-1440 Project: logback Issue Type: Sub-task Reporter: Ceki Gülcü Assignee: Ceki Gülcü -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-1439) Allow offline verification of configuration files
by QOS.CH (JIRA) 22 Nov '18

22 Nov '18

Ceki Gülcü created LOGBACK-1439: ----------------------------------- Summary: Allow offline verification of configuration files Key: LOGBACK-1439 URL: https://jira.qos.ch/browse/LOGBACK-1439 Project: logback Issue Type: Sub-task Reporter: Ceki Gülcü Assignee: Ceki Gülcü -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-1438) Allow for standardized logging configuration
by QOS.CH (JIRA) 21 Nov '18

21 Nov '18

Ceki Gülcü created LOGBACK-1438: ----------------------------------- Summary: Allow for standardized logging configuration Key: LOGBACK-1438 URL: https://jira.qos.ch/browse/LOGBACK-1438 Project: logback Issue Type: Improvement Environment: Allow for standardized logging configuration to be shared by multiple applications. However, the configuration should be parameterizable to some extent, Example of general structure {code} [general parameters] scan period appName externalConfPath outputPath include: externalConfPath/appName-custome.xml [RollingFileAppender-GENERAL] dailyRollover flush: no (configurable) outputPath/appName-general-TIME.log maxHistory: 90 days, configurable sizeCap: 100GB, configurable [root-logger] level: info, overridable appender:RollingFileAppender-GENERAL {code} Reporter: Ceki Gülcü Assignee: Logback dev list -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-1437) Attempting to log session ID throws if session not set
by QOS.CH (JIRA) 20 Nov '18

20 Nov '18

Keith Gregory created LOGBACK-1437: -------------------------------------- Summary: Attempting to log session ID throws if session not set Key: LOGBACK-1437 URL: https://jira.qos.ch/browse/LOGBACK-1437 Project: logback Issue Type: Bug Components: logback-access Affects Versions: 1.2.3 Environment: Tomcat 8.5 Oracle JDK 1.8 Logback 1.2.3 (although it appears that the code in 1.3.0-alpha has the same problem) Reporter: Keith Gregory Assignee: Logback dev list With a simple web-app that does not automatically create a session, using the following pattern in \{\{logback-access.xml}}: \{code:xml} <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender"> <encoder> <pattern>%h %l %u %user %date "%r" %s %b %sessionID</pattern> </encoder> </appender> \{code} will cause the following exception: \{code} 20:22:26,782 |-ERROR in ch.qos.logback.core.ConsoleAppender[STDOUT] - Appender [STDOUT] failed to append. java.lang.IllegalStateException: Cannot create a session after the response has been committed at java.lang.IllegalStateException: Cannot create a session after the response has been committed at at org.apache.catalina.connector.Request.doGetSession(Request.java:3030) at at org.apache.catalina.connector.Request.getSession(Request.java:2451) at at ch.qos.logback.access.spi.AccessEvent.getSessionID(AccessEvent.java:249) at at ch.qos.logback.access.pattern.SessionIDConverter.convert(SessionIDConverter.java:21) ... \{code} I believe that you can resolve this by changing [AccessEvent.getSession()|https://logback.qos.ch/xref/ch/qos/logback/access/spi/AccessEvent.html#L249] to call \{\{getSession(false)}} rather than \{\{getSession()}}. -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-1436) There is no way to know how many events are discarded by AsyncAppender
by QOS.CH (JIRA) 14 Nov '18

14 Nov '18

Roberto Tyley created LOGBACK-1436: -------------------------------------- Summary: There is no way to know how many events are discarded by AsyncAppender Key: LOGBACK-1436 URL: https://jira.qos.ch/browse/LOGBACK-1436 Project: logback Issue Type: Improvement Components: logback-classic Affects Versions: 1.2.3 Reporter: Roberto Tyley Assignee: Logback dev list ch.qos.logback.classic.AsyncAppender's append() method will discard events if both isQueueBelowDiscardingThreshold() and isDiscardable(eventObject) are true, which is reasonable and documented behaviour, but there is no way for the user to track the level at which this is occurring. It's not easy to address this problem by extending AsyncAppender, as isQueueBelowDiscardingThreshold() is private and depends on private values. Making isQueueBelowDiscardingThreshold() protected rather than private would help here, or alternatively directly building-in some kind of counter of discarded events would be another way. -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

JDK 12 , JDK 8u202 & Project Panama Early-Access builds available
by Rory O'Donnell 09 Nov '18

09 Nov '18

Hi Ceki, *JDK 12 Early Access build 19 is available at : - jdk.java.net/12/* * These early-access, open-source builds are provided under the GNU General Public License, version 2, with the Classpath Exception <http://openjdk.java.net/legal/gplv2+ce.html>. * Release Notes updates since last email o Build 18 – JDK-8211883: Disable anon and NULL cipher suites + Crypto Roadmap <https://java.com/en/jre-jdk-cryptoroadmap.html> Updated o Build 17 – JDK-8211806: TLS 1.3 handshake server name indication is missing on a session resume o Build 16 – JDK-8211866: TLS 1.3 CertificateRequest message sometimes offers disallowed signature algorithms o Build 17 – JDK-8195793 : Remove GTE CyberTrust Global Root o Build 16 - JDK-8191053 : Provide a mechanism to make system's security manager immutable * JEPs proposed for JDK 12 so far: o JEP 230 - Microbenchmark Suite <https://openjdk.java.net/jeps/230> * JEPs targeted to JDK 12, so far o 325: Switch Expressions (Preview) <http://openjdk.java.net/jeps/325> o 326: Raw String Literals (Preview) <http://openjdk.java.net/jeps/326> o 340: One AArch64 Port, Not Two <http://openjdk.java.net/jeps/340> o 341: Default CDS Archives <http://openjdk.java.net/jeps/341> *JDK 8u202 Early Access build 03 is available at : - **http://jdk.java.net/8/* * JDK 8u202 timeline is available [1] o GA is scheduled for January 2019 *Project Panama Early-Access build 0 ***is available at : - http://jdk.java.net/panama/ ** * Early access builds from Project Panama <https://openjdk.java.net/projects/panama/> * Early-access builds are provided under the GNU General Public License, version 2, with the Classpath Exception <http://openjdk.java.net/legal/gplv2+ce.html>. * Feedback - Please send feedback via e-mail to panama-dev(a)openjdk.java.net <mailto:panama-dev@openjdk.java.net>. * To send e-mail to this address you must first subscribe to the mailing list <http://mail.openjdk.java.net/mailman/listinfo/panama-dev>. *Crypto Roadmap Updated [2] * Rgds,Rory [1] http://openjdk.java.net/projects/jdk8u/releases/8u202.html [2] https://java.com/en/jre-jdk-cryptoroadmap.html -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA , Dublin, Ireland

1 0