[GitHub] [logging-log4j2] ppkarwasz commented on a change in pull request #774: [LOG4J2-3413] Fixes resolution of non-Log4j properties
ppkarwasz commented on a change in pull request #774:
URL: https://github.com/apache/logging-log4j2/pull/774#discussion_r815276131
##
File path:
log4j-api/src/main/java/org/apache/logging/log4j/util/PropertySource.java
##
@@ -100,9 +101,19 @@ public int compare(final PropertySource o1, final
PropertySource o2) {
* @since 2.10.0
*/
final class Util {
-private static final String PREFIXES =
"(?i:^log4j2?[-._/]?|^org\\.apache\\.logging\\.log4j\\.)?";
-private static final Pattern PROPERTY_TOKENIZER =
Pattern.compile(PREFIXES + "([A-Z]*[a-z0-9]+|[A-Z0-9]+)[-._/]?");
+private static final Pattern PREFIX_PATTERN = Pattern.compile(
+// just lookahead for AsyncLogger
+
"(^log4j2?[-._/]?|^org\\.apache\\.logging\\.log4j\\.)|(?=AsyncLogger(Config)?\\.)",
+Pattern.CASE_INSENSITIVE);
+private static final Pattern PROPERTY_TOKENIZER =
Pattern.compile("([A-Z]*[a-z0-9]+|[A-Z0-9]+)[-._/]?");
private static final Map> CACHE = new
ConcurrentHashMap<>();
+static {
+// Add legacy properties without Log4j prefix
+CACHE.put("disableThreadContext", Arrays.asList("disable",
"thread", "context"));
+CACHE.put("disableThreadContextStack", Arrays.asList("disable",
"thread", "context", "stack"));
+CACHE.put("disableThreadContextMap", Arrays.asList("disable",
"thread", "context", "map"));
+CACHE.put("isThreadContextMapInheritable", Arrays.asList("is",
"thread", "context", "map", "inheritable"));
+}
Review comment:
These are here just to satisfy `LegacyPropertiesCompatibilityTest`,
which verifies that the tokenized version of the legacy and normalized
properties are the same.
From the `PropertiesUtil` perspective they are not strictly necessary, since
`getStringProperty("disableThreadContext")` will always look up at least the
exact string "disableThreadContext" and it will retrieve the value before
falling back to token-based comparison.
--
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...@logging.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[jira] [Commented] (LOG4J2-3413) Log4j2 Incorrectly Uses System Property For Level Setting And Got IllegalArgumentException
[
https://issues.apache.org/jira/browse/LOG4J2-3413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17498401#comment-17498401
]
Piotr P. Karwasz commented on LOG4J2-3413:
--
I submitted [PR #774|https://github.com/apache/logging-log4j2/pull/774], which
should solve the problem of properties without a {{log4j}},
{{org.apache.logging.log4j}} prefix being picked up by Log4j.
> Log4j2 Incorrectly Uses System Property For Level Setting And Got
> IllegalArgumentException
> --
>
> Key: LOG4J2-3413
> URL: https://issues.apache.org/jira/browse/LOG4J2-3413
> Project: Log4j 2
> Issue Type: Bug
> Components: Configuration
>Affects Versions: 2.17.1
> Environment: IBM WAS 9, JAVA 8
>Reporter: Sean Wang
>Priority: Major
> Attachments: Log4j2IssueLogs.txt
>
>
> We have an environment parameter in IBM WAS 9 running JAVA 8 with a name of
> "level" and a value of "DEVL". This parameter is used by applications to
> detect the environment they are on and worked fine with log4j2.8.2.
> After upgraded to Log4j2.17.1, for some reason the Log4j2 grabs that
> parameter during the initialization, ignoring the settings in the log4j2.xml,
> and spills a _java.lang.IllegalArgumentException: Unknown level constant
> [DEVL]_ in the system log.
>
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[GitHub] [logging-log4j2] ppkarwasz commented on pull request #774: [LOG4J2-3413] Fixes resolution of non-Log4j properties
ppkarwasz commented on pull request #774: URL: https://github.com/apache/logging-log4j2/pull/774#issuecomment-1051598903 Yes, I thought JIRA would link the PR automatically, but apparently it only checks the title provided at submission time. -- 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...@logging.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [logging-log4j2] jvz opened a new pull request #775: [LOG4J2-3415] Support JSON configuration using embedded JSON parser
jvz opened a new pull request #775: URL: https://github.com/apache/logging-log4j2/pull/775 * Moves `JsonReader` from log4j-layout-json-template to log4j-api. * Adds support for comments in parsing JSON for compatibility with existing Jackson usage. * Adds new default `JsonConfigurationFactory` implementation using this. -- 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...@logging.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Assigned] (LOG4J2-3415) Support JSON configuration using embedded JSON parser
[ https://issues.apache.org/jira/browse/LOG4J2-3415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker reassigned LOG4J2-3415: --- Assignee: Matt Sicker > Support JSON configuration using embedded JSON parser > - > > Key: LOG4J2-3415 > URL: https://issues.apache.org/jira/browse/LOG4J2-3415 > Project: Log4j 2 > Issue Type: New Feature > Components: Configuration >Reporter: Matt Sicker >Assignee: Matt Sicker >Priority: Major > > In order to reduce the required module list for log4j-core to java.base, that > leaves us with no parsers for configuration files besides properties. This is > not ideal. > JsonTemplateLayout contains a basic JSON parser that can be used for JSON > configuration. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (LOG4J2-3415) Support JSON configuration using embedded JSON parser
Matt Sicker created LOG4J2-3415: --- Summary: Support JSON configuration using embedded JSON parser Key: LOG4J2-3415 URL: https://issues.apache.org/jira/browse/LOG4J2-3415 Project: Log4j 2 Issue Type: New Feature Components: Configuration Reporter: Matt Sicker In order to reduce the required module list for log4j-core to java.base, that leaves us with no parsers for configuration files besides properties. This is not ideal. JsonTemplateLayout contains a basic JSON parser that can be used for JSON configuration. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Comment Edited] (LOG4J2-3412) Rolling file does not work with new version of log4j2 2.16 and 2.17.1 versions
[
https://issues.apache.org/jira/browse/LOG4J2-3412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17498247#comment-17498247
]
Piotr P. Karwasz edited comment on LOG4J2-3412 at 2/25/22, 9:07 PM:
[~rgoers]: maybe just a _"if file name is not provided, the appropriate file
pattern is used"_.
However personally I find the {{RollingFileAppender}} deserves a page of its
own to better expose the great amount of configuration possibilities it
provides.
was (Author: JIRAUSER280472):
[~rgoers]: maybe just a _"if file name is not provided, the appropriate file
pattern is used"_.
However personally I find the {{RollingFileAppender}} deserves a page of its
own to better expose the great amount of configuration possibilities it exposes.
> Rolling file does not work with new version of log4j2 2.16 and 2.17.1 versions
> --
>
> Key: LOG4J2-3412
> URL: https://issues.apache.org/jira/browse/LOG4J2-3412
> Project: Log4j 2
> Issue Type: Bug
> Components: API, Appenders
>Affects Versions: 2.16.0, 2.17.0
>Reporter: Srikanth
>Priority: Major
> Labels: Rollover, log4j2
>
> Rolling file is not creating the next day log file and previous day file is
> being written with new logs in windows tomcat
> Details of logging.properties used:
>
> {code:java}
> rootLogger.level = all
> appenders = rolling, console
> appender.console.type = Console
> appender.console.name = console
> appender.console.layout.type = PatternLayout
> appender.console.layout.pattern = %d [%-5p] (%F:%M:%L) %m%n
> appender.rolling.type = RollingFile
> appender.rolling.name = rolling
> appender.rolling.fileName = C:/Local/Logs/${date:MMdd}_myfile.log
> appender.rolling.filePattern = C:/Local/Logs/%d{MMdd}_myfile.log
> appender.rolling.layout.type = PatternLayout
> appender.rolling.layout.pattern = %d [%-5p] [%F:%M:%L] %m%n
> appender.rolling.policies.type = Policies
> appender.rolling.policies.time.type = TimeBasedTriggeringPolicy
> appender.rolling.policies.time.interval = 1
> appender.rolling.policies.time.modulate = true
> rootLogger.appenderRefs = rolling, console
> rootLogger.appenderRef.console.ref = console
> rootLogger.appenderRef.rolling.ref = rolling
> rootLogger.appenderRef.stdout.ref = console, rolling
> {code}
>
> ===
> I am using below configuration for the java web application: Tomcat 9.x
> log4j-api-2.16.0.jar
> log4j-core-2.16.0.jar
>
> I even tried with 2.17.1 version as well.
>
> everying working fine , logs are generating but when i trigger the log file
> next day the logs are triggring in old day file only.
> suppose today (12-01-2022) i am hitting the URL. The file creates and logging
> data in the file 20220112_myfile.log
> i change the date and hitting the URL again, Here i am expecting the code
> should create 20220113_myfile.log, but the log file not creating instead all
> logs are going in the 20220112_myfile.log.
> After i restart the server the new file generating, but i need the file by
> hitting the URL if it is a different date the log file to be created with the
> same date, not by restarting the server.
> Can someone help me on this.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[GitHub] [logging-log4j2] ppkarwasz opened a new pull request #774: [LOG4J-3413] Fixes resolution of non-Log4j properties
ppkarwasz opened a new pull request #774: URL: https://github.com/apache/logging-log4j2/pull/774 For properties that does not start with `log4j` or `org.apache.logging.log4j` the loosed token-based lookup should not be applied. There are a couple of exceptions to this rule: the properties that start with `AsyncLogger` and those related to `disableThreadContext`. This PR prevents properties such as `level` to be used as a substitute for `log4j2.level` -- 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...@logging.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (LOG4J2-3413) Log4j2 Incorrectly Uses System Property For Level Setting And Got IllegalArgumentException
[
https://issues.apache.org/jira/browse/LOG4J2-3413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17498273#comment-17498273
]
Piotr P. Karwasz commented on LOG4J2-3413:
--
It's a bug in the property sources (cf.
[documentation|https://logging.apache.org/log4j/2.x/manual/configuration.html#SystemProperties])
introduced in Log4j 2.10.0. The algorithm that allows to support both legacy
property names and new standardized names is too liberal. It takes your
{{LEVEL}} environment variable as a valid substitute for {{log4j2.level}}.
As a workaround you can declare a Java system property:
{noformat}
org.apache.logging.log4j.level=ERROR
{noformat}
Since it is literally the property requested by Log4j code, it will override
the {{LEVEL}} environment variable.
> Log4j2 Incorrectly Uses System Property For Level Setting And Got
> IllegalArgumentException
> --
>
> Key: LOG4J2-3413
> URL: https://issues.apache.org/jira/browse/LOG4J2-3413
> Project: Log4j 2
> Issue Type: Bug
> Components: Configuration
>Affects Versions: 2.17.1
> Environment: IBM WAS 9, JAVA 8
>Reporter: Sean Wang
>Priority: Major
> Attachments: Log4j2IssueLogs.txt
>
>
> We have an environment parameter in IBM WAS 9 running JAVA 8 with a name of
> "level" and a value of "DEVL". This parameter is used by applications to
> detect the environment they are on and worked fine with log4j2.8.2.
> After upgraded to Log4j2.17.1, for some reason the Log4j2 grabs that
> parameter during the initialization, ignoring the settings in the log4j2.xml,
> and spills a _java.lang.IllegalArgumentException: Unknown level constant
> [DEVL]_ in the system log.
>
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (LOG4J2-3412) Rolling file does not work with new version of log4j2 2.16 and 2.17.1 versions
[
https://issues.apache.org/jira/browse/LOG4J2-3412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17498247#comment-17498247
]
Piotr P. Karwasz commented on LOG4J2-3412:
--
[~rgoers]: maybe just a _"if file name is not provided, the appropriate file
pattern is used"_.
However personally I find the {{RollingFileAppender}} deserves a page of its
own to better expose the great amount of configuration possibilities it exposes.
> Rolling file does not work with new version of log4j2 2.16 and 2.17.1 versions
> --
>
> Key: LOG4J2-3412
> URL: https://issues.apache.org/jira/browse/LOG4J2-3412
> Project: Log4j 2
> Issue Type: Bug
> Components: API, Appenders
>Affects Versions: 2.16.0, 2.17.0
>Reporter: Srikanth
>Priority: Major
> Labels: Rollover, log4j2
>
> Rolling file is not creating the next day log file and previous day file is
> being written with new logs in windows tomcat
> Details of logging.properties used:
>
> {code:java}
> rootLogger.level = all
> appenders = rolling, console
> appender.console.type = Console
> appender.console.name = console
> appender.console.layout.type = PatternLayout
> appender.console.layout.pattern = %d [%-5p] (%F:%M:%L) %m%n
> appender.rolling.type = RollingFile
> appender.rolling.name = rolling
> appender.rolling.fileName = C:/Local/Logs/${date:MMdd}_myfile.log
> appender.rolling.filePattern = C:/Local/Logs/%d{MMdd}_myfile.log
> appender.rolling.layout.type = PatternLayout
> appender.rolling.layout.pattern = %d [%-5p] [%F:%M:%L] %m%n
> appender.rolling.policies.type = Policies
> appender.rolling.policies.time.type = TimeBasedTriggeringPolicy
> appender.rolling.policies.time.interval = 1
> appender.rolling.policies.time.modulate = true
> rootLogger.appenderRefs = rolling, console
> rootLogger.appenderRef.console.ref = console
> rootLogger.appenderRef.rolling.ref = rolling
> rootLogger.appenderRef.stdout.ref = console, rolling
> {code}
>
> ===
> I am using below configuration for the java web application: Tomcat 9.x
> log4j-api-2.16.0.jar
> log4j-core-2.16.0.jar
>
> I even tried with 2.17.1 version as well.
>
> everying working fine , logs are generating but when i trigger the log file
> next day the logs are triggring in old day file only.
> suppose today (12-01-2022) i am hitting the URL. The file creates and logging
> data in the file 20220112_myfile.log
> i change the date and hitting the URL again, Here i am expecting the code
> should create 20220113_myfile.log, but the log file not creating instead all
> logs are going in the 20220112_myfile.log.
> After i restart the server the new file generating, but i need the file by
> hitting the URL if it is a different date the log file to be created with the
> same date, not by restarting the server.
> Can someone help me on this.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (LOG4J2-3412) Rolling file does not work with new version of log4j2 2.16 and 2.17.1 versions
[
https://issues.apache.org/jira/browse/LOG4J2-3412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17498201#comment-17498201
]
Ralph Goers commented on LOG4J2-3412:
-
[~Dundigala] You can either do as Piotr suggests or you can create a
subdirectory for the rolled over files and change the filePattern to reference
that.
Also, you don't have a delete action configured so the rolled over files will
never be deleted by Log4j. If you add one Log4j can ensure that you do not run
out of disk space.
[~ppkarwasz] What documentation are you thinking needs fixing?
> Rolling file does not work with new version of log4j2 2.16 and 2.17.1 versions
> --
>
> Key: LOG4J2-3412
> URL: https://issues.apache.org/jira/browse/LOG4J2-3412
> Project: Log4j 2
> Issue Type: Bug
> Components: API, Appenders
>Affects Versions: 2.16.0, 2.17.0
>Reporter: Srikanth
>Priority: Major
> Labels: Rollover, log4j2
>
> Rolling file is not creating the next day log file and previous day file is
> being written with new logs in windows tomcat
> Details of logging.properties used:
>
> {code:java}
> rootLogger.level = all
> appenders = rolling, console
> appender.console.type = Console
> appender.console.name = console
> appender.console.layout.type = PatternLayout
> appender.console.layout.pattern = %d [%-5p] (%F:%M:%L) %m%n
> appender.rolling.type = RollingFile
> appender.rolling.name = rolling
> appender.rolling.fileName = C:/Local/Logs/${date:MMdd}_myfile.log
> appender.rolling.filePattern = C:/Local/Logs/%d{MMdd}_myfile.log
> appender.rolling.layout.type = PatternLayout
> appender.rolling.layout.pattern = %d [%-5p] [%F:%M:%L] %m%n
> appender.rolling.policies.type = Policies
> appender.rolling.policies.time.type = TimeBasedTriggeringPolicy
> appender.rolling.policies.time.interval = 1
> appender.rolling.policies.time.modulate = true
> rootLogger.appenderRefs = rolling, console
> rootLogger.appenderRef.console.ref = console
> rootLogger.appenderRef.rolling.ref = rolling
> rootLogger.appenderRef.stdout.ref = console, rolling
> {code}
>
> ===
> I am using below configuration for the java web application: Tomcat 9.x
> log4j-api-2.16.0.jar
> log4j-core-2.16.0.jar
>
> I even tried with 2.17.1 version as well.
>
> everying working fine , logs are generating but when i trigger the log file
> next day the logs are triggring in old day file only.
> suppose today (12-01-2022) i am hitting the URL. The file creates and logging
> data in the file 20220112_myfile.log
> i change the date and hitting the URL again, Here i am expecting the code
> should create 20220113_myfile.log, but the log file not creating instead all
> logs are going in the 20220112_myfile.log.
> After i restart the server the new file generating, but i need the file by
> hitting the URL if it is a different date the log file to be created with the
> same date, not by restarting the server.
> Can someone help me on this.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (LOG4J2-3412) Rolling file does not work with new version of log4j2 2.16 and 2.17.1 versions
[
https://issues.apache.org/jira/browse/LOG4J2-3412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17498177#comment-17498177
]
Piotr P. Karwasz commented on LOG4J2-3412:
--
[~Dundigala]: the `fileName` attribute is optional for the
`RollingFileAppender`. If it is missing, a direct write rollover strategy is
used (cf.
[documentation|https://logging.apache.org/log4j/2.x/manual/appenders.html#DirectWrite_Rollover_Strategy]).
Try:
{noformat}
appender.rolling.type = RollingFile
appender.rolling.name = rolling
appender.rolling.filePattern = C:/Local/Logs/%d{MMdd}_myfile.log
appender.rolling.layout.type = PatternLayout
appender.rolling.layout.pattern = %d [%-5p] [%F:%M:%L] %m%n
appender.rolling.policy.type = TimeBasedTriggeringPolicy
{noformat}
To me this looks like a documentation problem.
> Rolling file does not work with new version of log4j2 2.16 and 2.17.1 versions
> --
>
> Key: LOG4J2-3412
> URL: https://issues.apache.org/jira/browse/LOG4J2-3412
> Project: Log4j 2
> Issue Type: Bug
> Components: API, Appenders
>Affects Versions: 2.16.0, 2.17.0
>Reporter: Srikanth
>Priority: Major
> Labels: Rollover, log4j2
>
> Rolling file is not creating the next day log file and previous day file is
> being written with new logs in windows tomcat
> Details of logging.properties used:
>
> {code:java}
> rootLogger.level = all
> appenders = rolling, console
> appender.console.type = Console
> appender.console.name = console
> appender.console.layout.type = PatternLayout
> appender.console.layout.pattern = %d [%-5p] (%F:%M:%L) %m%n
> appender.rolling.type = RollingFile
> appender.rolling.name = rolling
> appender.rolling.fileName = C:/Local/Logs/${date:MMdd}_myfile.log
> appender.rolling.filePattern = C:/Local/Logs/%d{MMdd}_myfile.log
> appender.rolling.layout.type = PatternLayout
> appender.rolling.layout.pattern = %d [%-5p] [%F:%M:%L] %m%n
> appender.rolling.policies.type = Policies
> appender.rolling.policies.time.type = TimeBasedTriggeringPolicy
> appender.rolling.policies.time.interval = 1
> appender.rolling.policies.time.modulate = true
> rootLogger.appenderRefs = rolling, console
> rootLogger.appenderRef.console.ref = console
> rootLogger.appenderRef.rolling.ref = rolling
> rootLogger.appenderRef.stdout.ref = console, rolling
> {code}
>
> ===
> I am using below configuration for the java web application: Tomcat 9.x
> log4j-api-2.16.0.jar
> log4j-core-2.16.0.jar
>
> I even tried with 2.17.1 version as well.
>
> everying working fine , logs are generating but when i trigger the log file
> next day the logs are triggring in old day file only.
> suppose today (12-01-2022) i am hitting the URL. The file creates and logging
> data in the file 20220112_myfile.log
> i change the date and hitting the URL again, Here i am expecting the code
> should create 20220113_myfile.log, but the log file not creating instead all
> logs are going in the 20220112_myfile.log.
> After i restart the server the new file generating, but i need the file by
> hitting the URL if it is a different date the log file to be created with the
> same date, not by restarting the server.
> Can someone help me on this.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (LOG4J2-3413) Log4j2 Incorrectly Uses System Property For Level Setting And Got IllegalArgumentException
[ https://issues.apache.org/jira/browse/LOG4J2-3413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Wang updated LOG4J2-3413: -- Description: We have an environment parameter in IBM WAS 9 running JAVA 8 with a name of "level" and a value of "DEVL". This parameter is used by applications to detect the environment they are on and worked fine with log4j2.8.2. After upgraded to Log4j2.17.1, for some reason the Log4j2 grabs that parameter during the initialization, ignoring the settings in the log4j2.xml, and spills a _java.lang.IllegalArgumentException: Unknown level constant [DEVL]_ in the system log. was: We have an environment parameter in IBM WAS 9 running JAVA 8 with a name of "level" and a value of "DEVL". This parameter is used by applications to detect the environment they are on and worked fine with log4j1.x. After upgraded to Log4j2.17.1, for some reason the Log4j2 grabs that parameter during the initialization, ignoring the settings in the log4j2.xml, and spills a _java.lang.IllegalArgumentException: Unknown level constant [DEVL]_ in the system log. > Log4j2 Incorrectly Uses System Property For Level Setting And Got > IllegalArgumentException > -- > > Key: LOG4J2-3413 > URL: https://issues.apache.org/jira/browse/LOG4J2-3413 > Project: Log4j 2 > Issue Type: Bug > Components: Configuration >Affects Versions: 2.17.1 > Environment: IBM WAS 9, JAVA 8 >Reporter: Sean Wang >Priority: Major > Attachments: Log4j2IssueLogs.txt > > > We have an environment parameter in IBM WAS 9 running JAVA 8 with a name of > "level" and a value of "DEVL". This parameter is used by applications to > detect the environment they are on and worked fine with log4j2.8.2. > After upgraded to Log4j2.17.1, for some reason the Log4j2 grabs that > parameter during the initialization, ignoring the settings in the log4j2.xml, > and spills a _java.lang.IllegalArgumentException: Unknown level constant > [DEVL]_ in the system log. > > > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (LOG4J2-3414) Release date for 2.17.2 to ease migration from log4j1.x to log4j 2.x in one of our product
[ https://issues.apache.org/jira/browse/LOG4J2-3414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17498134#comment-17498134 ] Gary D. Gregory commented on LOG4J2-3414: - [~PoojaTheCoder] Please see https://logging.apache.org/log4j/2.x/mail-lists.html > Release date for 2.17.2 to ease migration from log4j1.x to log4j 2.x in one > of our product > -- > > Key: LOG4J2-3414 > URL: https://issues.apache.org/jira/browse/LOG4J2-3414 > Project: Log4j 2 > Issue Type: Bug > Components: Appenders >Affects Versions: 2.17.1 >Reporter: Pooja Pandey >Priority: Major > > We are trying to migrate one of our product from log4j 1.x to log4j 2.x by > using the Log4j 1.x bridge. > We are using custom FileAppender and ConsoleAppender in our product. However > when we are trying to build the code using Log4j 1.x bridge, build fails with > errors 'cannot find symbol'. We are trying to resolve this yet. > I have found a mention on web that "Version 2.17.2 will contain about 50 > improvements in the Log4j 1.x bridge, among them some old classes like > org.apache.log4j.FileAppender". > I expect that hopefully version 2.17.2 will ease the migration process. > I wanted to check does anyone knows the date or approximate date for the > release of 2.17.2? > Thanks! -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (LOG4J2-3414) Release date for 2.17.2 to ease migration from log4j1.x to log4j 2.x in one of our product
[ https://issues.apache.org/jira/browse/LOG4J2-3414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17498122#comment-17498122 ] Pooja Pandey commented on LOG4J2-3414: -- [~ggregory] , I could subscribe to mailing list. Thanks :) > Release date for 2.17.2 to ease migration from log4j1.x to log4j 2.x in one > of our product > -- > > Key: LOG4J2-3414 > URL: https://issues.apache.org/jira/browse/LOG4J2-3414 > Project: Log4j 2 > Issue Type: Bug > Components: Appenders >Affects Versions: 2.17.1 >Reporter: Pooja Pandey >Priority: Major > > We are trying to migrate one of our product from log4j 1.x to log4j 2.x by > using the Log4j 1.x bridge. > We are using custom FileAppender and ConsoleAppender in our product. However > when we are trying to build the code using Log4j 1.x bridge, build fails with > errors 'cannot find symbol'. We are trying to resolve this yet. > I have found a mention on web that "Version 2.17.2 will contain about 50 > improvements in the Log4j 1.x bridge, among them some old classes like > org.apache.log4j.FileAppender". > I expect that hopefully version 2.17.2 will ease the migration process. > I wanted to check does anyone knows the date or approximate date for the > release of 2.17.2? > Thanks! -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (LOG4J2-3414) Release date for 2.17.2 to ease migration from log4j1.x to log4j 2.x in one of our product
[ https://issues.apache.org/jira/browse/LOG4J2-3414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17498115#comment-17498115 ] Pooja Pandey commented on LOG4J2-3414: -- [~ggregory] , I could not figure out how to subscribe on the mailing list. Can you please help with steps to subscribe for the mailing list?? Thanks, Pooja > Release date for 2.17.2 to ease migration from log4j1.x to log4j 2.x in one > of our product > -- > > Key: LOG4J2-3414 > URL: https://issues.apache.org/jira/browse/LOG4J2-3414 > Project: Log4j 2 > Issue Type: Bug > Components: Appenders >Affects Versions: 2.17.1 >Reporter: Pooja Pandey >Priority: Major > > We are trying to migrate one of our product from log4j 1.x to log4j 2.x by > using the Log4j 1.x bridge. > We are using custom FileAppender and ConsoleAppender in our product. However > when we are trying to build the code using Log4j 1.x bridge, build fails with > errors 'cannot find symbol'. We are trying to resolve this yet. > I have found a mention on web that "Version 2.17.2 will contain about 50 > improvements in the Log4j 1.x bridge, among them some old classes like > org.apache.log4j.FileAppender". > I expect that hopefully version 2.17.2 will ease the migration process. > I wanted to check does anyone knows the date or approximate date for the > release of 2.17.2? > Thanks! -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (LOG4J2-3414) Release date for 2.17.2 to ease migration from log4j1.x to log4j 2.x in one of our product
[ https://issues.apache.org/jira/browse/LOG4J2-3414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory closed LOG4J2-3414. --- Resolution: Information Provided [~PoojaTheCoder] please subscribe to the user's mailing list instead of creating a ticket for this question. The release announcement will be posted on the mailing list. > Release date for 2.17.2 to ease migration from log4j1.x to log4j 2.x in one > of our product > -- > > Key: LOG4J2-3414 > URL: https://issues.apache.org/jira/browse/LOG4J2-3414 > Project: Log4j 2 > Issue Type: Bug > Components: Appenders >Affects Versions: 2.17.1 >Reporter: Pooja Pandey >Priority: Major > > We are trying to migrate one of our product from log4j 1.x to log4j 2.x by > using the Log4j 1.x bridge. > We are using custom FileAppender and ConsoleAppender in our product. However > when we are trying to build the code using Log4j 1.x bridge, build fails with > errors 'cannot find symbol'. We are trying to resolve this yet. > I have found a mention on web that "Version 2.17.2 will contain about 50 > improvements in the Log4j 1.x bridge, among them some old classes like > org.apache.log4j.FileAppender". > I expect that hopefully version 2.17.2 will ease the migration process. > I wanted to check does anyone knows the date or approximate date for the > release of 2.17.2? > Thanks! -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Comment Edited] (LOG4J2-3414) Release date for 2.17.2 to ease migration from log4j1.x to log4j 2.x in one of our product
[ https://issues.apache.org/jira/browse/LOG4J2-3414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17498054#comment-17498054 ] Pooja Pandey edited comment on LOG4J2-3414 at 2/25/22, 11:38 AM: - [~ppkarwasz], thanks for your response. was (Author: JIRAUSER285751): [~ppkarwasz], thanks for your response. Any idea how can I use/test RC1 ?? > Release date for 2.17.2 to ease migration from log4j1.x to log4j 2.x in one > of our product > -- > > Key: LOG4J2-3414 > URL: https://issues.apache.org/jira/browse/LOG4J2-3414 > Project: Log4j 2 > Issue Type: Bug > Components: Appenders >Affects Versions: 2.17.1 >Reporter: Pooja Pandey >Priority: Major > > We are trying to migrate one of our product from log4j 1.x to log4j 2.x by > using the Log4j 1.x bridge. > We are using custom FileAppender and ConsoleAppender in our product. However > when we are trying to build the code using Log4j 1.x bridge, build fails with > errors 'cannot find symbol'. We are trying to resolve this yet. > I have found a mention on web that "Version 2.17.2 will contain about 50 > improvements in the Log4j 1.x bridge, among them some old classes like > org.apache.log4j.FileAppender". > I expect that hopefully version 2.17.2 will ease the migration process. > I wanted to check does anyone knows the date or approximate date for the > release of 2.17.2? > Thanks! -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (LOG4J2-3414) Release date for 2.17.2 to ease migration from log4j1.x to log4j 2.x in one of our product
[ https://issues.apache.org/jira/browse/LOG4J2-3414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17498054#comment-17498054 ] Pooja Pandey commented on LOG4J2-3414: -- [~ppkarwasz], thanks for your response. Any idea how can I use/test RC1 ?? > Release date for 2.17.2 to ease migration from log4j1.x to log4j 2.x in one > of our product > -- > > Key: LOG4J2-3414 > URL: https://issues.apache.org/jira/browse/LOG4J2-3414 > Project: Log4j 2 > Issue Type: Bug > Components: Appenders >Affects Versions: 2.17.1 >Reporter: Pooja Pandey >Priority: Major > > We are trying to migrate one of our product from log4j 1.x to log4j 2.x by > using the Log4j 1.x bridge. > We are using custom FileAppender and ConsoleAppender in our product. However > when we are trying to build the code using Log4j 1.x bridge, build fails with > errors 'cannot find symbol'. We are trying to resolve this yet. > I have found a mention on web that "Version 2.17.2 will contain about 50 > improvements in the Log4j 1.x bridge, among them some old classes like > org.apache.log4j.FileAppender". > I expect that hopefully version 2.17.2 will ease the migration process. > I wanted to check does anyone knows the date or approximate date for the > release of 2.17.2? > Thanks! -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Comment Edited] (LOG4J2-3414) Release date for 2.17.2 to ease migration from log4j1.x to log4j 2.x in one of our product
[ https://issues.apache.org/jira/browse/LOG4J2-3414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17498033#comment-17498033 ] Piotr P. Karwasz edited comment on LOG4J2-3414 at 2/25/22, 10:33 AM: - RC1 is ready and there is a vote in progress (cf. [mailing list|https://lists.apache.org/thread/xjo6dkj3ldcfpt45rydwd1doxydzmd2l]). You might want to check the RC1 too and test if it suits your needs. was (Author: JIRAUSER280472): RC1 is ready and there is a vote in progress (cf. [mailing list|https://lists.apache.org/thread/xjo6dkj3ldcfpt45rydwd1doxydzmd2l]). > Release date for 2.17.2 to ease migration from log4j1.x to log4j 2.x in one > of our product > -- > > Key: LOG4J2-3414 > URL: https://issues.apache.org/jira/browse/LOG4J2-3414 > Project: Log4j 2 > Issue Type: Bug > Components: Appenders >Affects Versions: 2.17.1 >Reporter: Pooja Pandey >Priority: Major > > We are trying to migrate one of our product from log4j 1.x to log4j 2.x by > using the Log4j 1.x bridge. > We are using custom FileAppender and ConsoleAppender in our product. However > when we are trying to build the code using Log4j 1.x bridge, build fails with > errors 'cannot find symbol'. We are trying to resolve this yet. > I have found a mention on web that "Version 2.17.2 will contain about 50 > improvements in the Log4j 1.x bridge, among them some old classes like > org.apache.log4j.FileAppender". > I expect that hopefully version 2.17.2 will ease the migration process. > I wanted to check does anyone knows the date or approximate date for the > release of 2.17.2? > Thanks! -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (LOG4J2-3414) Release date for 2.17.2 to ease migration from log4j1.x to log4j 2.x in one of our product
[ https://issues.apache.org/jira/browse/LOG4J2-3414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17498033#comment-17498033 ] Piotr P. Karwasz commented on LOG4J2-3414: -- RC1 is ready and there is a vote in progress (cf. [mailing list|https://lists.apache.org/thread/xjo6dkj3ldcfpt45rydwd1doxydzmd2l]). > Release date for 2.17.2 to ease migration from log4j1.x to log4j 2.x in one > of our product > -- > > Key: LOG4J2-3414 > URL: https://issues.apache.org/jira/browse/LOG4J2-3414 > Project: Log4j 2 > Issue Type: Bug > Components: Appenders >Affects Versions: 2.17.1 >Reporter: Pooja Pandey >Priority: Major > > We are trying to migrate one of our product from log4j 1.x to log4j 2.x by > using the Log4j 1.x bridge. > We are using custom FileAppender and ConsoleAppender in our product. However > when we are trying to build the code using Log4j 1.x bridge, build fails with > errors 'cannot find symbol'. We are trying to resolve this yet. > I have found a mention on web that "Version 2.17.2 will contain about 50 > improvements in the Log4j 1.x bridge, among them some old classes like > org.apache.log4j.FileAppender". > I expect that hopefully version 2.17.2 will ease the migration process. > I wanted to check does anyone knows the date or approximate date for the > release of 2.17.2? > Thanks! -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (LOG4J2-3414) Release date for 2.17.2 to ease migration from log4j1.x to log4j 2.x in one of our product
Pooja Pandey created LOG4J2-3414: Summary: Release date for 2.17.2 to ease migration from log4j1.x to log4j 2.x in one of our product Key: LOG4J2-3414 URL: https://issues.apache.org/jira/browse/LOG4J2-3414 Project: Log4j 2 Issue Type: Bug Components: Appenders Affects Versions: 2.17.1 Reporter: Pooja Pandey We are trying to migrate one of our product from log4j 1.x to log4j 2.x by using the Log4j 1.x bridge. We are using custom FileAppender and ConsoleAppender in our product. However when we are trying to build the code using Log4j 1.x bridge, build fails with errors 'cannot find symbol'. We are trying to resolve this yet. I have found a mention on web that "Version 2.17.2 will contain about 50 improvements in the Log4j 1.x bridge, among them some old classes like org.apache.log4j.FileAppender". I expect that hopefully version 2.17.2 will ease the migration process. I wanted to check does anyone knows the date or approximate date for the release of 2.17.2? Thanks! -- This message was sent by Atlassian Jira (v8.20.1#820001)
