[jira] [Created] (LOG4J2-3418) Proper registration of Log4j2CloudConfigLoggingSystem
Piotr P. Karwasz created LOG4J2-3418:
Summary: Proper registration of Log4j2CloudConfigLoggingSystem
Key: LOG4J2-3418
URL: https://issues.apache.org/jira/browse/LOG4J2-3418
Project: Log4j 2
Issue Type: Bug
Components: Spring
Affects Versions: 2.14.0
Reporter: Piotr P. Karwasz
The current version of {{log4j-spring-boot}} sets Java's
{{org.springframework.boot.logging.LoggingSystem}} property to force the usage
of the {{Log4j2CloudConfigLoggingSystem}}.
This can potentially break applications running in the same JVM, if they use
different logging systems.
The artifact should use the {{spring.factories}} detection mechanism instead.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (LOG4J2-3416) Line Number Not getting printeed
[
https://issues.apache.org/jira/browse/LOG4J2-3416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17498748#comment-17498748
]
Sagar Salal commented on LOG4J2-3416:
-
[~rgoers] I have used IncludeLocation=true also
Please find below for your reference
> Line Number Not getting printeed
>
>
> Key: LOG4J2-3416
> URL: https://issues.apache.org/jira/browse/LOG4J2-3416
> Project: Log4j 2
> Issue Type: Bug
> Components: Appenders
>Affects Versions: 2.17.0
>Reporter: Sagar Salal
>Priority: Major
>
> I am not able to print line numbers in logs. I am using 2.17.0 version and
> using pattern
> pattern="%d\{-MM-dd HH:mm:ss,SSS} [%t] %-5p %logger\{36}:%L %X - %m%n" />.
>
> I have tried with multiple patterns but issue still persists. It is basically
> neglecting *%L.* Can anyone please have a look at this?
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (LOG4J2-3416) Line Number Not getting printeed
[
https://issues.apache.org/jira/browse/LOG4J2-3416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17498725#comment-17498725
]
Ralph Goers commented on LOG4J2-3416:
-
Are you using asynchronous logging by chance? Location information is disabled
by default when asynchronous logging is used.
> Line Number Not getting printeed
>
>
> Key: LOG4J2-3416
> URL: https://issues.apache.org/jira/browse/LOG4J2-3416
> Project: Log4j 2
> Issue Type: Bug
> Components: Appenders
>Affects Versions: 2.17.0
>Reporter: Sagar Salal
>Priority: Major
>
> I am not able to print line numbers in logs. I am using 2.17.0 version and
> using pattern
> pattern="%d\{-MM-dd HH:mm:ss,SSS} [%t] %-5p %logger\{36}:%L %X - %m%n" />.
>
> I have tried with multiple patterns but issue still persists. It is basically
> neglecting *%L.* Can anyone please have a look at this?
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Comment Edited] (LOG4J2-3417) Create JDBC appender for compatibility with v1
[
https://issues.apache.org/jira/browse/LOG4J2-3417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17498718#comment-17498718
]
Ralph Goers edited comment on LOG4J2-3417 at 2/28/22, 6:19 AM:
---
[~ggregory]
This was from our video chat today. Matt should have added a few more details.
The JdbcAppender in Log4j 2 can accept ColumnConfigs and/or ColumnMappings such
as:
{code:java}
{code}
It is obvious that the example query in the Javadoc for the Log4j 1 JdbcAppender
{code:java}
insert into LogTable (Thread, Class, Message) values ("%t", "%c", "%m") {code}
could be converted to:
{code:java}
{code}
Although it would be done using the JdbcAppenderBuilder in the log4j-1.2-api
module instead of via XML.
So the task here is to create a JdbcAppenderBuilder that creates the Log4j 2
JdbcAppender. So there is no requirement to use a prepared statement in the
builder, only to build a proper Log4j 2 JdbcAppender.
was (Author: ralph.go...@dslextreme.com):
[~ggregory]
This was from our video chat today. Matt should have added a few more details.
The JdbcAppender in Log4j 2 can accept ColumnConfigs and/or ColumnMappings such
as:
{code:java}
{code}
It is obvious that the example query in the Javadoc for the Log4j 1 JdbcAppender
{code:java}
insert into LogTable (Thread, Class, Message) values ("%t", "%c", "%m") {code}
could be converted to:
{code:java}
{code}
Although it would be done using the Appender's Builder instead of via XML.
So the task here is to create a JdbcAppenderBuilder that creates the Log4j 2
JdbcAppender. So there is no requirement to use a prepared statement in the
builder, only to build a proper Log4j 2 JdbcAppender.
> Create JDBC appender for compatibility with v1
> --
>
> Key: LOG4J2-3417
> URL: https://issues.apache.org/jira/browse/LOG4J2-3417
> Project: Log4j 2
> Issue Type: New Feature
> Components: Appenders, Log4j 1.2 bridge
>Reporter: Matt Sicker
>Priority: Major
>
> Log4j 1 had a JDBC appender which made it fairly simple to set up an appender
> to a database. While the old version doesn't work properly with modern
> security practices, it shouldn't be too hard to parse the configured SQL
> statement for pattern layout keys and extract them into a parameterized query.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Comment Edited] (LOG4J2-3417) Create JDBC appender for compatibility with v1
[
https://issues.apache.org/jira/browse/LOG4J2-3417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17498718#comment-17498718
]
Ralph Goers edited comment on LOG4J2-3417 at 2/28/22, 6:17 AM:
---
[~ggregory]
This was from our video chat today. Matt should have added a few more details.
The JdbcAppender in Log4j 2 can accept ColumnConfigs and/or ColumnMappings such
as:
{code:java}
{code}
It is obvious that the example query in the Javadoc for the Log4j 1 JdbcAppender
{code:java}
insert into LogTable (Thread, Class, Message) values ("%t", "%c", "%m") {code}
could be converted to:
{code:java}
{code}
Although it would be done using the Appender's Builder instead of via XML.
So the task here is to create a JdbcAppenderBuilder that creates the Log4j 2
JdbcAppender. So there is no requirement to use a prepared statement in the
builder, only to build a proper Log4j 2 JdbcAppender.
was (Author: ralph.go...@dslextreme.com):
[~ggregory]
This was from our video chat today. Matt should have added a few more details.
The JdbcAppender in Log4j 2 can accept ColumnConfigs and/or ColumnMappings such
as:
{code:java}
{code}
It is obvious that a query like:
{code:java}
insert into LogTable (Thread, Class, Message) values ("%t", "%c", "%m") {code}
could be converted to:
{code:java}
{code}
Although it would be done using the Appender's Builder instead of via XML.
So the task here is to create a JdbcAppenderBuilder that creates the Log4j 2
JdbcAppender. So there is no requirement to use a prepared statement in the
builder, only to build a proper Log4j 2 JdbcAppender.
> Create JDBC appender for compatibility with v1
> --
>
> Key: LOG4J2-3417
> URL: https://issues.apache.org/jira/browse/LOG4J2-3417
> Project: Log4j 2
> Issue Type: New Feature
> Components: Appenders, Log4j 1.2 bridge
>Reporter: Matt Sicker
>Priority: Major
>
> Log4j 1 had a JDBC appender which made it fairly simple to set up an appender
> to a database. While the old version doesn't work properly with modern
> security practices, it shouldn't be too hard to parse the configured SQL
> statement for pattern layout keys and extract them into a parameterized query.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Comment Edited] (LOG4J2-3417) Create JDBC appender for compatibility with v1
[
https://issues.apache.org/jira/browse/LOG4J2-3417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17498718#comment-17498718
]
Ralph Goers edited comment on LOG4J2-3417 at 2/28/22, 6:16 AM:
---
[~ggregory]
This was from our video chat today. Matt should have added a few more details.
The JdbcAppender in Log4j 2 can accept ColumnConfigs and/or ColumnMappings such
as:
{code:java}
{code}
It is obvious that a query like:
{code:java}
insert into LogTable (Thread, Class, Message) values ("%t", "%c", "%m") {code}
could be converted to:
{code:java}
{code}
Although it would be done using the Appender's Builder instead of via XML.
So the task here is to create a JdbcAppenderBuilder that creates the Log4j 2
JdbcAppender. So there is no requirement to use a prepared statement in the
builder, only to build a proper Log4j 2 JdbcAppender.
was (Author: ralph.go...@dslextreme.com):
[~ggregory]
This was from our video chat today. Matt should have added a few more details.
The JdbcAppender in Log4j 2 can accept ColumnConfigs and/or ColumnMappings such
as:
{code:java}
{code}
It is obvious that a query like:
{code:java}
insert into LogTable (Thread, Class, Message) values ("%t", "%c", "%m") {code}
could be converted to:
{code:java}
{code}
Although it would be done using the Appender's Builder.
So the task here is to create a JdbcAppenderBuilder that creates the Log4j 2
JdbcAppender. So there is no requirement to use a prepared statement in the
builder, only to build a proper Log4j 2 JdbcAppender.
> Create JDBC appender for compatibility with v1
> --
>
> Key: LOG4J2-3417
> URL: https://issues.apache.org/jira/browse/LOG4J2-3417
> Project: Log4j 2
> Issue Type: New Feature
> Components: Appenders, Log4j 1.2 bridge
>Reporter: Matt Sicker
>Priority: Major
>
> Log4j 1 had a JDBC appender which made it fairly simple to set up an appender
> to a database. While the old version doesn't work properly with modern
> security practices, it shouldn't be too hard to parse the configured SQL
> statement for pattern layout keys and extract them into a parameterized query.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (LOG4J2-3417) Create JDBC appender for compatibility with v1
[
https://issues.apache.org/jira/browse/LOG4J2-3417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17498718#comment-17498718
]
Ralph Goers commented on LOG4J2-3417:
-
[~ggregory]
This was from our video chat today. Matt should have added a few more details.
The JdbcAppender in Log4j 2 can accept ColumnConfigs and/or ColumnMappings such
as:
{code:java}
{code}
It is obvious that a query like:
{code:java}
insert into LogTable (Thread, Class, Message) values ("%t", "%c", "%m") {code}
could be converted to:
{code:java}
{code}
Although it would be done using the Appender's Builder.
So the task here is to create a JdbcAppenderBuilder that creates the Log4j 2
JdbcAppender. So there is no requirement to use a prepared statement in the
builder, only to build a proper Log4j 2 JdbcAppender.
> Create JDBC appender for compatibility with v1
> --
>
> Key: LOG4J2-3417
> URL: https://issues.apache.org/jira/browse/LOG4J2-3417
> Project: Log4j 2
> Issue Type: New Feature
> Components: Appenders, Log4j 1.2 bridge
>Reporter: Matt Sicker
>Priority: Major
>
> Log4j 1 had a JDBC appender which made it fairly simple to set up an appender
> to a database. While the old version doesn't work properly with modern
> security practices, it shouldn't be too hard to parse the configured SQL
> statement for pattern layout keys and extract them into a parameterized query.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[GitHub] [logging-log4j2] rgoers commented on pull request #775: [LOG4J2-3415] Support JSON configuration using embedded JSON parser
rgoers commented on pull request #775: URL: https://github.com/apache/logging-log4j2/pull/775#issuecomment-1053916356 @jvz You are correct. Accomplishing what I want to with Properties will be much simpler if the JsonReader is a utility class in the api module. I will absolutely need JSON support for that. But to be honest, I am not sure that PropertiesUtil really needs to be in the API. Or if we have one it could probably be greatly simplified since it controls only a very few system properties. -- 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] dependabot[bot] opened a new pull request #776: Bump slf4jVersion from 1.7.35 to 1.7.36
dependabot[bot] opened a new pull request #776: URL: https://github.com/apache/logging-log4j2/pull/776 Bumps `slf4jVersion` from 1.7.35 to 1.7.36. Updates `slf4j-api` from 1.7.35 to 1.7.36 Commits https://github.com/qos-ch/slf4j/commit/e9ee55cca93c2bf26f14482a9bdf961c750d2a56";>e9ee55c update timestamp before release https://github.com/qos-ch/slf4j/commit/3b6a92f66815605ce851671dd1d6e0758c29ed4c";>3b6a92f reproducible builds https://github.com/qos-ch/slf4j/commit/882502706063b460997a3c6018223018f36cecd3";>8825027 prepare release 1.7.36, fix SLF4J-541 https://github.com/qos-ch/slf4j/commit/561738747da5813b8a9d2e2ebd10f0128a78a960";>5617387 add relase.sh See full diff in https://github.com/qos-ch/slf4j/compare/v_1.7.35...v_1.7.36";>compare view Updates `slf4j-ext` from 1.7.35 to 1.7.36 Commits https://github.com/qos-ch/slf4j/commit/e9ee55cca93c2bf26f14482a9bdf961c750d2a56";>e9ee55c update timestamp before release https://github.com/qos-ch/slf4j/commit/3b6a92f66815605ce851671dd1d6e0758c29ed4c";>3b6a92f reproducible builds https://github.com/qos-ch/slf4j/commit/882502706063b460997a3c6018223018f36cecd3";>8825027 prepare release 1.7.36, fix SLF4J-541 https://github.com/qos-ch/slf4j/commit/561738747da5813b8a9d2e2ebd10f0128a78a960";>5617387 add relase.sh See full diff in https://github.com/qos-ch/slf4j/compare/v_1.7.35...v_1.7.36";>compare view Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -- 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-3417) Create JDBC appender for compatibility with v1
[
https://issues.apache.org/jira/browse/LOG4J2-3417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17498660#comment-17498660
]
Gary D. Gregory commented on LOG4J2-3417:
-
Internally the SQL for something like
log4j.appender.DB.sql=INSERT INTO LOGS VALUES('%x','%d','%C','%p','%m')
Should translate to
INSERT INTO LOGS VALUES(?, ?, ?, ?, ?)
It should be a requirement on our implementation to use JDBC a prepared
statement or callable statement for a stored procedure call.
> Create JDBC appender for compatibility with v1
> --
>
> Key: LOG4J2-3417
> URL: https://issues.apache.org/jira/browse/LOG4J2-3417
> Project: Log4j 2
> Issue Type: New Feature
> Components: Appenders, Log4j 1.2 bridge
>Reporter: Matt Sicker
>Priority: Major
>
> Log4j 1 had a JDBC appender which made it fairly simple to set up an appender
> to a database. While the old version doesn't work properly with modern
> security practices, it shouldn't be too hard to parse the configured SQL
> statement for pattern layout keys and extract them into a parameterized query.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (LOG4J2-3417) Create JDBC appender for compatibility with v1
Matt Sicker created LOG4J2-3417: --- Summary: Create JDBC appender for compatibility with v1 Key: LOG4J2-3417 URL: https://issues.apache.org/jira/browse/LOG4J2-3417 Project: Log4j 2 Issue Type: New Feature Components: Appenders, Log4j 1.2 bridge Reporter: Matt Sicker Log4j 1 had a JDBC appender which made it fairly simple to set up an appender to a database. While the old version doesn't work properly with modern security practices, it shouldn't be too hard to parse the configured SQL statement for pattern layout keys and extract them into a parameterized query. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[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=17498659#comment-17498659 ] Ralph Goers commented on LOG4J2-3413: - Log4j 2.17.2 was just released last night but did not include this fix. I would expect the next release would be 1 or 2 months out. > 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 > Fix For: 2.18.0 > > 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-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=17498642#comment-17498642 ] Sean Wang commented on LOG4J2-3413: --- Thank you very much for your quick response on this issue. Do you have an estimate how soon the fix would be in the next release or patch? Thanks again. Sean > 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 > Fix For: 2.18.0 > > 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] [Created] (LOG4J2-3416) Line Number Not getting printeed
Sagar Salal created LOG4J2-3416: --- Summary: Line Number Not getting printeed Key: LOG4J2-3416 URL: https://issues.apache.org/jira/browse/LOG4J2-3416 Project: Log4j 2 Issue Type: Bug Components: Appenders Affects Versions: 2.17.0 Reporter: Sagar Salal I am not able to print line numbers in logs. I am using 2.17.0 version and using pattern . I have tried with multiple patterns but issue still persists. It is basically neglecting *%L.* Can anyone please have a look at this? -- This message was sent by Atlassian Jira (v8.20.1#820001)
