- logback-dev - mailman3.qos.ch

[JIRA] (LOGBACK-1497) Empty default variable value results in _IS_UNDEFINED
by QOS.CH (JIRA) 21 Jan '20

21 Jan '20

Neeme Praks created LOGBACK-1497: ------------------------------------ Summary: Empty default variable value results in _IS_UNDEFINED Key: LOGBACK-1497 URL: https://jira.qos.ch/browse/LOGBACK-1497 Project: logback Issue Type: Bug Components: logback-core Affects Versions: 1.2.3 Reporter: Neeme Praks Assignee: Logback dev list Priority: Minor Config file: {code:xml} <?xml version="1.0" encoding="UTF-8"?> <configuration> <appender name="HUMAN" class="ch.qos.logback.core.FileAppender"> <file>test.log</file> <encoder class="ch.qos.logback.classic.encoder.PatternLayoutEncoder"> <Pattern>%d{yyyy-MM-dd HH:mm:ss.SSS} [%thread] %level %logger{35} - %msg ${log.pattern.suffix:-}%n</Pattern> </encoder> </appender> <root level="INFO"> <appender-ref ref="HUMAN" /> </root> </configuration> {code} The variable ${log.pattern.suffix} is not defined. *Observed behaviour*: ${log.pattern.suffix:-} is replaced with "log.pattern.suffix_IS_UNDEFINED" *Expected behaviour*: ${log.pattern.suffix:-} should be replaced with empty string (as there is empty string after ":-". -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[qos-ch/logback] 8fce9b: update link to Maven central
by Ceki Gulcu 19 Jan '20

19 Jan '20

Branch: refs/heads/master Home: https://github.com/qos-ch/logback Commit: 8fce9b34c9ea1a29030c7513e3b91b9b80045fc3 https://github.com/qos-ch/logback/commit/8fce9b34c9ea1a29030c7513e3b91b9b80… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2020-01-19 (Sun, 19 Jan 2020) Changed paths: M logback-site/src/site/pages/download.html Log Message: ----------- update link to Maven central Commit: 7ee74ad132bf74ead68c5bb553f5353aa2588bb0 https://github.com/qos-ch/logback/commit/7ee74ad132bf74ead68c5bb553f5353aa2… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2020-01-19 (Sun, 19 Jan 2020) Changed paths: M src/main/clas/signed-clas.txt Log Message: ----------- Merge branch 'master' of github.com:qos-ch/logback Compare: https://github.com/qos-ch/logback/compare/b5baeb47bacd...7ee74ad132bf

1 0

JDK 14 is now in Rampdown Phase Two
by Rory O'Donnell 17 Jan '20

17 Jan '20

Hi Ceki, *Per the JDK 14 schedule , we are now in Rampdown Phase Two * *Please advise if you have any open high priority issues.* ** * The overall feature set is frozen. o No further JEPs will be targeted to this release o Per the JDK Release Process [1] we now turn our focus to P1 and P2 bugs. o For more details , see Mark Reinhold's email to jdk-dev mailing list [2] JDK 14 Early Access build 32 is availableat : - jdk.java.net/14/ * These early-access , open-source builds are provided under the o GNU General Public License, version 2, with the Classpath Exception <http://openjdk.java.net/legal/gplv2+ce.html>. * Recent fixes that maybe of interest: o Build 32 + JDK-8230318: Better trust store usage + JDK-8225773: jdeps --check produces NPE if there is any missing module dependence # reported by JUnit5 + JDK-8235870: C2 crashes in IdealLoopTree::est_loop_flow_merge_sz() # duplicate of Apache Lucene's bug. o Build 31 + JDK-8235984: C2: assert(out->in(PhiNode::Region) == head || out->in(PhiNode::Region) == slow_head) failed: phi must be either part of the slow or the fast loop # duplicate of JDK-8236412 reported by Apache Lucene. + JDK-8236695: java.lang.Record should be declared with an explicit constructor JDK 15 Early Access build 6 is availableat : - jdk.java.net/15/ * These early-access , open-source builds are provided under the o GNU General Public License, version 2, with the Classpath Exception <http://openjdk.java.net/legal/gplv2+ce.html>. * Release notes o http://jdk.java.net/15/release-notes * Recent fixes that maybe of interest : o Build 6 + JDK-7143743: Potential memory leak with zip provider # Contributed by Jaikiran! + JDK-8213222: remove RMIConnectorServer.CREDENTIAL_TYPES + JDK-8235870: C2 crashes in IdealLoopTree::est_loop_flow_merge_sz() # duplicate of Apache Lucene's bug. o Build 5 + JDK-8227313: Support monetary grouping separator in DecimalFormat/DecimalFormatSymbols + JDK-8236695: java.lang.Record should be declared with an explicit constructor *Invitation to Project Skara update and demo, January 22, 2020, 8:30 am PST * * See Joe Darcy's email [3]* * ** Rgds, Rory  [1] http://openjdk.java.net/jeps/3 [2] https://mail.openjdk.java.net/pipermail/jdk-dev/2020-January/003846.html [3] https://mail.openjdk.java.net/pipermail/discuss/2020-January/005274.html -- Rgds, Rory O'Donnell Quality Engineering Manager Oracle EMEA, Dublin, Ireland

1 0

[JIRA] (LOGBACK-1496) Add support for overriding default LogbackMDCAdapter
by QOS.CH (JIRA) 14 Jan '20

14 Jan '20

Sami Korhone created LOGBACK-1496: ------------------------------------- Summary: Add support for overriding default LogbackMDCAdapter Key: LOGBACK-1496 URL: https://jira.qos.ch/browse/LOGBACK-1496 Project: logback Issue Type: Improvement Components: logback-classic Reporter: Sami Korhone Assignee: Logback dev list Priority: Minor Currently LogbackServiceProvider creates instance of MDCAdapter using _new_ operator. If a MDCAdapter was created using ServiceLoader and LogbackMDCAdapter was set as default provider, if no other was found, frameworks (such as spring webflux) could override default implementation of MDCAdapter. Proposed change would allow frameworks to support MDC that is bound to request rather than to currently executing thread. Currently users are forced to rebind either use mapped diagnostic context other than MDC or to bind variables for every logging event Code that needs to be changed: [https://github.com/qos-ch/logback/blob/b5baeb47bacdd64190d1c10f119f810b3977…] -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

JDK 14 Early Access build 30 & JDK 15 Early Access build 4 are available.
by Rory O'Donnell 06 Jan '20

06 Jan '20

Hi Ceki, Happy New Year ! *Per the JDK 14 schedule , we are now in Rampdown Phase One* *Please advise if you have found any issues while testing the latest Early Access build. * * The overall feature set is frozen. o No further JEPs will be targeted to this release o For more details , see Mark Reinhold's email to jdk-dev mailing list [1] *JDK 14 **Early Access build 30 **is available**at : - jdk.java.net/14/* * These early-access , open-source builds are provided under the o GNU General Public License, version 2, with the Classpath Exception <http://openjdk.java.net/legal/gplv2+ce.html>. * Release notes o https://jdk.java.net/14/release-notes * Recent fixes that might be of interest o Build 29: + JDK-8233228: Disable weak named curves by default in TLS, CertPath, and Signed JAR o Build 28: + JDK-8234049: Implementation of Memory Access API (Incubator) + JDK-8235668: LineNumberReader#getLineNumber() returns wrong line number (one fewer) in Lucene test # Reported by Apache Lucene *JDK 15 **Early Access build 4 **is available**at : - jdk.java.net/15/* * These early-access , open-source builds are provided under the o GNU General Public License, version 2, with the Classpath Exception <http://openjdk.java.net/legal/gplv2+ce.html>. * Release notes o http://jdk.java.net/15/release-notes The Quality Outreach Report for Decemeber 2019 was published since the last email * https://wiki.openjdk.java.net/display/quality/Quality+Outreach+report+Decem… * Many thanks to all those who contributed to testing, logging bugs etc against the Early Access builds. * * Rgds, Rory [1] https://mail.openjdk.java.net/pipermail/jdk-dev/2019-December/003795.html -- Rgds, Rory O'Donnell Quality Engineering Manager Oracle EMEA, Dublin, Ireland

1 0

[JIRA] (LOGBACK-1495) logevent can not be written into file when config file is loading
by QOS.CH (JIRA) 06 Jan '20

06 Jan '20

liuzhiqiang created LOGBACK-1495: ------------------------------------ Summary: logevent can not be written into file when config file is loading Key: LOGBACK-1495 URL: https://jira.qos.ch/browse/LOGBACK-1495 Project: logback Issue Type: Bug Components: logback-core Affects Versions: 1.2.3 Environment: slf4j-api-1.7.29 logback-core-1.2.3 logback-classic-1.2.3 Reporter: liuzhiqiang Assignee: Logback dev list Priority: Critical first,use jdb command to start the log program then set some breakpoints as follows: stop at ch.qos.logback.core.spi.AppenderAttachableImpl:50 stop at ch.qos.logback.core.spi.AppenderAttachableImpl:51 stop at ch.qos.logback.core.joran.spi.ConfigurationWatchList:83 stop at ch.qos.logback.core.spi.AppenderAttachableImpl:109 run ----------------------------------------------- hit breakpoint ch.qos.logback.core.spi.AppenderAttachableImpl:50 find main thread id, suspend 【main thread id】, execute cont command hit breakpoint ch.qos.logback.core.joran.spi.ConfigurationWatchList:83 now ,let us change our config file ,save it, go back to debug tool interface,execute cont command hit breakpoint ch.qos.logback.core.spi.AppenderAttachableImpl:109 execute next command, appenderList will be cleared, suspend current thread id, and resume main thread, then let us execute cont command hit breakpoint ch.qos.logback.core.spi.AppenderAttachableImpl:51 step debug from here, u can find something as follows: !https://oscimg.oschina.net/oscnet/up-4bb53de3e7d503199323c2cd8ec0b7ad4d8.png! -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

suggestion/feature request: tell us *why* it is outputting configuration info
by Roger Pack 23 Dec '19

23 Dec '19

As a note, many of us have run into this behavior: we use logback, it works great. Then we add something, suddenly logback is outputting a lot of "configuration" information and it's not clear why. ex: https://stackoverflow.com/questions/3257154/how-to-prevent-logback-from-out… Suggestion/feature request: if logback outputs configuration information because of a configuration problem (for instance, if we have debug set to false already), add a line at the top of the output 'loopback: outputting debug information because configuration issue detected" or something like that. Would help clear up confusion at least in my case. Thank you! -Roger-

1 0

documentation is confusing
by Roger Pack 19 Dec '19

19 Dec '19

As a note, when I go and look for "how do I format the config files again"? What I want are some details in this page: http://logback.qos.ch/manual/layouts.html#conversionWord However, the top of that page is...pretty confusing. It discusses java objects and custom events. It's pretty confusing and makes it hard to find. https://stackoverflow.com/questions/3881242/where-is-logback-encoder-patter… Might be worth considering a cleanup somehow. Some of the other doc pages have a similar feel FWIW. Thank you, -Roger pack-

1 0

JDK 14 enters Rampdown Phase One
by Rory O'Donnell 14 Dec '19

14 Dec '19

Hi Ceki, *Per the JDK 14 schedule , we are now in Rampdown Phase One* *Please advise if you have found any issues while testing the latest Early Access build. * * Schedule for JDK 14 o *2019/12/12 Rampdown Phase One* o 2020/01/16 Rampdown Phase Two o 2020/02/06 Initial Release Candidate o 2020/02/20 Final Release Candidate o 2020/03/17 General Availability * The overall feature set is frozen. o No further JEPs will be targeted to this release o For more details , see Mark Reinhold's email to jdk-dev mailing list [1] * Features included in JDK 14:. o JEP 305: Pattern Matching for instanceof (Preview) <http://openjdk.java.net/jeps/305> o JEP 343: Packaging Tool (Incubator) <http://openjdk.java.net/jeps/343> o JEP 345: NUMA-Aware Memory Allocation for G1 <http://openjdk.java.net/jeps/345> o JEP 349: JFR Event Streaming <http://openjdk.java.net/jeps/349> o JEP 352: Non-Volatile Mapped Byte Buffers <http://openjdk.java.net/jeps/352> o JEP 358: Helpful NullPointerExceptions <https://openjdk.java.net/jeps/358> o JEP 359: Records (Preview) <http://openjdk.java.net/jeps/359> JEP 359: Records (Preview) <http://openjdk.java.net/jeps/359> o JEP 361: Switch Expressions (Standard) <http://openjdk.java.net/jeps/361> o JEP 362: Deprecate the Solaris and SPARC Ports <https://openjdk.java.net/jeps/362> o JEP 363: Remove the Concurrent Mark Sweep Garbage Collector <http://openjdk.java.net/jeps/363> o JEP 364: ZGC on macOS <http://openjdk.java.net/jeps/364> o JEP 365 ZGC on Windows <https://openjdk.java.net/jeps/365> o JEP 366: Deprecate ParallelScavenge SerialOld GC Combination <http://openjdk.java.net/jeps/366> o JEP 367: Remove the Pack200 Tools and API <http://openjdk.java.net/jeps/367> o JEP 368: Text Blocks (Second Preview) <http://openjdk.java.net/jeps/368> o JEP 370: Foreign-Memory Access API (Incubator) <https://openjdk.java.net/jeps/370> *JDK 14 **Early Access build 27 **is available**at : - jdk.java.net/14/* * Release notes o https://jdk.java.net/14/release-notes * Recent fixes that might be of interest o Build 27: + JDK-8212780: Packaging Tool Implementation + JDK-8234370: Implementation of JEP 362: Deprecate the Solaris and SPARC Ports + JDK-8190492: Remove SSLv2Hello and SSLv3 from default enabled TLS protocols + JDK-8214481: freetype path does not disable TrueType hinting with AA+FM hints + JDK-8234076: JVM crashes on Windows 10 using --module=NAME + JDK-8222756: Plural support in CompactNumberFormat + JDK-8234211: allow discoverable javac plugins to be invoked by default o Build 26: + JDK-8233223: Add Amazon Root CA certificates + JDK-8235263: Revert TLS 1.3 change that wrapped IOExceptions + JDK-8234893: ARM32: build failure after JDK-8234387 Rgds, Rory [1] https://mail.openjdk.java.net/pipermail/jdk-dev/2019-December/003795.html -- Rgds, Rory O'Donnell Quality Engineering Manager Oracle EMEA, Dublin, Ireland

1 0

[JIRA] (LOGBACK-1494) logback
by QOS.CH (JIRA) 09 Dec '19

09 Dec '19

xiaoyushang created LOGBACK-1494: ------------------------------------ Summary: logback Key: LOGBACK-1494 URL: https://jira.qos.ch/browse/LOGBACK-1494 Project: logback Issue Type: Bug Reporter: xiaoyushang Assignee: Logback dev list Thread-56 "[STUCK] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'" <alive, suspended, blocked, priority=1, DAEMON> \{ -- Blocked trying to get lock: java.lang.Object@10109229[fat lock] ch.qos.logback.core.OutputStreamAppender.subAppend(OutputStreamAppender.java:205) ch.qos.logback.core.rolling.RollingFileAppender.subAppend(RollingFileAppender.java:142) ch.qos.logback.core.OutputStreamAppender.append(OutputStreamAppender.java:104) ch.qos.logback.core.UnsynchronizedAppenderBase.doAppend(UnsynchronizedAppenderBase.java:70) ch.qos.logback.core.spi.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:60) ch.qos.logback.classic.Logger.appendLoopOnAppenders(Logger.java:282) ch.qos.logback.classic.Logger.callAppenders(Logger.java:268) ch.qos.logback.classic.Logger.buildLoggingEventAndAppend(Logger.java:469) ch.qos.logback.classic.Logger.filterAndLog_0_Or3Plus(Logger.java:413) ch.qos.logback.classic.Logger.info(Logger.java:629) com.yinzhijie.trans.log.TransXmlHandle.writeLog(TransXmlHandle.java:58) com.yinzhijie.trans.service.HttpTransProvider.doGetAndPost(HttpTransProvider.java:87) com.yinzhijie.trans.servlet.HttpFileTrans.doSomeThing(HttpFileTrans.java:43) com.yinzhijie.trans.servlet.HttpFileTrans.doGet(HttpFileTrans.java:35) javax.servlet.http.HttpServlet.service(HttpServlet.java:700) javax.servlet.http.HttpServlet.service(HttpServlet.java:815) weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:224) weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:108) weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:207) weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:184) weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3702) weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3696) weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:308) weblogic.security.service.SecurityManager.runAs(SecurityManager.java:116) weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2209) weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2131) weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1457) weblogic.work.ExecuteThread.execute(ExecuteThread.java:250) weblogic.work.ExecuteThread.run(ExecuteThread.java:213) } -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0