[jira] [Commented] (LOG4J2-1103) Failover appender does not fail over

[ https://issues.apache.org/jira/browse/LOG4J2-1103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16838294#comment-16838294 ] ASF subversion and git services commented on LOG4J2-1103: - Commi

Build failed in Jenkins: Log4j 2 3.x #399

See Changes: [rgoers] LOG4J2-2561 - java version detection was not JEP223 compatible -- [...truncated 359.02 KB...] (see https://errorprone.info/bugpattern/StringSplitte

Build failed in Jenkins: Log4j 2 3.x #398

See Changes: [rgoers] JEP223 detection [rgoers] Test for JEP223 detection [rgoers] Test for JEP223 detection [rgoers] Delegate method call to make it testable (without having to use [rgoers] Use existing JDK ve

[jira] [Resolved] (LOG4J2-2561) In log4j-core AbstractStringLayout java version detection is not JEP223 compatible

[ https://issues.apache.org/jira/browse/LOG4J2-2561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-2561. - Resolution: Fixed Fix Version/s: 2.12.0 Patches applied. Please verify and close. > In l

[jira] [Commented] (LOG4J2-2561) In log4j-core AbstractStringLayout java version detection is not JEP223 compatible

[ https://issues.apache.org/jira/browse/LOG4J2-2561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16838279#comment-16838279 ] ASF subversion and git services commented on LOG4J2-2561: - Commi

[jira] [Commented] (LOG4J2-2561) In log4j-core AbstractStringLayout java version detection is not JEP223 compatible

[ https://issues.apache.org/jira/browse/LOG4J2-2561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16838278#comment-16838278 ] ASF subversion and git services commented on LOG4J2-2561: - Commi

Build failed in Jenkins: Log4j 2 3.x #397

See -- [...truncated 359.39 KB...] (see https://errorprone.info/bugpattern/StringSplitter) Did you mean 'group = Iterables.get(Splitter.on(':').split(aGroup), 0);'? [WARNING]

[jira] [Work logged] (LOG4J2-2561) In log4j-core AbstractStringLayout java version detection is not JEP223 compatible

[ https://issues.apache.org/jira/browse/LOG4J2-2561?focusedWorklogId=240875&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-240875 ] ASF GitHub Bot logged work on LOG4J2-2561: -- Author: ASF GitHub Bot

[GitHub] [logging-log4j2] rgoers merged pull request #260: [LOG4J2-2561] JEP223 version detection fix for JDK 9 and up

rgoers merged pull request #260: [LOG4J2-2561] JEP223 version detection fix for JDK 9 and up URL: https://github.com/apache/logging-log4j2/pull/260 This is an automated message from the Apache Git Service. To respond to the

Build failed in Jenkins: Log4j 2 3.x #396

See Changes: [rgoers] LOG4J2-1103 remove used nodes when child is of list type [rgoers] LOG4J2-1103 - FailoverAppender was failing with ERROR appender Failover -- [...trunc

[GitHub] [logging-log4j2] rgoers closed pull request #252: Fixed message length with TLS and Syslog // fixes LOG4J2-2532

rgoers closed pull request #252: Fixed message length with TLS and Syslog // fixes LOG4J2-2532 URL: https://github.com/apache/logging-log4j2/pull/252 This is an automated message from the Apache Git Service. To respond to th

[GitHub] [logging-log4j2] rgoers commented on issue #252: Fixed message length with TLS and Syslog // fixes LOG4J2-2532

rgoers commented on issue #252: Fixed message length with TLS and Syslog // fixes LOG4J2-2532 URL: https://github.com/apache/logging-log4j2/pull/252#issuecomment-491680441 Closing this PR since the TLS support for RFC 5424 Syslog records is covered in https://tools.ietf.org/html/rfc5425 wh

[jira] [Work logged] (LOG4J2-2532) SyslogAppender with RFC5424 and TLS is prepending messagelength

[ https://issues.apache.org/jira/browse/LOG4J2-2532?focusedWorklogId=240873&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-240873 ] ASF GitHub Bot logged work on LOG4J2-2532: -- Author: ASF GitHub Bot

[jira] [Work logged] (LOG4J2-2532) SyslogAppender with RFC5424 and TLS is prepending messagelength

[ https://issues.apache.org/jira/browse/LOG4J2-2532?focusedWorklogId=240874&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-240874 ] ASF GitHub Bot logged work on LOG4J2-2532: -- Author: ASF GitHub Bot

[jira] [Commented] (LOG4J2-1103) Failover appender does not fail over

[ https://issues.apache.org/jira/browse/LOG4J2-1103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16838270#comment-16838270 ] ASF subversion and git services commented on LOG4J2-1103: - Commi

[jira] [Commented] (LOG4J2-1103) Failover appender does not fail over

[ https://issues.apache.org/jira/browse/LOG4J2-1103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16838269#comment-16838269 ] ASF subversion and git services commented on LOG4J2-1103: - Commi

[jira] [Resolved] (LOG4J2-1103) Failover appender does not fail over

[ https://issues.apache.org/jira/browse/LOG4J2-1103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-1103. - Resolution: Fixed Fix Version/s: 2.12.0 Patch applied. Please verify and close. > Failov

[jira] [Commented] (LOG4J2-1103) Failover appender does not fail over

[ https://issues.apache.org/jira/browse/LOG4J2-1103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16838268#comment-16838268 ] ASF subversion and git services commented on LOG4J2-1103: - Commi

[GitHub] [logging-log4j2] rgoers merged pull request #266: LOG4J2-1103 remove used nodes when child is of list type

rgoers merged pull request #266: LOG4J2-1103 remove used nodes when child is of list type URL: https://github.com/apache/logging-log4j2/pull/266 This is an automated message from the Apache Git Service. To respond to the mes

[jira] [Work logged] (LOG4J2-1103) Failover appender does not fail over

[ https://issues.apache.org/jira/browse/LOG4J2-1103?focusedWorklogId=240806&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-240806 ] ASF GitHub Bot logged work on LOG4J2-1103: -- Author: ASF GitHub Bot

[jira] [Commented] (LOG4J2-1103) Failover appender does not fail over

[ https://issues.apache.org/jira/browse/LOG4J2-1103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16838194#comment-16838194 ] ASF subversion and git services commented on LOG4J2-1103: - Commi

[jira] [Commented] (LOG4J2-1852) Plugins lookup by package is not compatible with Spring Boot jar packaging

[ https://issues.apache.org/jira/browse/LOG4J2-1852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16838193#comment-16838193 ] Ralph Goers commented on LOG4J2-1852: - Any further feedback? > Plugins lookup by pa

Jenkins build is back to stable : Log4j 2 3.x #395

See

[jira] [Resolved] (LOG4J2-2602) Same file is overwritten on rollover which causes logs loss

[ https://issues.apache.org/jira/browse/LOG4J2-2602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-2602. - Resolution: Fixed Fix Version/s: 2.12.0 Fixed in release-2.x and master. Please verify an

[jira] [Commented] (LOG4J2-2602) Same file is overwritten on rollover which causes logs loss

[ https://issues.apache.org/jira/browse/LOG4J2-2602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16838183#comment-16838183 ] ASF subversion and git services commented on LOG4J2-2602: - Commi

[jira] [Commented] (LOG4J2-2602) Same file is overwritten on rollover which causes logs loss

[ https://issues.apache.org/jira/browse/LOG4J2-2602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16838182#comment-16838182 ] ASF subversion and git services commented on LOG4J2-2602: - Commi