[jira] [Commented] (LOG4J2-3471) log4j-1.2-api 2.17.2 throws NullPointerException while removing appender with name as null

2022-04-07 Thread Rajesh (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-3471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17519318#comment-17519318 ] Rajesh commented on LOG4J2-3471: [~ggregory] Thanks for the quick fix. > log4j-1.2-api

[GitHub] [logging-log4j2] remkop commented on pull request #763: Added java logging with Asynchronous logger

2022-04-07 Thread GitBox
remkop commented on PR #763: URL: https://github.com/apache/logging-log4j2/pull/763#issuecomment-1092382916 @ruhulmus Thank you for your patience and persistence. What you are proposing (if I understand correctly) is quite different from what we have at the moment. * All of the

[jira] [Commented] (LOG4J2-3471) log4j-1.2-api 2.17.2 throws NullPointerException while removing appender with name as null

2022-04-07 Thread ASF subversion and git services (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-3471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17519239#comment-17519239 ] ASF subversion and git services commented on LOG4J2-3471: - Commi

[jira] [Commented] (LOG4J2-3471) log4j-1.2-api 2.17.2 throws NullPointerException while removing appender with name as null

2022-04-07 Thread ASF subversion and git services (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-3471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17519238#comment-17519238 ] ASF subversion and git services commented on LOG4J2-3471: - Commi

[GitHub] [logging-log4j2] ruhulmus commented on pull request #763: Added java logging with Asynchronous logger

2022-04-07 Thread GitBox
ruhulmus commented on PR #763: URL: https://github.com/apache/logging-log4j2/pull/763#issuecomment-1092256016 > @ruhulmus, I also agree with Gary and Remko: I fail to see the point of this new Maven artifact. What does it have that is missing in the [official documentation](http

[GitHub] [logging-log4j2] ppkarwasz commented on a diff in pull request #815: [LOG4J2-2872] Normalizes level names

2022-04-07 Thread GitBox
ppkarwasz commented on code in PR #815: URL: https://github.com/apache/logging-log4j2/pull/815#discussion_r845563956 ## log4j-api/src/main/java/org/apache/logging/log4j/Level.java: ## @@ -259,15 +258,23 @@ public String toString() { * @throws java.lang.IllegalArgumentExcep

[GitHub] [logging-log4j2] garydgregory commented on a diff in pull request #815: [LOG4J2-2872] Normalizes level names

2022-04-07 Thread GitBox
garydgregory commented on code in PR #815: URL: https://github.com/apache/logging-log4j2/pull/815#discussion_r845558255 ## log4j-api/src/main/java/org/apache/logging/log4j/Level.java: ## @@ -276,9 +283,13 @@ public static Level forName(final String name, final int intValue) {

[jira] [Work started] (LOG4J2-2872) Unable to parse Custom Log Levels

2022-04-07 Thread Piotr Karwasz (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-2872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on LOG4J2-2872 started by Piotr Karwasz. - > Unable to parse Custom Log Levels > - > >

[GitHub] [logging-log4j2] garydgregory commented on a diff in pull request #815: [LOG4J2-2872] Normalizes level names

2022-04-07 Thread GitBox
garydgregory commented on code in PR #815: URL: https://github.com/apache/logging-log4j2/pull/815#discussion_r845557940 ## log4j-api/src/main/java/org/apache/logging/log4j/Level.java: ## @@ -259,15 +258,23 @@ public String toString() { * @throws java.lang.IllegalArgumentEx

[GitHub] [logging-log4j2] ppkarwasz commented on pull request #763: Added java logging with Asynchronous logger

2022-04-07 Thread GitBox
ppkarwasz commented on PR #763: URL: https://github.com/apache/logging-log4j2/pull/763#issuecomment-1092193939 @ruhulmus, I also agree with Gary and Remko: I fail to see the point of this new Maven artifact. What does it have that is missing in the [official documentation](https://loggin

[jira] [Resolved] (LOG4J2-3471) log4j-1.2-api 2.17.2 throws NullPointerException while removing appender with name as null

2022-04-07 Thread Gary D. Gregory (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-3471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory resolved LOG4J2-3471. - Fix Version/s: 2.17.3 Resolution: Fixed [~rajeshn]  Thank you for your report.

[GitHub] [logging-log4j2] ppkarwasz opened a new pull request, #815: [LOG4J2-2872] Normalizes level names

2022-04-07 Thread GitBox
ppkarwasz opened a new pull request, #815: URL: https://github.com/apache/logging-log4j2/pull/815 Calling `Level.forName` with a non upper case argument, can create a custom level that can not be retrieved using `Level.toLevel`. This PR fixes to upper case the keys in the `Level.LEVEL

[jira] [Commented] (LOG4J2-3471) log4j-1.2-api 2.17.2 throws NullPointerException while removing appender with name as null

2022-04-07 Thread ASF subversion and git services (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-3471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17519160#comment-17519160 ] ASF subversion and git services commented on LOG4J2-3471: - Commi

[jira] [Updated] (LOG4J2-3471) log4j-1.2-api-2.17.2 throws NullPointerException while removing appender with name as null

2022-04-07 Thread Gary D. Gregory (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-3471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory updated LOG4J2-3471: Summary: log4j-1.2-api-2.17.2 throws NullPointerException while removing appender with nam

[jira] [Updated] (LOG4J2-3471) log4j-1.2-api 2.17.2 throws NullPointerException while removing appender with name as null

2022-04-07 Thread Gary D. Gregory (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-3471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory updated LOG4J2-3471: Summary: log4j-1.2-api 2.17.2 throws NullPointerException while removing appender with nam

[jira] [Commented] (LOG4J2-3471) log4j-1.2-api-2.17.2 throws exception while removing appender with name as null

2022-04-07 Thread ASF subversion and git services (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-3471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17519158#comment-17519158 ] ASF subversion and git services commented on LOG4J2-3471: - Commi

[jira] [Assigned] (LOG4J2-2872) Unable to parse Custom Log Levels

2022-04-07 Thread Piotr Karwasz (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-2872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Karwasz reassigned LOG4J2-2872: - Assignee: Piotr Karwasz > Unable to parse Custom Log Levels > -

[jira] [Assigned] (LOG4J2-3471) log4j-1.2-api-2.17.2 throws exception while removing appender with name as null

2022-04-07 Thread Gary D. Gregory (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-3471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory reassigned LOG4J2-3471: --- Assignee: Gary D. Gregory > log4j-1.2-api-2.17.2 throws exception while removing ap

[jira] [Assigned] (LOG4J2-3463) java.util.ServiceConfigurationError: org.apache.logging.log4j.spi.Provider: Provider org.apache.logging.log4j.core.impl.Log4jProvider not a subtype

2022-04-07 Thread Gary D. Gregory (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-3463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory reassigned LOG4J2-3463: --- Assignee: (was: Gary D. Gregory) > java.util.ServiceConfigurationError: org.apa

[jira] [Assigned] (LOG4J2-3463) java.util.ServiceConfigurationError: org.apache.logging.log4j.spi.Provider: Provider org.apache.logging.log4j.core.impl.Log4jProvider not a subtype

2022-04-07 Thread Gary D. Gregory (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-3463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory reassigned LOG4J2-3463: --- Assignee: Gary D. Gregory > java.util.ServiceConfigurationError: org.apache.logging

[GitHub] [logging-log4j2] ruhulmus commented on pull request #763: Added java logging with Asynchronous logger

2022-04-07 Thread GitBox
ruhulmus commented on PR #763: URL: https://github.com/apache/logging-log4j2/pull/763#issuecomment-1092154845 Hi @remkop, Did you review the latest one? may I ask What is the additional process for the merge :)? or any additional thing needed? Looking for your feedback :). -- Thi

[jira] [Comment Edited] (LOG4J2-3467) Update from Log4J 2.17.1 to 2.17.2 breaks application

2022-04-07 Thread Piotr Karwasz (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-3467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17519122#comment-17519122 ] Piotr Karwasz edited comment on LOG4J2-3467 at 4/7/22 7:32 PM: ---

[jira] [Commented] (LOG4J2-3467) Update from Log4J 2.17.1 to 2.17.2 breaks application

2022-04-07 Thread Piotr Karwasz (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-3467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17519122#comment-17519122 ] Piotr Karwasz commented on LOG4J2-3467: --- [~veita], Yes, the configuration code in

[jira] [Commented] (LOG4J2-3463) java.util.ServiceConfigurationError: org.apache.logging.log4j.spi.Provider: Provider org.apache.logging.log4j.core.impl.Log4jProvider not a subtype

2022-04-07 Thread Piotr Karwasz (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-3463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17519092#comment-17519092 ] Piotr Karwasz commented on LOG4J2-3463: --- Hello [~smarkhedkar], my PR has a rather

[jira] [Created] (LOG4J2-3471) log4j-1.2-api-2.17.2 throws exception while removing appender with name as null

2022-04-07 Thread Rajesh (Jira)
Rajesh created LOG4J2-3471: -- Summary: log4j-1.2-api-2.17.2 throws exception while removing appender with name as null Key: LOG4J2-3471 URL: https://issues.apache.org/jira/browse/LOG4J2-3471 Project: Log4j 2

[GitHub] [logging-log4j2] vy commented on pull request #814: [DOC] add blank line for markdown rendering

2022-04-07 Thread GitBox
vy commented on PR #814: URL: https://github.com/apache/logging-log4j2/pull/814#issuecomment-1091781306 Thanks @kevinjmh! -- 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

[GitHub] [logging-log4j2] vy merged pull request #814: [DOC] add blank line for markdown rendering

2022-04-07 Thread GitBox
vy merged PR #814: URL: https://github.com/apache/logging-log4j2/pull/814 -- 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: notifications-unsubscr...@logg

[jira] [Commented] (LOG4J2-3470) Expressions in property values are not expanded anymore

2022-04-07 Thread Jan Mosig (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-3470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17518894#comment-17518894 ] Jan Mosig commented on LOG4J2-3470: --- The application's configuration is this: {code}

[jira] [Commented] (LOG4J2-3467) Update from Log4J 2.17.1 to 2.17.2 breaks application

2022-04-07 Thread Alexander Veit (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-3467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17518891#comment-17518891 ] Alexander Veit commented on LOG4J2-3467: OK. Is my interpretation correct that t

[jira] [Comment Edited] (LOG4J2-3470) Expressions in property values are not expanded anymore

2022-04-07 Thread Carter Kozak (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-3470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17518850#comment-17518850 ] Carter Kozak edited comment on LOG4J2-3470 at 4/7/22 12:26 PM: ---

[jira] [Reopened] (LOG4J2-3470) Expressions in property values are not expanded anymore

2022-04-07 Thread Carter Kozak (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-3470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak reopened LOG4J2-3470: -- > Expressions in property values are not expanded anymore > --

[jira] [Closed] (LOG4J2-3470) Expressions in property values are not expanded anymore

2022-04-07 Thread Carter Kozak (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-3470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak closed LOG4J2-3470. Resolution: Duplicate This is a duplicate of https://issues.apache.org/jira/browse/LOG4J2-3424, wh

[jira] [Closed] (LOG4J2-3434) Property is not populating "value"

2022-04-07 Thread Carter Kozak (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-3434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak closed LOG4J2-3434. Resolution: Duplicate This is a duplicate of https://issues.apache.org/jira/browse/LOG4J2-3424, wh

[jira] [Created] (LOG4J2-3470) Expressions in property values are not expanded anymore

2022-04-07 Thread Jan Mosig (Jira)
Jan Mosig created LOG4J2-3470: - Summary: Expressions in property values are not expanded anymore Key: LOG4J2-3470 URL: https://issues.apache.org/jira/browse/LOG4J2-3470 Project: Log4j 2 Issue Typ

[GitHub] [logging-log4j2] kevinjmh opened a new pull request, #814: [DOC] add blank line for markdown rendering

2022-04-07 Thread GitBox
kevinjmh opened a new pull request, #814: URL: https://github.com/apache/logging-log4j2/pull/814 ![image](https://user-images.githubusercontent.com/3809732/162153008-42357499-97a1-4404-ad64-7bd486d5e47b.png) some titles are not rendered correctly. -- This is an automated message f

[jira] [Commented] (LOG4J2-3469) Create new builder from existing Appender

2022-04-07 Thread Ralph Goers (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-3469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17518627#comment-17518627 ] Ralph Goers commented on LOG4J2-3469: - Once a configuration has started you cannot m