[jira] [Commented] (LOG4J2-3272) Enable Git and GitHub for log4j 1.2 repository

[ https://issues.apache.org/jira/browse/LOG4J2-3272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17464344#comment-17464344 ] Vladimir Sitnikov commented on LOG4J2-3272: --- Could you please clarify why did

[jira] [Commented] (LOG4J2-3272) Enable Git and GitHub for log4j 1.2 repository

[ https://issues.apache.org/jira/browse/LOG4J2-3272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17464340#comment-17464340 ] Remko Popma commented on LOG4J2-3272: - I believe it’s available now, sorry for the w

[jira] [Updated] (LOG4J2-3278) SpringLookup log4j2 2.17.0 version Invalidation

[ https://issues.apache.org/jira/browse/LOG4J2-3278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ZhangZhichun updated LOG4J2-3278: - Attachment: image-2021-12-23-15-04-36-171.png > SpringLookup log4j2 2.17.0 version Invalidation

[jira] [Updated] (LOG4J2-3278) SpringLookup log4j2 2.17.0 version Invalidation

[ https://issues.apache.org/jira/browse/LOG4J2-3278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ZhangZhichun updated LOG4J2-3278: - Description: SpringLookup 2.16.0 is ok,Invalid after update to 2.17.0.   ${spring:spring.applic

[jira] [Updated] (LOG4J2-3278) SpringLookup log4j2 2.17.0 version Invalidation

[ https://issues.apache.org/jira/browse/LOG4J2-3278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ZhangZhichun updated LOG4J2-3278: - Attachment: (was: image-2021-12-23-14-20-21-891.png) > SpringLookup log4j2 2.17.0 version I

[jira] [Updated] (LOG4J2-3278) SpringLookup log4j2 2.17.0 version Invalidation

[ https://issues.apache.org/jira/browse/LOG4J2-3278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ZhangZhichun updated LOG4J2-3278: - Description: SpringLookup 2.16.0 is ok,Invalid after update to 2.17.0.   ${spring:spring.applic

[jira] [Created] (LOG4J2-3278) SpringLookup log4j2 2.17.0 version Invalidation

ZhangZhichun created LOG4J2-3278: Summary: SpringLookup log4j2 2.17.0 version Invalidation Key: LOG4J2-3278 URL: https://issues.apache.org/jira/browse/LOG4J2-3278 Project: Log4j 2 Issue Type

[jira] [Commented] (LOG4J2-3272) Enable Git and GitHub for log4j 1.2 repository

[ https://issues.apache.org/jira/browse/LOG4J2-3272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17464316#comment-17464316 ] Vladimir Sitnikov commented on LOG4J2-3272: --- I see [~rpopma] says {quote} Mig

[jira] [Commented] (LOG4J2-444) Log4j2 eclipselink integration

[ https://issues.apache.org/jira/browse/LOG4J2-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17464292#comment-17464292 ] Ralph Goers commented on LOG4J2-444: I am afraid you would have to ask the EclipseLin

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

BUILD UNSTABLE Build URL https://ci-builds.apache.org/job/Logging/job/log4j/job/release-2.x/524/ Project: release-2.x Date of build: Thu, 23 Dec 2021 04:01:40 + Build duration: 1 hr 1 min and counting JUnit Tests Name: (root) Failed: 0 test(s), P

[jira] [Commented] (LOG4J2-3269) Method To Find Log4j Version on Windows Servers

[ https://issues.apache.org/jira/browse/LOG4J2-3269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17464289#comment-17464289 ] Richard Gomez commented on LOG4J2-3269: --- [~Ciaran] Something like [https://github.

[jira] [Commented] (LOG4J2-444) Log4j2 eclipselink integration

[ https://issues.apache.org/jira/browse/LOG4J2-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17464288#comment-17464288 ] rinilnath commented on LOG4J2-444: -- Thanks Ralph, then what is the answer to the OP's qu

[jira] [Commented] (LOG4J2-2819) Add support for specifying an SSL configuration for SmtpAppender

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

[jira] [Commented] (LOG4J2-2819) Add support for specifying an SSL configuration for SmtpAppender

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

[jira] [Commented] (LOG4J2-2819) Add support for specifying an SSL configuration for SmtpAppender

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

[jira] [Commented] (LOG4J2-2819) Add support for specifying an SSL configuration for SmtpAppender

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

[jira] [Commented] (LOG4J2-2819) Add support for specifying an SSL configuration for SmtpAppender

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

[jira] [Closed] (LOG4J2-3276) MD5 Hash links for 2.3.1 are all broken

[ https://issues.apache.org/jira/browse/LOG4J2-3276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma closed LOG4J2-3276. --- The updated site is live. Thank you for raising this, [~sebb]! > MD5 Hash links for 2.3.1 are all brok

[jira] [Closed] (LOG4J2-3275) Broken download page links and incorrect titles

[ https://issues.apache.org/jira/browse/LOG4J2-3275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma closed LOG4J2-3275. --- The updated site is live. Thank you for raising this, [~sebb]! > Broken download page links and incorr

[jira] [Closed] (LOG4J2-3277) Update previous releases in left-side nav menu

[ https://issues.apache.org/jira/browse/LOG4J2-3277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma closed LOG4J2-3277. --- Resolution: Fixed > Update previous releases in left-side nav menu > ---

[jira] [Updated] (LOG4J2-3277) Update previous releases in left-side nav menu

[ https://issues.apache.org/jira/browse/LOG4J2-3277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-3277: Fix Version/s: 2.17.0 > Update previous releases in left-side nav menu > -

[jira] [Closed] (LOG4J2-3277) Update previous releases in left-side nav menu

[ https://issues.apache.org/jira/browse/LOG4J2-3277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma closed LOG4J2-3277. --- > Update previous releases in left-side nav menu > -- > >

[jira] [Reopened] (LOG4J2-3277) Update previous releases in left-side nav menu

[ https://issues.apache.org/jira/browse/LOG4J2-3277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma reopened LOG4J2-3277: - > Update previous releases in left-side nav menu > -- >

[jira] [Resolved] (LOG4J2-3277) Update previous releases in left-side nav menu

[ https://issues.apache.org/jira/browse/LOG4J2-3277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-3277. - Resolution: Fixed Fixed and pushed to live site. > Update previous releases in left-side nav me

[jira] [Commented] (LOG4J2-3276) MD5 Hash links for 2.3.1 are all broken

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

[jira] [Commented] (LOG4J2-3277) Update previous releases in left-side nav menu

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

[jira] [Commented] (LOG4J2-3275) Broken download page links and incorrect titles

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

[jira] [Commented] (LOG4J2-3277) Update previous releases in left-side nav menu

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

[jira] [Commented] (LOG4J2-3277) Update previous releases in left-side nav menu

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

[GitHub] [logging-log4j2] garydgregory commented on pull request #649: Remove requirement of JndiLookup class to exist

garydgregory commented on pull request #649: URL: https://github.com/apache/logging-log4j2/pull/649#issuecomment-117158 > We were in such a hurry to get patches out that nothing was brought back to the master (3.0) branch. I am actually in the process right now of moving the JNDI piece

[GitHub] [logging-log4cxx] rm5248 edited a comment on pull request #87: Imported and slightly cleaned up throughput tests

rm5248 edited a comment on pull request #87: URL: https://github.com/apache/logging-log4cxx/pull/87#issuecomment-114049 > 1. Multi threaded logging to a single logger probably should be part of the unit tests rather than a throughput test. The mutex in log4cxx::Hierarchy (or AppenderA

[GitHub] [logging-log4cxx] rm5248 commented on pull request #87: Imported and slightly cleaned up throughput tests

rm5248 commented on pull request #87: URL: https://github.com/apache/logging-log4cxx/pull/87#issuecomment-114049 > 1. Multi threaded logging to a single logger probably should be part of the unit tests rather than a throughput test. The mutex in log4cxx::Hierarchy (or AppenderAttac

[jira] [Commented] (LOG4J2-3277) Update previous releases in left-side nav menu

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

[jira] [Created] (LOG4J2-3277) Update previous releases in left-side nav menu

Remko Popma created LOG4J2-3277: --- Summary: Update previous releases in left-side nav menu Key: LOG4J2-3277 URL: https://issues.apache.org/jira/browse/LOG4J2-3277 Project: Log4j 2 Issue Type: Do

[jira] [Work started] (LOG4J2-3277) Update previous releases in left-side nav menu

[jira] [Resolved] (LOG4J2-3275) Broken download page links and incorrect titles

[ https://issues.apache.org/jira/browse/LOG4J2-3275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-3275. - Resolution: Fixed Fixed and pushed to [staging|https://logging.staged.apache.org/log4j/log4j-2.

[jira] [Updated] (LOG4J2-3275) Broken download page links and incorrect titles

[ https://issues.apache.org/jira/browse/LOG4J2-3275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-3275: Affects Version/s: 2.12.3 > Broken download page links and incorrect titles >

[jira] [Updated] (LOG4J2-3275) Broken download page links and incorrect titles

[ https://issues.apache.org/jira/browse/LOG4J2-3275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-3275: Fix Version/s: 2.12.3 > Broken download page links and incorrect titles >

[jira] [Commented] (LOG4J2-3275) Broken download page links and incorrect titles

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

[jira] [Commented] (LOG4J2-3275) Broken download page links and incorrect titles

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

[jira] [Commented] (LOG4J2-3275) Broken download page links and incorrect titles

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

[jira] [Commented] (LOG4J2-3275) Broken download page links and incorrect titles

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

[GitHub] [logging-log4cxx] rm5248 commented on a change in pull request #87: Imported and slightly cleaned up throughput tests

rm5248 commented on a change in pull request #87: URL: https://github.com/apache/logging-log4cxx/pull/87#discussion_r774285680 ## File path: src/test/cpp/throughput/CMakeLists.txt ## @@ -0,0 +1,40 @@ +option(BUILD_THROUGHPUT_TESTS "Build throughput tests" OFF) + +if( NOT BUILD

[jira] [Resolved] (LOG4J2-3276) MD5 Hash links for 2.3.1 are all broken

[ https://issues.apache.org/jira/browse/LOG4J2-3276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-3276. - Resolution: Fixed > MD5 Hash links for 2.3.1 are all broken > --

[jira] [Work stopped] (LOG4J2-3276) MD5 Hash links for 2.3.1 are all broken

[ https://issues.apache.org/jira/browse/LOG4J2-3276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on LOG4J2-3276 stopped by Remko Popma. --- > MD5 Hash links for 2.3.1 are all broken > -

[jira] [Commented] (LOG4J2-3276) MD5 Hash links for 2.3.1 are all broken

[ https://issues.apache.org/jira/browse/LOG4J2-3276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17464227#comment-17464227 ] Remko Popma commented on LOG4J2-3276: - Fixed and pushed to [staging|https://logging

[jira] [Updated] (LOG4J2-3276) MD5 Hash links for 2.3.1 are all broken

[ https://issues.apache.org/jira/browse/LOG4J2-3276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-3276: Fix Version/s: 2.3.1 > MD5 Hash links for 2.3.1 are all broken > -

[jira] [Updated] (LOG4J2-3276) MD5 Hash links for 2.3.1 are all broken

[ https://issues.apache.org/jira/browse/LOG4J2-3276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-3276: Affects Version/s: 2.3.1 > MD5 Hash links for 2.3.1 are all broken > -

[jira] [Commented] (LOG4J2-3276) MD5 Hash links for 2.3.1 are all broken

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

[jira] [Commented] (LOG4J2-3276) MD5 Hash links for 2.3.1 are all broken

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

[jira] [Commented] (LOG4J2-3276) MD5 Hash links for 2.3.1 are all broken

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

[GitHub] [logging-log4j2] quaff commented on pull request #646: LOG4J2-3264: Fix MapLookup to lookup MapMessage before DefaultMap

quaff commented on pull request #646: URL: https://github.com/apache/logging-log4j2/pull/646#issuecomment-71506 > @quaff I've resolved that issue, would you mind rebasing to `release-2.x`? I think you'll need to update one of the tests in `InterpolatorTest` as well. Thanks! @car

[GitHub] [logging-log4cxx] swebb2066 edited a comment on pull request #87: Imported and slightly cleaned up throughput tests

swebb2066 edited a comment on pull request #87: URL: https://github.com/apache/logging-log4cxx/pull/87#issuecomment-33135 Hi Robert, This should do the initial job just fine. However, a couple of things occur to me in hindsight. 1. Multi threaded logging to a single

[jira] [Work started] (LOG4J2-3276) MD5 Hash links for 2.3.1 are all broken

[ https://issues.apache.org/jira/browse/LOG4J2-3276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on LOG4J2-3276 started by Remko Popma. --- > MD5 Hash links for 2.3.1 are all broken > -

[jira] [Assigned] (LOG4J2-3276) MD5 Hash links for 2.3.1 are all broken

[ https://issues.apache.org/jira/browse/LOG4J2-3276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma reassigned LOG4J2-3276: --- Assignee: Remko Popma > MD5 Hash links for 2.3.1 are all broken > -

[jira] [Assigned] (LOG4J2-3275) Broken download page links and incorrect titles

[ https://issues.apache.org/jira/browse/LOG4J2-3275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma reassigned LOG4J2-3275: --- Assignee: Remko Popma > Broken download page links and incorrect titles > -

[jira] [Work started] (LOG4J2-3275) Broken download page links and incorrect titles

[ https://issues.apache.org/jira/browse/LOG4J2-3275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on LOG4J2-3275 started by Remko Popma. --- > Broken download page links and incorrect titles > -

[GitHub] [logging-log4cxx] swebb2066 commented on a change in pull request #87: Imported and slightly cleaned up throughput tests

swebb2066 commented on a change in pull request #87: URL: https://github.com/apache/logging-log4cxx/pull/87#discussion_r77423 ## File path: src/test/cpp/throughput/CMakeLists.txt ## @@ -0,0 +1,40 @@ +option(BUILD_THROUGHPUT_TESTS "Build throughput tests" OFF) + +if( NOT BU

[jira] [Commented] (LOG4J2-444) Log4j2 eclipselink integration

[ https://issues.apache.org/jira/browse/LOG4J2-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17464165#comment-17464165 ] Ralph Goers commented on LOG4J2-444: It is marked resolved because Eclipselink provid

[jira] [Comment Edited] (LOG4J2-3251) Weblookup ${web:rootDir} is not working if old loggercontext is removed and tried to initialize loggerContext using Configurator.initialize

[ https://issues.apache.org/jira/browse/LOG4J2-3251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17464160#comment-17464160 ] Ralph Goers edited comment on LOG4J2-3251 at 12/22/21, 11:20 PM: -

[jira] [Updated] (LOG4J2-3251) Weblookup ${web:rootDir} is not working if old loggercontext is removed and tried to initialize loggerContext using Configurator.initialize

[ https://issues.apache.org/jira/browse/LOG4J2-3251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-3251: Issue Type: Wish (was: Bug) > Weblookup ${web:rootDir} is not working if old loggercontext is rem

[jira] [Resolved] (LOG4J2-3251) Weblookup ${web:rootDir} is not working if old loggercontext is removed and tried to initialize loggerContext using Configurator.initialize

[ https://issues.apache.org/jira/browse/LOG4J2-3251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-3251. - Resolution: Won't Do > Weblookup ${web:rootDir} is not working if old loggercontext is removed a

[jira] [Commented] (LOG4J2-3251) Weblookup ${web:rootDir} is not working if old loggercontext is removed and tried to initialize loggerContext using Configurator.initialize

[ https://issues.apache.org/jira/browse/LOG4J2-3251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17464160#comment-17464160 ] Ralph Goers commented on LOG4J2-3251: - What you are doing sounds invalid. LoggerCont

[jira] [Commented] (LOG4J2-3276) MD5 Hash links for 2.3.1 are all broken

[ https://issues.apache.org/jira/browse/LOG4J2-3276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17464158#comment-17464158 ] Sebb commented on LOG4J2-3276: -- Furthermore, the .zip.asc links are both broken - typo /log

[jira] [Resolved] (LOG4J2-3273) Upgrade to Log4j 2.17

[ https://issues.apache.org/jira/browse/LOG4J2-3273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-3273. - Resolution: Information Provided > Upgrade to Log4j 2.17 > - > >

[jira] [Commented] (LOG4J2-3273) Upgrade to Log4j 2.17

[ https://issues.apache.org/jira/browse/LOG4J2-3273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17464157#comment-17464157 ] Ralph Goers commented on LOG4J2-3273: - There is no way we can advise you on this. We

[GitHub] [logging-log4cxx] swebb2066 commented on pull request #87: Imported and slightly cleaned up throughput tests

swebb2066 commented on pull request #87: URL: https://github.com/apache/logging-log4cxx/pull/87#issuecomment-33135 Hi Robert, This should do the initial job just fine. However, a couple of things occur to me in hindsight. 1. Multi threaded logging to a single logger

[jira] [Comment Edited] (LOG4J2-3274) Log4j2 deadlock version 2.16

[ https://issues.apache.org/jira/browse/LOG4J2-3274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17464152#comment-17464152 ] Ralph Goers edited comment on LOG4J2-3274 at 12/22/21, 11:09 PM: -

[jira] [Resolved] (LOG4J2-3274) Log4j2 deadlock version 2.16

[ https://issues.apache.org/jira/browse/LOG4J2-3274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-3274. - Resolution: Not A Bug Resolving as not a bug since this was caused by a bad configuration. > Lo

[jira] [Commented] (LOG4J2-3274) Log4j2 deadlock version 2.16

[ https://issues.apache.org/jira/browse/LOG4J2-3274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17464150#comment-17464150 ] Ralph Goers commented on LOG4J2-3274: - This is quite an interesting thread dump. It

[jira] [Created] (LOG4J2-3276) MD5 Hash links for 2.3.1 are all broken

Sebb created LOG4J2-3276: Summary: MD5 Hash links for 2.3.1 are all broken Key: LOG4J2-3276 URL: https://issues.apache.org/jira/browse/LOG4J2-3276 Project: Log4j 2 Issue Type: Bug Reporte

[jira] [Created] (LOG4J2-3275) Broken download page links and incorrect titles

Sebb created LOG4J2-3275: Summary: Broken download page links and incorrect titles Key: LOG4J2-3275 URL: https://issues.apache.org/jira/browse/LOG4J2-3275 Project: Log4j 2 Issue Type: Bug

[GitHub] [logging-log4j2] riven8192 closed pull request #649: Remove requirement of JndiLookup class to exist

riven8192 closed pull request #649: URL: https://github.com/apache/logging-log4j2/pull/649 -- 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 the specific comment. To unsubscribe, e-mail: notific

[GitHub] [logging-log4j2] carterkozak commented on pull request #646: LOG4J2-3264: Fix MapLookup to lookup MapMessage before DefaultMap

carterkozak commented on pull request #646: URL: https://github.com/apache/logging-log4j2/pull/646#issuecomment-08178 @quaff I've resolved that issue, would you mind rebasing to `release-2.x`? I think you'll need to update one of the tests in `InterpolatorTest` as well. Thanks! -- T

[GitHub] [logging-log4j2] riven8192 commented on pull request #649: Remove requirement of JndiLookup class to exist

riven8192 commented on pull request #649: URL: https://github.com/apache/logging-log4j2/pull/649#issuecomment-08082 Thanks @carterkozak - that indeed ensures security in the case I described. -- This is an automated message from the Apache Git Service. To respond to the message, pleas

[GitHub] [logging-log4j2] carterkozak commented on pull request #649: Remove requirement of JndiLookup class to exist

carterkozak commented on pull request #649: URL: https://github.com/apache/logging-log4j2/pull/649#issuecomment-00777 @riven8192 the repackaging plugins I'm aware of also match string constants and rewrite those when they match fully qualified class names. I believe that would work cor

[GitHub] [logging-log4j2] riven8192 edited a comment on pull request #649: Remove requirement of JndiLookup class to exist

riven8192 edited a comment on pull request #649: URL: https://github.com/apache/logging-log4j2/pull/649#issuecomment-999896230 Thanks for your reply. With repackaging I didn't mean a refactor on the log4j side, but for example a 3rd party library like a google client-api, that renames:

[GitHub] [logging-log4j2] riven8192 edited a comment on pull request #649: Remove requirement of JndiLookup class to exist

riven8192 edited a comment on pull request #649: URL: https://github.com/apache/logging-log4j2/pull/649#issuecomment-999896230 Thanks for your reply. With repackaging I didn't mean a refactor on the log4j side, but for example a 3rd party library like a google client-api, that renames:

[GitHub] [logging-log4j2] riven8192 commented on pull request #649: Remove requirement of JndiLookup class to exist

riven8192 commented on pull request #649: URL: https://github.com/apache/logging-log4j2/pull/649#issuecomment-999896230 Thanks for your reply. With repackaging I didn't mean a refactor on the log4j side, but for example a 3rd party library like a google client-api, that renames: `org.ap

[jira] [Commented] (LOG4J2-3270) Interpolator defaults should use only configuration properties

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

[GitHub] [logging-log4j2] rgoers edited a comment on pull request #649: Remove requirement of JndiLookup class to exist

rgoers edited a comment on pull request #649: URL: https://github.com/apache/logging-log4j2/pull/649#issuecomment-999887585 We were in such a hurry to get patches out that nothing was brought back to the master (3.0) branch. I am actually in the process right now of moving the JNDI pieces

[GitHub] [logging-log4j2] rgoers commented on pull request #649: Remove requirement of JndiLookup class to exist

rgoers commented on pull request #649: URL: https://github.com/apache/logging-log4j2/pull/649#issuecomment-999887585 We were in such a hurry to get patches out that nothing was brought back to the master (3.0) branch. I am actually in the process right now of moving the JNDI pieces to thei

[GitHub] [logging-log4j2] riven8192 commented on pull request #649: Remove requirement of JndiLookup class to exist

riven8192 commented on pull request #649: URL: https://github.com/apache/logging-log4j2/pull/649#issuecomment-999883312 Thanks for the information regarding the branches @garydgregory. I will not (yet) make PRs for those branches, as it seems it'd be preferable to agree on the underl

[jira] [Closed] (LOG4J2-3270) Interpolator defaults should use only configuration properties

[ https://issues.apache.org/jira/browse/LOG4J2-3270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak closed LOG4J2-3270. > Interpolator defaults should use only configuration properties > ---

[jira] [Resolved] (LOG4J2-3270) Interpolator defaults should use only configuration properties

[ https://issues.apache.org/jira/browse/LOG4J2-3270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak resolved LOG4J2-3270. -- Resolution: Fixed > Interpolator defaults should use only configuration properties > -

[jira] [Updated] (LOG4J2-3270) Interpolator defaults should use only configuration properties

[ https://issues.apache.org/jira/browse/LOG4J2-3270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak updated LOG4J2-3270: - Fix Version/s: 2.17.1 > Interpolator defaults should use only configuration properties > ---

[GitHub] [logging-log4j2] carterkozak merged pull request #647: LOG4J2-3270 Provide separation between MapMessage and properties lookups

carterkozak merged pull request #647: URL: https://github.com/apache/logging-log4j2/pull/647 -- 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 the specific comment. To unsubscribe, e-mail: notif

[GitHub] [logging-log4j2] carterkozak merged pull request #650: JNDI enablement properties are loaded at most once

carterkozak merged pull request #650: URL: https://github.com/apache/logging-log4j2/pull/650 -- 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 the specific comment. To unsubscribe, e-mail: notif

[GitHub] [logging-log4j2] garydgregory commented on pull request #650: JNDI enablement properties are loaded at most once

garydgregory commented on pull request #650: URL: https://github.com/apache/logging-log4j2/pull/650#issuecomment-999871597 > Local build succeeded :-) Ka-pow! :-) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use

[GitHub] [logging-log4j2] carterkozak commented on pull request #650: JNDI enablement properties are loaded at most once

carterkozak commented on pull request #650: URL: https://github.com/apache/logging-log4j2/pull/650#issuecomment-999870595 Local build succeeded :-) -- 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 t

[GitHub] [logging-log4j2] garydgregory commented on pull request #650: JNDI enablement properties are loaded at most once

garydgregory commented on pull request #650: URL: https://github.com/apache/logging-log4j2/pull/650#issuecomment-999870082 > > How is that going to work for tests that set and clear properties? You don't want to set a property "forever"... > > Good question. I'm letting CI run our te

[GitHub] [logging-log4j2] carterkozak commented on pull request #650: JNDI enablement properties are loaded at most once

carterkozak commented on pull request #650: URL: https://github.com/apache/logging-log4j2/pull/650#issuecomment-999860302 > How is that going to work for tests that set and clear properties? You don't want to set a property "forever"... Good question. I'm letting CI run our tests to

[GitHub] [logging-log4j2] garydgregory edited a comment on pull request #650: JNDI enablement properties are loaded at most once

garydgregory edited a comment on pull request #650: URL: https://github.com/apache/logging-log4j2/pull/650#issuecomment-999846809 How is that going to work for tests that set and clear properties? You don't want to set a property "forever"... Gary On Wed, Dec 22, 2021, 15:2

[GitHub] [logging-log4j2] garydgregory commented on pull request #650: JNDI enablement properties are loaded at most once

garydgregory commented on pull request #650: URL: https://github.com/apache/logging-log4j2/pull/650#issuecomment-999846809 How is that going to work for tests that set and clear properties? You don't want to set a property "forever"... Gaty On Wed, Dec 22, 2021, 15:25 Carter

[GitHub] [logging-log4j2] carterkozak opened a new pull request #650: JNDI enablement properties are loaded at most once

carterkozak opened a new pull request #650: URL: https://github.com/apache/logging-log4j2/pull/650 Rather than checking properties after each invocation, jndi properties are all read into static final boolean fields when the JndiManager class is initialized, this way properties cannot

[jira] [Commented] (LOG4J2-3274) Log4j2 deadlock version 2.16

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

[GitHub] [logging-log4j2] garydgregory commented on pull request #649: Remove requirement of JndiLookup class to exist

garydgregory commented on pull request #649: URL: https://github.com/apache/logging-log4j2/pull/649#issuecomment-999792045 You might not have noticed the master branch is labeled 3.0.0-SNAPSHOT. The branch for 2.x is called release-2.x. -- This is an automated message from the Apache Git

[GitHub] [logging-log4j2] garydgregory commented on pull request #649: Remove requirement of JndiLookup class to exist

garydgregory commented on pull request #649: URL: https://github.com/apache/logging-log4j2/pull/649#issuecomment-999789007 Now that we have provides releases for all Java versions that ever saw a Log4j 2 release, I don't think our code should account for mangled jar files. - Java 8 -> 2.

[GitHub] [logging-log4j2] riven8192 commented on pull request #649: Remove requirement of JndiLookup class to exist

riven8192 commented on pull request #649: URL: https://github.com/apache/logging-log4j2/pull/649#issuecomment-999785941 @garydgregory The 2.17.0 patch does not factor in a safeguard for repackaged dependencies (where the java package-names are changed) -- This is an automated message fro

[GitHub] [logging-log4j2] garydgregory commented on pull request #649: Remove requirement of JndiLookup class to exist

garydgregory commented on pull request #649: URL: https://github.com/apache/logging-log4j2/pull/649#issuecomment-999784891 This has already been handled in 2.17.0. Note that PRs should be created against the release-2.x branch. -- This is an automated message from the Apache Git Service.

  1   2   >