[jira] [Commented] (LOG4J2-2956) Using log4j-spring-cloud-config-client and DynamicThresholdFilter cause Could not initialize class org.apache.logging.log4j.core.impl.ContextDataFactoryException

2020-11-03 Thread Ralph Goers (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-2956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17225860#comment-17225860 ] Ralph Goers commented on LOG4J2-2956: - Please verify the versions of Log4j included in your

[jira] [Updated] (LOG4J2-2956) Using log4j-spring-cloud-config-client and DynamicThresholdFilter cause Could not initialize class org.apache.logging.log4j.core.impl.ContextDataFactoryException

2020-11-03 Thread Ralph Goers (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-2956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-2956: Description: Assumptions: # Application is a Spring Boot app. # {{It is configured to use 

[CI][UNSTABLE] Logging/log4j/master#173 has test failures

2020-11-03 Thread Mr. Jenkins
BUILD UNSTABLE Build URL https://ci-builds.apache.org/job/Logging/job/log4j/job/master/173/ Project: master Date of build: Tue, 03 Nov 2020 23:54:42 + Build duration: 1 hr 35 min and counting JUnit Tests Name: liquibase.ext.logging.log4j2

[CI][UNSTABLE] Logging/log4j/release-2.x#128 has test failures

2020-11-03 Thread Mr. Jenkins
BUILD UNSTABLE Build URL https://ci-builds.apache.org/job/Logging/job/log4j/job/release-2.x/128/ Project: release-2.x Date of build: Tue, 03 Nov 2020 19:40:05 + Build duration: 1 hr 14 min and counting JUnit Tests Name:

[jira] [Created] (LOG4J2-2956) Using log4j-spring-cloud-config-client and DynamicThresholdFilter cause Could not initialize class org.apache.logging.log4j.core.impl.ContextDataFactoryException

2020-11-03 Thread Jira
Rafał Figas created LOG4J2-2956: --- Summary: Using log4j-spring-cloud-config-client and DynamicThresholdFilter cause Could not initialize class org.apache.logging.log4j.core.impl.ContextDataFactoryException Key: LOG4J2-2956

[CI][UNSTABLE] Logging/log4j/release-2.x#127 has test failures

2020-11-03 Thread Mr. Jenkins
BUILD UNSTABLE Build URL https://ci-builds.apache.org/job/Logging/job/log4j/job/release-2.x/127/ Project: release-2.x Date of build: Tue, 03 Nov 2020 14:51:27 + Build duration: 1 hr 37 min and counting JUnit Tests Name:

[CI][UNSTABLE] Logging/log4j/master#172 has test failures

2020-11-03 Thread Mr. Jenkins
BUILD UNSTABLE Build URL https://ci-builds.apache.org/job/Logging/job/log4j/job/master/172/ Project: master Date of build: Tue, 03 Nov 2020 14:58:20 + Build duration: 1 hr 28 min and counting JUnit Tests Name: liquibase.ext.logging.log4j2

[jira] [Commented] (LOG4J2-2954) Shutdown callbacks registered in LoggerContext.setUpShutdownHook() aren't strongly referenced

2020-11-03 Thread ASF subversion and git services (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-2954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17225476#comment-17225476 ] ASF subversion and git services commented on LOG4J2-2954: - Commit

[jira] [Resolved] (LOG4J2-2954) Shutdown callbacks registered in LoggerContext.setUpShutdownHook() aren't strongly referenced

2020-11-03 Thread Carter Kozak (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-2954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak resolved LOG4J2-2954. -- Fix Version/s: 2.14.0 Resolution: Fixed I've merged the first approach to both

[jira] [Commented] (LOG4J2-2954) Shutdown callbacks registered in LoggerContext.setUpShutdownHook() aren't strongly referenced

2020-11-03 Thread ASF subversion and git services (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-2954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17225474#comment-17225474 ] ASF subversion and git services commented on LOG4J2-2954: - Commit

[jira] [Commented] (LOG4J2-2954) Shutdown callbacks registered in LoggerContext.setUpShutdownHook() aren't strongly referenced

2020-11-03 Thread ASF subversion and git services (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-2954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17225473#comment-17225473 ] ASF subversion and git services commented on LOG4J2-2954: - Commit

[GitHub] [logging-log4j2] carterkozak commented on a change in pull request #434: LOG4J2-2954 Retain strong reference to shutdown callbacks

2020-11-03 Thread GitBox
carterkozak commented on a change in pull request #434: URL: https://github.com/apache/logging-log4j2/pull/434#discussion_r516721169 ## File path: log4j-core/src/main/java/org/apache/logging/log4j/core/util/DefaultShutdownCallbackRegistry.java ## @@ -87,42 +92,41 @@ public

[GitHub] [logging-log4j2] carterkozak commented on a change in pull request #434: LOG4J2-2954 Retain strong reference to shutdown callbacks

2020-11-03 Thread GitBox
carterkozak commented on a change in pull request #434: URL: https://github.com/apache/logging-log4j2/pull/434#discussion_r516721169 ## File path: log4j-core/src/main/java/org/apache/logging/log4j/core/util/DefaultShutdownCallbackRegistry.java ## @@ -87,42 +92,41 @@ public

[GitHub] [logging-log4j2] carterkozak commented on pull request #434: LOG4J2-2954 Retain strong reference to shutdown callbacks

2020-11-03 Thread GitBox
carterkozak commented on pull request #434: URL: https://github.com/apache/logging-log4j2/pull/434#issuecomment-721158932 I think the approach in the first commit is less risky, so I'm going to merge that after I verify tests pass locally to ensure this makes the 2.14.0 release.

[GitHub] [logging-log4php] jvz merged pull request #25: Allow MDC use callable param

2020-11-03 Thread GitBox
jvz merged pull request #25: URL: https://github.com/apache/logging-log4php/pull/25 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to

[GitHub] [logging-log4j2] carterkozak commented on pull request #434: LOG4J2-2954 Retain strong reference to shutdown callbacks

2020-11-03 Thread GitBox
carterkozak commented on pull request #434: URL: https://github.com/apache/logging-log4j2/pull/434#issuecomment-720538814 I think the difference between the first and second commit on this PR is whether or not the JeroMqManager class (and related context classes) should be allowed to be

[GitHub] [logging-log4php] jvz commented on pull request #25: Allow MDC use callable param

2020-11-03 Thread GitBox
jvz commented on pull request #25: URL: https://github.com/apache/logging-log4php/pull/25#issuecomment-720568872 Thanks for the PR! This is an automated message from the Apache Git Service. To respond to the message, please

[GitHub] [logging-log4php] Falseclock commented on pull request #25: Allow MDC use callable param

2020-11-03 Thread GitBox
Falseclock commented on pull request #25: URL: https://github.com/apache/logging-log4php/pull/25#issuecomment-720283468 @jvz Done. Unfortunately had to add PHP version check cause composer's compatibility is >= 5.2.7 while Closures available since 5.3.0

[GitHub] [logging-log4j2] wuqian0808 commented on pull request #428: Avoid kafka thread leak - LOG4J2-2916

2020-11-03 Thread GitBox
wuqian0808 commented on pull request #428: URL: https://github.com/apache/logging-log4j2/pull/428#issuecomment-720878961 @jvz kindly help to advise This is an automated message from the Apache Git Service. To respond to the