- logback-dev - mailman3.qos.ch

[JIRA] (LOGBACK-632) Add timeout attribute to SMTP appender
by QOS.CH (JIRA) 21 Jan '19

21 Jan '19

1 0

[JIRA] (LOGBACK-632) Add timeout attribute to SMTP appender
by QOS.CH (JIRA) 21 Jan '19

21 Jan '19

1 0

JDK 12 enters Rampdown Phase Two
by Rory O'Donnell 21 Jan '19

21 Jan '19

Hi Ceki, **OpenJDK builds *- JDK 12 Early Access build 28 **is now available **at : - jdk.java.net/12/* * Per the JDK 12 schedule [1], we are now in Rampdown Phase Two. o For more details , see Mark Reinhold's email to jdk-dev mailing list [2] o The overall feature set is frozen, no further JEPs will be targeted to this release. o Per the JDK Release Process [3] we now turn our focusto P1 and P2 bugs. **OpenJDK builds *- JDK 13 Early Access build 4 is **now available **at : - jdk.java.net/13/* * 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/13/release-notes * Changes in this build <http://hg.openjdk.java.net/jdk/jdk/log?rev=reverse%28%22jdk-13%2B3%22%3A%3A…> Blog Updates from Java SE Product Management since last email. * Oracle Java SE Releases FAQ [3] * Oracle Java SE Support Roadmap [4] Rgds,Rory [1] http://openjdk.java.net/projects/jdk/12/#Schedule [2] http://mail.openjdk.java.net/pipermail/jdk-dev/2019-January/002537.html [3] https://blogs.oracle.com/java-platform-group/oracle-java-se-releases-faq [4] https://www.oracle.com/technetwork/java/java-se-support-roadmap.html -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA , Dublin, Ireland

1 0

[JIRA] (LOGBACK-1454) StackOverflow error
by QOS.CH (JIRA) 17 Jan '19

17 Jan '19

1 0

[JIRA] (LOGBACK-1454) StackOverflow error
by QOS.CH (JIRA) 17 Jan '19

17 Jan '19

1 0

[JIRA] (LOGBACK-1421) Logback 1.2.3 threads getting deadlocked at CachingDateFormatter
by QOS.CH (JIRA) 17 Jan '19

17 Jan '19

1 0

[JIRA] (LOGBACK-1454) StackOverflow error
by QOS.CH (JIRA) 17 Jan '19

17 Jan '19

Mickael Marrache created LOGBACK-1454: ----------------------------------------- Summary: StackOverflow error Key: LOGBACK-1454 URL: https://jira.qos.ch/browse/LOGBACK-1454 Project: logback Issue Type: Bug Affects Versions: 1.2.3 Reporter: Mickael Marrache Assignee: Logback dev list I just encountered the following error: {code:java} 2019-01-17 16:40:00.048 WARN 5845 --- [p1932274274-291] o.e.j.u.thread.strategy.EatWhatYouKill : java.lang.StackOverflowError: null at java.lang.reflect.InvocationTargetException.<init>(InvocationTargetException.java:72) ~[na:1.8.0_171] at sun.reflect.GeneratedMethodAccessor230.invoke(Unknown Source) ~[na:na] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_171] at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_171] at ch.qos.logback.classic.spi.ThrowableProxy.<init>(ThrowableProxy.java:66) ~[logback-classic-1.2.3.jar!/:na] at ch.qos.logback.classic.spi.ThrowableProxy.<init>(ThrowableProxy.java:60) ~[logback-classic-1.2.3.jar!/:na] at ch.qos.logback.classic.spi.ThrowableProxy.<init>(ThrowableProxy.java:60) ~[logback-classic-1.2.3.jar!/:na] at ch.qos.logback.classic.spi.ThrowableProxy.<init>(ThrowableProxy.java:72) ~[logback-classic-1.2.3.jar!/:na] .............. [the constructor appearing hundreds of time in the stack trace] {code} -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-1453) Let us default to ALL when no keys are specified - ResponseHeaderConverter
by QOS.CH (JIRA) 17 Jan '19

17 Jan '19

이경욱 created LOGBACK-1453: ---------------------------- Summary: Let us default to ALL when no keys are specified - ResponseHeaderConverter Key: LOGBACK-1453 URL: https://jira.qos.ch/browse/LOGBACK-1453 Project: logback Issue Type: Improvement Components: logback-access Reporter: 이경욱 Assignee: Logback dev list Priority: Minor RequestHeaderConverter is work, but ResponseHeaderConvert is not. [https://github.com/qos-ch/logback/commit/e5345c42a9404590b0e095a027b536af9e…] [https://github.com/qos-ch/logback/blob/4dd08e68321548cd85251ec389f5a832505e…] -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-1452) stackoverflow cause logback die
by QOS.CH (JIRA) 16 Jan '19

16 Jan '19

xiezhaoodong created LOGBACK-1452: ------------------------------------- Summary: stackoverflow cause logback die Key: LOGBACK-1452 URL: https://jira.qos.ch/browse/LOGBACK-1452 Project: logback Issue Type: Bug Components: logback-core Affects Versions: 1.2.3 Environment: jdk 1.8 Reporter: xiezhaoodong Assignee: Logback dev list Priority: Blocker Attachments: image-2019-01-16-15-37-57-659.png execute arraybloking put method ,if happend stackoverflow error ,may be cause finally block ```lock.unlock()``` can not executed。 all thread print log will be hang forever look this: 937 thread are waiting lock,but owner thread is termernal !image-2019-01-16-15-37-57-659.png! -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-1451) Logger for a file is not getting created with logback version 1.1.7
by QOS.CH (JIRA) 16 Jan '19

16 Jan '19

David Prasad created LOGBACK-1451: ------------------------------------- Summary: Logger for a file is not getting created with logback version 1.1.7 Key: LOGBACK-1451 URL: https://jira.qos.ch/browse/LOGBACK-1451 Project: logback Issue Type: Bug Components: logback-core Affects Versions: 1.1.7 Environment: Production Reporter: David Prasad Assignee: Logback dev list Priority: Blocker Hello All, We have upgraded our logback version from 1.1.3 to 1.1.7, and facing this problem of logs are not getting written to files for specific adapter code, which will create a file name called "adapter.log". We also observed the application logs are written properly to "app.log", but adapter logs are not being written to adapter log file properly. Kindly help us to understand what is causing v1.1.7 to not update the custom adapter log files. Thanks, David -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0