[jira] [Resolved] (LOGCXX-504) vcpkg build integration

[ https://issues.apache.org/jira/browse/LOGCXX-504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Middleton resolved LOGCXX-504. - Resolution: Fixed > vcpkg build integration > > >

[jira] [Comment Edited] (LOGCXX-504) vcpkg build integration

[ https://issues.apache.org/jira/browse/LOGCXX-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17231060#comment-17231060 ] Dr Stephen L S Webb edited comment on LOGCXX-504 at 11/13/20, 12:47 AM: ---

[jira] [Commented] (LOGCXX-504) vcpkg build integration

[ https://issues.apache.org/jira/browse/LOGCXX-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17231060#comment-17231060 ] Dr Stephen L S Webb commented on LOGCXX-504: Vcpkg has been switch to version

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

BUILD UNSTABLE Build URL https://ci-builds.apache.org/job/Logging/job/log4j/job/master/180/ Project: master Date of build: Thu, 12 Nov 2020 22:10:26 + Build duration: 1 hr 25 min and counting JUnit Tests Name: liquibase.ext.logging.log4j2 Failed:

[jira] [Closed] (LOG4J2-2916) If loggercontext got reconfigured and kafka appender got recreated, the previous producer can not be closed, which cause thread leak

[ https://issues.apache.org/jira/browse/LOG4J2-2916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Volkan Yazici closed LOG4J2-2916. - Resolution: Fixed > If loggercontext got reconfigured and kafka appender got recreated, the > p

[jira] [Assigned] (LOG4J2-2916) If loggercontext got reconfigured and kafka appender got recreated, the previous producer can not be closed, which cause thread leak

[ https://issues.apache.org/jira/browse/LOG4J2-2916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Volkan Yazici reassigned LOG4J2-2916: - Assignee: Volkan Yazici > If loggercontext got reconfigured and kafka appender got recr

[jira] [Commented] (LOG4J2-2916) If loggercontext got reconfigured and kafka appender got recreated, the previous producer can not be closed, which cause thread leak

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

[jira] [Commented] (LOG4J2-2916) If loggercontext got reconfigured and kafka appender got recreated, the previous producer can not be closed, which cause thread leak

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

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

BUILD SUCCESS Build URL https://ci-builds.apache.org/job/Logging/job/log4j/job/release-2.x/149/ Project: release-2.x Date of build: Thu, 12 Nov 2020 18:59:14 + Build duration: 1 hr 6 min and counting JUnit Tests Name: liquibase.ext.logging.log4j2

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

BUILD UNSTABLE Build URL https://ci-builds.apache.org/job/Logging/job/log4j/job/master/179/ Project: master Date of build: Thu, 12 Nov 2020 16:48:39 + Build duration: 1 hr 24 min and counting JUnit Tests Name: liquibase.ext.logging.log4j2 Failed:

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

BUILD UNSTABLE Build URL https://ci-builds.apache.org/job/Logging/job/log4j/job/release-2.x/148/ Project: release-2.x Date of build: Thu, 12 Nov 2020 16:33:32 + Build duration: 1 hr 11 min and counting JUnit Tests Name: liquibase.ext.logging.log4

[GitHub] [logging-log4j2] vy commented on pull request #428: LOG4J2-2916 Avoid redundant Kafka producer instantiation causing thread leaks.

vy commented on pull request #428: URL: https://github.com/apache/logging-log4j2/pull/428#issuecomment-726199650 Nevermind, applied your changes manually. Will backport it to 2.x too. Thanks so much! This is an automated mes

[GitHub] [logging-log4j2] vy closed pull request #428: LOG4J2-2916 Avoid redundant Kafka producer instantiation causing thread leaks.

vy closed pull request #428: URL: https://github.com/apache/logging-log4j2/pull/428 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

[jira] [Commented] (LOG4J2-2916) If loggercontext got reconfigured and kafka appender got recreated, the previous producer can not be closed, which cause thread leak

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

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

BUILD UNSTABLE Build URL https://ci-builds.apache.org/job/Logging/job/log4j/job/master/178/ Project: master Date of build: Thu, 12 Nov 2020 15:26:48 + Build duration: 1 hr 20 min and counting JUnit Tests Name: liquibase.ext.logging.log4j2 Failed:

[GitHub] [logging-log4j2] ilam-natarajan commented on pull request #437: LOG4J2-2025 jul-log4j bridgehandler

ilam-natarajan commented on pull request #437: URL: https://github.com/apache/logging-log4j2/pull/437#issuecomment-726195646 thanks, @jvz thats done now. This is an automated message from the Apache Git Service. To respond t

[GitHub] [logging-log4j2] jvz commented on pull request #437: LOG4J2-2025 jul-log4j bridgehandler

jvz commented on pull request #437: URL: https://github.com/apache/logging-log4j2/pull/437#issuecomment-726163770 If you add an entry to `src/changes/changes.xml`, I think that's the only remaining thing. Otherwise, a volunteer from the project will merge this when they get some time to do

[jira] [Commented] (LOG4J2-2850) LocalizedMessageFactory creates new message with baseName as messagePattern

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

[jira] [Commented] (LOG4J2-2850) LocalizedMessageFactory creates new message with baseName as messagePattern

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

[jira] [Commented] (LOG4J2-2850) LocalizedMessageFactory creates new message with baseName as messagePattern

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

[jira] [Commented] (LOG4J2-2850) LocalizedMessageFactory creates new message with baseName as messagePattern

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

[jira] [Deleted] (LOG4J2-2959) Cenforce 100

[ https://issues.apache.org/jira/browse/LOG4J2-2959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers deleted LOG4J2-2959: > Cenforce 100 > > > Key: LOG4J2-2959 > URL: https://iss

[GitHub] [logging-log4j2] vy merged pull request #436: LOG4J2-2850 Fix ctor used in LocalizedMessageFactory#newMessage().

vy merged pull request #436: URL: https://github.com/apache/logging-log4j2/pull/436 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] vy commented on a change in pull request #428: LOG4J2-2916 Avoid redundant Kafka producer instantiation causing thread leaks.

vy commented on a change in pull request #428: URL: https://github.com/apache/logging-log4j2/pull/428#discussion_r522189283 ## File path: log4j-kafka/src/test/java/org/apache/logging/log4j/kafka/appender/KafkaThreadTest.java ## @@ -0,0 +1,33 @@ +package org.apache.logging.log4

[jira] [Deleted] (LOG4J2-2960) Popular medicines for Erectile Dysfunction

[ https://issues.apache.org/jira/browse/LOG4J2-2960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory deleted LOG4J2-2960: > Popular medicines for Erectile Dysfunction > -- > >

[jira] [Closed] (LOG4J2-2959) Cenforce 100

[ https://issues.apache.org/jira/browse/LOG4J2-2959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma closed LOG4J2-2959. --- Resolution: Invalid Nice touch on the "ready to commit" label. Thanks but no thanks. > Cenforce 10

[jira] [Closed] (LOG4J2-2960) Popular medicines for Erectile Dysfunction

[ https://issues.apache.org/jira/browse/LOG4J2-2960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma closed LOG4J2-2960. --- Resolution: Invalid I am very tempted to make a PR joke here but I will abstain. > Popular medicine

[GitHub] [logging-log4j2] ilam-natarajan commented on pull request #437: LOG4J2-2025 jul-log4j bridgehandler

ilam-natarajan commented on pull request #437: URL: https://github.com/apache/logging-log4j2/pull/437#issuecomment-726029598 @rgoers thanks for the review. should I do anything to get this merged? sorry I am not very familiar with the process as this is my first time

[jira] [Created] (LOG4J2-2960) Popular medicines for Erectile Dysfunction

martin beck created LOG4J2-2960: --- Summary: Popular medicines for Erectile Dysfunction Key: LOG4J2-2960 URL: https://issues.apache.org/jira/browse/LOG4J2-2960 Project: Log4j 2 Issue Type: Task

[jira] [Created] (LOG4J2-2959) Cenforce 100

martin beck created LOG4J2-2959: --- Summary: Cenforce 100 Key: LOG4J2-2959 URL: https://issues.apache.org/jira/browse/LOG4J2-2959 Project: Log4j 2 Issue Type: Bug Components: Appenders,