March 2017 - logback-dev - mailman3.qos.ch

[JIRA] (LOGBACK-1276) %msg dissapear ( empty message log )
by QOS.CH (JIRA) 10 Mar '17

10 Mar '17

Dani Vainstein created LOGBACK-1276: --------------------------------------- Summary: %msg dissapear ( empty message log ) Key: LOGBACK-1276 URL: https://jira.qos.ch/browse/LOGBACK-1276 Project: logback Issue Type: Bug Components: logback-classic Environment: Windows7 Reporter: Dani Vainstein Assignee: Logback dev list *String* s = "ALL|RANDOM|NONE"; log.error( "My Message is :", s ); log.info( "My Message is : ", s ); log: 00:53:05.576 start-up-context | ERROR | <main> | "XlsRunnerParser.java" [ XlsRunnerParser.parse:118 ] - My Message is : 00:53:08.077 start-up-context | INFO | <main> | "XlsRunnerParser.java" [ XlsRunnerParser.parse:119 ] - My Message is : {color:#ff0000}The message is not printed!!{color} -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-1275) Make use of StackWalker API
by QOS.CH (JIRA) 09 Mar '17

09 Mar '17

1 0

[JIRA] (LOGBACK-1275) Make use of StackWalker API
by QOS.CH (JIRA) 09 Mar '17

09 Mar '17

Ceki Gülcü created LOGBACK-1275: ----------------------------------- Summary: Make use of StackWalker API Key: LOGBACK-1275 URL: https://jira.qos.ch/browse/LOGBACK-1275 Project: logback Issue Type: Improvement Components: logback-classic Environment: Make use of StackWalker API introduced in Java 9 Reporter: Ceki Gülcü Assignee: Logback dev list Fix For: 1.2.2 -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-1274) Logback swallows output from Exceptions overriding toString()
by QOS.CH (JIRA) 08 Mar '17

08 Mar '17

Claus created LOGBACK-1274: ------------------------------ Summary: Logback swallows output from Exceptions overriding toString() Key: LOGBACK-1274 URL: https://jira.qos.ch/browse/LOGBACK-1274 Project: logback Issue Type: Bug Components: logback-classic Affects Versions: 1.2.1 Environment: Windows, Java 8 Reporter: Claus Assignee: Logback dev list Attachments: logback.xml, LoggerTest.java When logging exceptions that overwrite toString() then logback ignores the output of it. For example: {code:java} class OverridingException extends Exception { @Override public String toString() { return super.toString() + " important additional information"; } }{code} When used with logback the following code {code:java} @Test public void testName() { org.slf4j.Logger logger = LoggerFactory.getLogger(LoggerTest.class); try { throw new OverridingException(); } catch (Throwable t) { logger.error("", t); } }{code} produces output without the string "important additional information" {code:java} 2017-03-08 16:44:27 [main] ERROR trial.LoggerTest - trial.LoggerTest$OverridingException: null at trial.LoggerTest.testName(LoggerTest.java:32){code} while Java Util Logging outputs correctly {code:java} Mär 08, 2017 4:44:27 PM trial.LoggerTest testLogging SCHWERWIEGEND: trial.LoggerTest$OverridingException important additional information at trial.LoggerTest.testLogging(LoggerTest.java:22){code} Testfile and logback.xml attached. -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-1011) SyslogAppender support for configurable hostname
by QOS.CH (JIRA) 08 Mar '17

08 Mar '17

1 0

[JIRA] (LOGBACK-1273) Missing documentation regarding groovy configuration of LevelChangePropagator
by QOS.CH (JIRA) 07 Mar '17

07 Mar '17

Joern Huxhorn created LOGBACK-1273: -------------------------------------- Summary: Missing documentation regarding groovy configuration of LevelChangePropagator Key: LOGBACK-1273 URL: https://jira.qos.ch/browse/LOGBACK-1273 Project: logback Issue Type: Improvement Components: logback-classic Affects Versions: 1.2.1 Environment: any Reporter: Joern Huxhorn Assignee: Logback dev list The documentation is missing info about how to enable {{LevelChangePropagator}} in a {{logback.groovy}} file. I came up with this: {code:java} LevelChangePropagator levelChangePropagator = new LevelChangePropagator() levelChangePropagator.setContext(context) levelChangePropagator.start() context.addListener(levelChangePropagator) {code} Is there a better/easier way I'm missing? Current approach is modeled after what the XML implementation is doing... -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-1272) Make logback in SL4J show relative time (%r) in hours, minutes and seconds
by QOS.CH (JIRA) 04 Mar '17

04 Mar '17

Stefano created LOGBACK-1272: -------------------------------- Summary: Make logback in SL4J show relative time (%r) in hours, minutes and seconds Key: LOGBACK-1272 URL: https://jira.qos.ch/browse/LOGBACK-1272 Project: logback Issue Type: Improvement Components: logback-classic, logback-core Affects Versions: 1.2.1 Reporter: Stefano Assignee: Logback dev list Priority: Minor I know that {{%r}} in logback outputs the relative time from the start of the logging event in milliseconds, but it seems that there's not way to set it in a pattern like {{HH.mm.ss.SSS}}. Unfortunately, something along the lines of {{%r\{HH.mm.ss.SSS}}} (which is the way I do it for the current date/time {{%d}}) doesn't work. I can of course build a {{StopWatch}} object and manually output its value every time I call the logger, but this way seems rather unpractical. Such a feature would be quite useful I think, and I was also suggested to post a feature request here after asking a similar question on [stackoverflow|http://stackoverflow.com/questions/42579880/make-logback-in-s…] -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

JDK 9 EA Build 159 and JDK 8u152 is available on java.net
by Rory O'Donnell 03 Mar '17

03 Mar '17

Hi Ceki, *JDK 8u152 **Early Access b01 <https://jdk8.java.net/download.html> *is available on java.net *JDK 9 Early Access* b159 <https://jdk9.java.net/download/> is available on java.net, summary of changes are listed here <http://download.java.net/java/jdk9/changes/jdk-9+159.html>. There have been a number of fixes to bugs reported by Open Source projects since the last availability email : * b159 - JDK-8175261 : Per-protocol cache setting not working for JAR URLConnection * b158 - JDK-8173028 : Incorrect processing of supplementary-plane characters in text fields * b158 - JDK-8172967 : [macosx] Exception while working with layout for text containing unmappable character * b158 - JDK-8173804 : javadoc throws UnsupportedOperationException: should not happen * b157 - JDK-8174073 : NPE caused by @link reference to class * b156 - JDK-8172726 : ForkJoin common pool retains a reference to the thread context class loader The following changeset is included in jdk-9+158: http://hg.openjdk.java.net/jdk9/dev/jdk/rev/8b0d55e02f54 If you have a user-defined Policy implementation that grants FilePermission on ${user.dir}/-, reading a file in the current directory using its base name will fail. Still the same solution: Ensure that the path used in permission granting has the same style as the one how you access the file. Setting -Djdk.security.filePermCompat=true will take you back to the jdk-9+140 behavior. Setting -Djdk.io.permissionsUseCanonicalPath=true will take you back to the jdk8 behavior. Feedback is welcome on jdk9-dev(a)openjdk.java.net Other areas of interest * JDK 9 Developer Guide [1] * JDK 9 Migration Guide [2] * JDK Cryptographic Roadmap [3] Finaly, Dalibor and I gave a presentation at FOSDEM the video is available here [*4*] Rgds,Rory [1] http://docs.oracle.com/javase/9/javase-docs.htm [2] https://docs.oracle.com/javase/9/migrate/toc.htm#JSMIG-GUID-7744EF96-5899-4… [3] https://www.java.com/en/jre-jdk-cryptoroadmap.html [4] https://fosdem.org/2017/schedule/event/outreach/ -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA , Dublin, Ireland

1 0

[JIRA] (LOGBACK-1270) PatternLayoutBase concurrent access race condition
by QOS.CH (JIRA) 01 Mar '17

01 Mar '17

1 0

[JIRA] (LOGBACK-1270) PatternLayoutBase concurrent access race condition
by QOS.CH (JIRA) 01 Mar '17

01 Mar '17

1 0