- logback-dev - mailman3.qos.ch

[JIRA] (LOGBACK-1356) Have MessageConverter include any extra arguments
by QOS.CH (JIRA) 01 Dec '17

01 Dec '17

1 0

[JIRA] (LOGBACK-1356) Have MessageConverter include any extra arguments
by QOS.CH (JIRA) 01 Dec '17

01 Dec '17

Eric Pabst created LOGBACK-1356: ----------------------------------- Summary: Have MessageConverter include any extra arguments Key: LOGBACK-1356 URL: https://jira.qos.ch/browse/LOGBACK-1356 Project: logback Issue Type: Improvement Components: logback-classic Affects Versions: 1.2.3 Environment: All Reporter: Eric Pabst Assignee: Logback dev list The purpose of logging to slf4j is to allow code to log information without worrying about which implementation and format will be used for actual logging. In deployed environments, we prefer JSON logging using logstash to be consumed by Splunk, which handles JSON very nicely. However, for local development and testing, we prefer text output via logback-classic. We often want to log extra fields to show up in the JSON output such as {{\{ "timestamp": "2017...", "message": "Event X happened", "userName": "bob", "url": "http://..."}}} To accomplish this, we use logstash's StructuredArgument to provide extra arguments to the Logger: {{import static net.logstash.logback.argument.StructuredArguments.keyValue;}} {{...}} {{ LOGGER.info("Event X happened", keyValue("userName", "bob"), keyValue("url", "http://..."));}} We don't want to include \{}'s in the message or else it would log the username and url both in the message and as separate JSON properties. However, when binding to logback-classic, it is logged without these extra arguments: {{INFO 2017... Event X happened}} It would help immensely to include these extra arguments automatically if present: INFO 2017... Event X happened username=bob url=http://... -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-1355) Cannot rollover when currentlyActiveFile renamed and size reduced by other process
by QOS.CH (JIRA) 01 Dec '17

01 Dec '17

hebelala created LOGBACK-1355: --------------------------------- Summary: Cannot rollover when currentlyActiveFile renamed and size reduced by other process Key: LOGBACK-1355 URL: https://jira.qos.ch/browse/LOGBACK-1355 Project: logback Issue Type: Bug Components: logback-core Environment: SizeBasedTriggeringPolicy's is`TriggeringEvent` method should use `ResilientFileOutputStream.getChannel().size()` to replace `activeFile.length()`, because the activeFile maybe already is not matched with the outputStream. Reporter: hebelala Assignee: Logback dev list Priority: Critical -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-1354) Errors cause AsyncAppender's worker thread to terminate causing halting
by QOS.CH (JIRA) 01 Dec '17

01 Dec '17

Greg created LOGBACK-1354: ----------------------------- Summary: Errors cause AsyncAppender's worker thread to terminate causing halting Key: LOGBACK-1354 URL: https://jira.qos.ch/browse/LOGBACK-1354 Project: logback Issue Type: Bug Components: logback-core Affects Versions: 1.2.3 Environment: (Not environment specific.) Reporter: Greg Assignee: Logback dev list The AsyncAppender worker thread, defined in AsyncAppenderBase, consumes log entries from a bounded blocking queue. Should this worker thread terminate prematurely for any reason and the AsyncAppender be configured as blocking (neverBlock=false) the queue fills and any calls to log block indefinitely. The worker thread is currently indirectly tolerant of exceptions thrown by an appender, due to the exception handling in AppenderBase.doAppend, but this exception handling does not cover other Throwable types. Ideally, the AsyncAppender worker thread should do everything possible to stay alive while the appender is started. -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[qos-ch/logback] 6faf5d: ongoing work on modularizing logback
by Ceki Gulcu 30 Nov '17

30 Nov '17

Branch: refs/heads/master Home: https://github.com/qos-ch/logback Commit: 6faf5d375dd619857357fb71ca729f0b2514d6c4 https://github.com/qos-ch/logback/commit/6faf5d375dd619857357fb71ca729f0b25… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2017-11-30 (Thu, 30 Nov 2017) Changed paths: M logback-classic/pom.xml M logback-classic/src/main/java/ch/qos/logback/classic/provider/LogbackServiceProvider.java M logback-core/pom.xml M pom.xml Log Message: ----------- ongoing work on modularizing logback

1 0

[qos-ch/logback] f25e0a: minor edits
by Ceki Gulcu 29 Nov '17

29 Nov '17

Branch: refs/heads/master Home: https://github.com/qos-ch/logback Commit: f25e0af4cf0498733bf30f275ea87efc3df733ae https://github.com/qos-ch/logback/commit/f25e0af4cf0498733bf30f275ea87efc3d… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2017-11-29 (Wed, 29 Nov 2017) Changed paths: M logback-classic/src/main/java/ch/qos/logback/classic/turbo/LRUMessageCache.java Log Message: ----------- minor edits Commit: 8753103696e5b52ad679405817ed790fd99b3ee6 https://github.com/qos-ch/logback/commit/8753103696e5b52ad679405817ed790fd9… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2017-11-29 (Wed, 29 Nov 2017) Changed paths: M logback-classic/pom.xml A logback-classic/src/main/java/ch/qos/logback/classic/provider/LogbackServiceProvider.java M logback-classic/src/test/java/ch/qos/logback/classic/LoggerPerfTest.java M logback-classic/src/test/java/ch/qos/logback/classic/boolex/GEventEvaluatorTest.java M logback-classic/src/test/java/ch/qos/logback/classic/spi/LoggingEventSerializationPerfTest.java M logback-classic/src/test/java/ch/qos/logback/classic/turbo/ReconfigureOnChangeTest.java M pom.xml Log Message: ----------- ongoing work - upgrading to slf4j 1.8 service provider api Compare: https://github.com/qos-ch/logback/compare/81951177471b...8753103696e5

1 0

[qos-ch/logback] 819511: add Christian Lorenz
by Ceki Gulcu 29 Nov '17

29 Nov '17

Branch: refs/heads/master Home: https://github.com/qos-ch/logback Commit: 81951177471b28ee45451d5f6ffa60bb9fa5c13e https://github.com/qos-ch/logback/commit/81951177471b28ee45451d5f6ffa60bb9f… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2017-11-29 (Wed, 29 Nov 2017) Changed paths: M src/main/clas/signed-clas.txt Log Message: ----------- add Christian Lorenz

1 0

JDK 10 Early Access b33 and JDK 8u162 Early Access b03 are available on jdk.java.net
by Rory O'Donnell 28 Nov '17

28 Nov '17

Hi Ceki, *JDK 10 Early Access build 33 is available at : - **jdk.java.net/10/* Notable changes since previous email. <http://bugs.openjdk.java.net/browse/JDK-8175094>JDK-8180019 <http://bugs.openjdk.java.net/browse/JDK-8180019> - *javadoc treats failure to access a URL as an error , not a warning.* If javadoc cannot access the contents of a URL provided with the -link or -linkoffline options,the tool will now report an error. Previously, the tool continued with a warning, producing incorrect documentation output. JDK-8175094 <http://bugs.openjdk.java.net/browse/JDK-8175094>*- **The java.security.acl APIs are deprecated, for removal**** * The deprecated java.security.acl APIs are now marked with forRemoval=true and are subject to removal in a future version of Java SE. JDK-8175091 <http://bugs.openjdk.java.net/browse/JDK-8175091> *- The java.security.{Certificate,Identity,IdentityScope,Signer} APIs are deprecated, for removal* The deprecated java.security.{Certificate, Identity, IdentityScope, Signer} classes are now marked with forRemoval=true and are subject to removal in a future version of Java SE. JDK 10 Schedule, Status & Features are available [1] Notes * OpenJDK EA binaries will be available at a later date. * Oracle has proposed: Newer version-string scheme for the Java SE Platform and the JDK o Please see Mark Reinhold's proposal [2] *JDK 8u162 Early Access build 03 is available at :- http://jdk.java.net/8/* <http://openjdk.java.net/projects/jdk8u/releases/8u162.html> *Feedback* - If you have suggestions or encounter bugs, please submit them using the usual Java SE bug-reporting channel. Be sure to include complete version information from the output of the |java --version| command. Regards, Rory [1] http://openjdk.java.net/projects/jdk/10/ [2] http://mail.openjdk.java.net/pipermail/jdk-dev/2017-November/000089.html -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA , Dublin, Ireland

1 0

[JIRA] (LOGBACK-1322) File handles to tmp file kept open after rotation
by QOS.CH (JIRA) 24 Nov '17

24 Nov '17

1 0

[JIRA] (LOGBACK-1297) Logback fails to roll once the file count exceeds 1000
by QOS.CH (JIRA) 16 Nov '17

16 Nov '17

1 0