- logback-dev - mailman3.qos.ch

[JIRA] (LOGBACK-1515) java.lang.ClassNotFoundException: javax.naming.NamingException on JDK 14 jlink build
by QOS.CH (JIRA) 10 Apr '20

10 Apr '20

1 0

[JIRA] (LOGBACK-1408) Reconfigure with scan feature ignores changes made to JoranConfigurator
by QOS.CH (JIRA) 10 Apr '20

10 Apr '20

1 0

OpenJDK 15 EA build 18 is now available
by Rory O'Donnell 10 Apr '20

10 Apr '20

Hi Ceki, OpenJDK 15 EA build 18 is now available at http://jdk.java.net/15 * * * 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>. * Schedule for JDK 15 o 2020/06/11 Rampdown Phase One o 2020/07/16 Rampdown Phase Two o 2020/08/06 Initial Release Candidate o 2020/08/20 Final Release Candidate o 2020/09/15 General Availability * Features o Proposed to target JDK 15 + JEP 371: <http://openjdk.java.net/jeps/371> Hidden Classes o JEPs targeted to JDK 15 + JEP 372 <https://openjdk.java.net/jeps/372>: Remove the Nashorn JavaScript Engine + JEP 377 <https://openjdk.java.net/jeps/377>: ZGC: A Scalable Low-Latency Garbage Collector + JEP 378 <https://openjdk.java.net/jeps/378>: Text Blocks + JEP 379 <https://openjdk.java.net/jeps/379>: Shenandoah: A Low-Pause-Time Garbage Collector * Changes in recent builds that maybe of interest: o build 18 + JDK-8240169 <https://bugs.openjdk.java.net/browse/JDK-8240169>: javadoc fails to link to non-modular api docs # Reported by JUnit5 + JDK-8241670 <https://bugs.openjdk.java.net/browse/JDK-8241670>: Enhance heap region size ergonomics to improve OOTB performance + JDK-8240745 <https://bugs.openjdk.java.net/browse/JDK-8240745>: Implementation: JEP 377: ZGC: A Scalable Low-Latency Garbage Collector (Production) + JDK-8225319 <https://bugs.openjdk.java.net/browse/JDK-8225319>: Remove rmic from the set of supported tools + JDK-8237490 <https://bugs.openjdk.java.net/browse/JDK-8237490>: Add support notarizing jpackage app-image and dmg o build 17 + JDK-8240676 <https://bugs.openjdk.java.net/browse/JDK-8240676> - Meet not symmetric failure when running lucene on jdk8 # Reported by Apache Lucene o Build 16 + JDK-8241039 <https://bugs.openjdk.java.net/browse/JDK-8241039> - Retire the deprecated SSLSession.getPeerCertificateChain() method + JDK-8219989 <https://bugs.openjdk.java.net/browse/JDK-8219989> - Retire the com.sun.net.ssl.internal.ssl.Provider name + JDK-8237859 <https://bugs.openjdk.java.net/browse/JDK-8237859> - C2: Crash when loads float above range check # Reported by Apache Lucene + JDK-8202469 <https://bugs.openjdk.java.net/browse/JDK-8202469> - (ann) Type annotations on type variable bounds that are also type variables are lost # Reported by ByteBuddy o Build 15 + JDK-8214245 <https://bugs.openjdk.java.net/browse/JDK-8214245> - Case insensitive matching doesn't work correctly for some character classes () * Quality Report for March 2020 was published here [1] o Thanks again for all the bug reports and feeback! Does your Project support JDK 14 - #AllTestsGreenOnJDK14 <https://twitter.com/hashtag/AllTestsGreenOnJDK14?src=hashtag_click> Rgds,Rory [1] https://wiki.openjdk.java.net/display/quality/Quality+Outreach+report+March… -- Rgds, Rory O'Donnell Quality Engineering Manager Oracle EMEA, Dublin, Ireland

1 0

[JIRA] (LOGBACK-1515) java.lang.ClassNotFoundException: javax.naming.NamingException on JDK 14 jlink build
by QOS.CH (JIRA) 09 Apr '20

09 Apr '20

R A D Melvin created LOGBACK-1515: ------------------------------------- Summary: java.lang.ClassNotFoundException: javax.naming.NamingException on JDK 14 jlink build Key: LOGBACK-1515 URL: https://jira.qos.ch/browse/LOGBACK-1515 Project: logback Issue Type: Bug Components: logback-classic Affects Versions: 1.3.0-alpha5 Environment: Building a project that uses logback-classic 1.3.0-alpha5, everything compiles ok. jlink successfully produces a jlink-image with a launcher. Running the launcher gives: {code:java} Caused by: java.lang.NoClassDefFoundError: javax/naming/NamingException at ch.qos.logback.classic/ch.qos.logback.classic.joran.JoranConfigurator.addInstanceRules(JoranConfigurator.java:48) at ch.qos.logback.core/ch.qos.logback.core.joran.GenericConfigurator.buildInterpreter(GenericConfigurator.java:134) at ch.qos.logback.core/ch.qos.logback.core.joran.JoranConfiguratorBase.buildInterpreter(JoranConfiguratorBase.java:95) at ch.qos.logback.core/ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:162) at ch.qos.logback.core/ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:152) at ch.qos.logback.core/ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:110) at ch.qos.logback.core/ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:53) at ch.qos.logback.classic/ch.qos.logback.classic.util.ContextInitializer.configureByResource(ContextInitializer.java:82) at ch.qos.logback.classic/ch.qos.logback.classic.util.ContextInitializer.autoConfig(ContextInitializer.java:157) at ch.qos.logback.classic/ch.qos.logback.classic.spi.LogbackServiceProvider.initializeLoggerContext(LogbackServiceProvider.java:49) at ch.qos.logback.classic/ch.qos.logback.classic.spi.LogbackServiceProvider.initialize(LogbackServiceProvider.java:40) at org.slf4j/org.slf4j.LoggerFactory.bind(LoggerFactory.java:152) at org.slf4j/org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:139) at org.slf4j/org.slf4j.LoggerFactory.getProvider(LoggerFactory.java:418) at org.slf4j/org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:404) at org.slf4j/org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:353) at org.slf4j/org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:379) at esa.sect.app(a)0.0.0-SNAPSHOT/esa.sect.tool.commands.BulkImportCommand.<clinit>(BulkImportCommand.java:56) at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.base/java.lang.reflect.Constructor.newInstanceWithCaller(Constructor.java:500) at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:481) at java.base/java.util.ServiceLoader$ProviderImpl.newInstance(ServiceLoader.java:782) ... 4 more Caused by: java.lang.ClassNotFoundException: javax.naming.NamingException at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:602) at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178) at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:522) ... 28 more{code} The line that fails is where it create an object of a class that has an import of jaxax.naming.NamingException. Any clues? Reporter: R A D Melvin Assignee: Logback dev list -- This message was sent by Atlassian Jira (v8.8.0#808000)

1 0

[JIRA] (LOGBACK-1027) Circular Referenced Suppressed Exception Throws StackOverflowError
by QOS.CH (JIRA) 09 Apr '20

09 Apr '20

1 0

[JIRA] (LOGBACK-1454) StackOverflow error
by QOS.CH (JIRA) 09 Apr '20

09 Apr '20

1 0

[JIRA] (LOGBACK-1408) Reconfigure with scan feature ignores changes made to JoranConfigurator
by QOS.CH (JIRA) 08 Apr '20

08 Apr '20

1 0

[JIRA] (LOGBACK-1205) CheckForCollisions methods can cause performance issue
by QOS.CH (JIRA) 06 Apr '20

06 Apr '20

1 0

[JIRA] (LOGBACK-1514) Add possibity for separate logging for JPMS module/layers
by QOS.CH (JIRA) 05 Apr '20

05 Apr '20

Pavel_K created LOGBACK-1514: -------------------------------- Summary: Add possibity for separate logging for JPMS module/layers Key: LOGBACK-1514 URL: https://jira.qos.ch/browse/LOGBACK-1514 Project: logback Issue Type: New Feature Reporter: Pavel_K Assignee: Logback dev list I suggest to add possibility for separate logging for JPMS module/layers. For example, it would be possible to route messages from different modules/layers to separate log files. Such feature was also discussed in jigsaw mailing list [http://mail.openjdk.java.net/pipermail/jigsaw-dev/2018-October/013941.html] and for Log4j2 [https://issues.apache.org/jira/browse/LOG4J2-2464] P.S. I hope that this feature request won't be deleted without any explanation. -- This message was sent by Atlassian Jira (v8.8.0#808000)

1 0

[JIRA] (LOGBACK-1513) [logback-access] Wrong duration reported by LogbackValve with spring-webflux
by QOS.CH (JIRA) 03 Apr '20

03 Apr '20

Guillaume DROUET created LOGBACK-1513: ----------------------------------------- Summary: [logback-access] Wrong duration reported by LogbackValve with spring-webflux Key: LOGBACK-1513 URL: https://jira.qos.ch/browse/LOGBACK-1513 Project: logback Issue Type: Bug Environment: Spring Webflux manages request processing through reactive streams Publisher so if we want to log the request duration we have to wait for the end of the subscription which writes to the response. The problem with LogbackValve is when it calculates the elapsed time in the AccessEvent just after calling getNext().invoke, which is actually the duration of Publisher's creation and not the time it takes to subscribe to it and write to the HTTP response. Reporter: Guillaume DROUET Assignee: Logback dev list -- This message was sent by Atlassian Jira (v8.8.0#808000)

1 0