[jira] [Commented] (LOG4J2-2878) How to change the level of the appender

[ https://issues.apache.org/jira/browse/LOG4J2-2878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17147544#comment-17147544 ] Ralph Goers commented on LOG4J2-2878: - Appender's don't have a Level. The AppenderCo

[CI][SUCCESS] log4j/release-2.x#67 back to normal

The build for log4j/release-2.x completed successfully and is back to normal. Build: https://builds.apache.org/job/log4j/job/release-2.x/67/ Logs: https://builds.apache.org/job/log4j/job/release-2.x/67/console Changes: https://builds.apache.org/job/log4j/job/release-2.x/67/changes -- Mr. Jenkins

[CI][FAILURE] log4j/release-2.x#68 has potential issues

There is a build failure in log4j/release-2.x. Build: https://builds.apache.org/job/log4j/job/release-2.x/68/ Logs: https://builds.apache.org/job/log4j/job/release-2.x/68/console Test results: https://builds.apache.org/job/log4j/job/release-2.x/68/testReport/ Changes: https://builds.apache.org/jo

[jira] [Resolved] (LOG4J2-2867) ContextDataProvider will cause concurrent threads blocking at the first logging time

[ https://issues.apache.org/jira/browse/LOG4J2-2867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-2867. - Fix Version/s: 2.14.0 Resolution: Fixed > ContextDataProvider will cause concurrent threa

[jira] [Commented] (LOG4J2-2867) ContextDataProvider will cause concurrent threads blocking at the first logging time

[ https://issues.apache.org/jira/browse/LOG4J2-2867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17147484#comment-17147484 ] Ralph Goers commented on LOG4J2-2867: - I couldn't really make a test that proves thi

[CI][FAILURE] log4j/master#87 has potential issues

There is a build failure in log4j/master. Build: https://builds.apache.org/job/log4j/job/master/87/ Logs: https://builds.apache.org/job/log4j/job/master/87/console Test results: https://builds.apache.org/job/log4j/job/master/87/testReport/ Changes: https://builds.apache.org/job/log4j/job/master/8

[jira] [Commented] (LOG4J2-2867) ContextDataProvider will cause concurrent threads blocking at the first logging time

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

[jira] [Commented] (LOG4J2-2867) ContextDataProvider will cause concurrent threads blocking at the first logging time

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

[jira] [Commented] (LOG4J2-2867) ContextDataProvider will cause concurrent threads blocking at the first logging time

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

[jira] [Commented] (LOG4J2-2867) ContextDataProvider will cause concurrent threads blocking at the first logging time

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

[jira] [Commented] (LOG4J2-2867) ContextDataProvider will cause concurrent threads blocking at the first logging time

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

[CI][FAILURE] log4j/master#86 has potential issues

There is a build failure in log4j/master. Build: https://builds.apache.org/job/log4j/job/master/86/ Logs: https://builds.apache.org/job/log4j/job/master/86/console Test results: https://builds.apache.org/job/log4j/job/master/86/testReport/ Changes: https://builds.apache.org/job/log4j/job/master/8

[GitHub] [logging-log4j2] sullis opened a new pull request #368: enable Dependabot v2

sullis opened a new pull request #368: URL: https://github.com/apache/logging-log4j2/pull/368 https://github.blog/2020-06-01-keep-all-your-packages-up-to-date-with-dependabot/ Dependabot v2 can detect: 1) outdated Maven plugins 2) outdated Java libraries -

[GitHub] [logging-log4j2] turbanoff opened a new pull request #367: avoid initialize 'volatile' fields with default values

turbanoff opened a new pull request #367: URL: https://github.com/apache/logging-log4j2/pull/367 It's known that writing to a `volatile` field has performance impact. It's true even if code initializes field with _default_ value. This PR cleans such redundant initialization and improv

[GitHub] [logging-log4j2] garydgregory commented on pull request #366: Allow clients to set the source manually.

garydgregory commented on pull request #366: URL: https://github.com/apache/logging-log4j2/pull/366#issuecomment-650743832 Yeah, I do not have a use case for that, I just wanted to mention it for completeness sake as well as guidance for contributing: don't break binary compatibility o