[jira] [Commented] (LOG4J2-3432) RollingFileAppender fails after 100 backup cycles if filePattern contains "%04i" .
[
https://issues.apache.org/jira/browse/LOG4J2-3432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17506713#comment-17506713
]
Ralph Goers commented on LOG4J2-3432:
-
[~ggregory] if you had looked at the changes in 2.17.2 you’d see no changes in
this area. Asking a user to test a newer version with no documented changes is
inconsiderate as it is a waste of the reporters time. It does make sense to ask
when any changes have been made to related code on the off chance it somehow
got fixed.
> RollingFileAppender fails after 100 backup cycles if filePattern contains
> "%04i" .
> --
>
> Key: LOG4J2-3432
> URL: https://issues.apache.org/jira/browse/LOG4J2-3432
> Project: Log4j 2
> Issue Type: Bug
> Components: Appenders
>Affects Versions: 2.17.1, 2.17.2
> Environment: * Red Hat Enterprise Linux Server release 6.10 (Santiago)
> * java version "1.8.0_181"
> Java(TM) SE Runtime Environment (build 1.8.0_181-b13)
> Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode)
> * 301873 Mar 9 07:53 log4j-api-2.17.1.jar
> 1790452 Mar 9 07:53 log4j-core-2.17.1.jar
>
>Reporter: Carl Smotricz
>Assignee: Ralph Goers
>Priority: Major
> Attachments: Main.java, log4j2.xml, runit.sh
>
>
> If a {{%i}} formatter in a filePattern includes a width specifier, e.g. "%4i"
> or "%04i", file renaming fails after a certain fixed number of cycles. After
> that, successive backups are renamed to the maximum cycle number and
> overwrite previous files of that same cycle number, regardless of min and max
> settings on the appender. Here are some failure modes I've found by testing:
> * if {{filePattern}} contains {{{}%06i{}}}, cycling breaks after 100.
> * if {{filePattern}} contains {{{}%006i{}}}, it breaks after 100 also.
> * if {{filePattern}} contains {{{}%6i{}}}, it breaks after 10.
> * if {{filePattern}} contains {{%06i}} and
> {{{}DefaultRolloverStrategy.min{}}}=1, {{{}max{}}}=9, it breaks after
> just 1.
> Now, the doc doesn't mention the %i spec supporting width and leading zero
> modifiers in the manner of printf() or String.format() . Yet, those
> variations (which I think other users will also be tempted to try) work -
> until they don't. So apparently width and padding on that spec are
> implemented but buggy.
> The doc for RollingRandomAccessFileAppender explicitly recommends these
> format modifiers:
> {quote}... and/or a %i which represents an integer counter. The integer
> counter allows specifying a padding, like %3i for space-padding the counter
> to 3 digits or (usually more useful) %03i for zero-padding the counter to 3
> digits.
> {quote}
> ...but I haven't verified that the problem occurs with that appender as well.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[GitHub] [logging-log4j2] dependabot[bot] opened a new pull request #796: Bump maven-pdf-plugin from 1.2 to 1.5.1
dependabot[bot] opened a new pull request #796: URL: https://github.com/apache/logging-log4j2/pull/796 Bumps [maven-pdf-plugin](https://github.com/apache/maven-pdf-plugin) from 1.2 to 1.5.1. Commits https://github.com/apache/maven-pdf-plugin/commit/441090ffb4d0303c6e12c2c15cee9b6dc523f8ee;>441090f [maven-release-plugin] prepare release maven-pdf-plugin-1.5.1 https://github.com/apache/maven-pdf-plugin/commit/286dcb19016670e0788cfda674b2017363ec9f32;>286dcb1 [MPDF-99] Add workaround for MPOM-269 https://github.com/apache/maven-pdf-plugin/commit/57d1d326c2975f2c6462c170e6d8e99b6f731169;>57d1d32 Fix Javadoc errors https://github.com/apache/maven-pdf-plugin/commit/25092697a7d58df184ebb13e42766c25a9efa7cb;>2509269 [maven-release-plugin] prepare for next development iteration https://github.com/apache/maven-pdf-plugin/commit/f7d939998f3295a22b77bb1e233958b21ffb4990;>f7d9399 [maven-release-plugin] prepare release maven-pdf-plugin-1.5.0 https://github.com/apache/maven-pdf-plugin/commit/dc212c4ddfe713d6a8565bb84011215e1b042537;>dc212c4 Small pom cleanups https://github.com/apache/maven-pdf-plugin/commit/4cbd850407c228a60fb03d51a043a02f772dff37;>4cbd850 Fix failing tests with new plexus-utils https://github.com/apache/maven-pdf-plugin/commit/0ab56936f109b0a7f6eaddb63283e06581278dd1;>0ab5693 Update CI config https://github.com/apache/maven-pdf-plugin/commit/392b08bb6cd763a4f3cc443167fd5f44a12f97db;>392b08b Bump actions/setup-java from 2.3.0 to 2.3.1 https://github.com/apache/maven-pdf-plugin/commit/55893344db2309f549bb1542d60c73afbf9c27aa;>5589334 Bump JSONUtil from 1.10.2-java6 to 1.10.4-java6 Additional commits viewable in https://github.com/apache/maven-pdf-plugin/compare/maven-pdf-plugin-1.2...maven-pdf-plugin-1.5.1;>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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
[GitHub] [logging-log4j2] dependabot[bot] opened a new pull request #795: Bump maven-pmd-plugin from 3.10.0 to 3.16.0
dependabot[bot] opened a new pull request #795: URL: https://github.com/apache/logging-log4j2/pull/795 Bumps [maven-pmd-plugin](https://github.com/apache/maven-pmd-plugin) from 3.10.0 to 3.16.0. Release notes Sourced from https://github.com/apache/maven-pmd-plugin/releases;>maven-pmd-plugin's releases. 3.16.0 Bug Fixes https://issues.apache.org/jira/browse/MPMD-325;>[MPMD-325] Could not find class due to IncompatibleClassChangeError warning https://issues.apache.org/jira/browse/MPMD-324;>[MPMD-324] Ruleset URLs have hyphen replaced with forwardslash https://issues.apache.org/jira/browse/MPMD-323;>[MPMD-323] ResourceManager should use project base dir instead of pom location Build https://issues.apache.org/jira/browse/MPMD-328;>[MPMD-328] Shared GitHub Actions New features and improvements https://issues.apache.org/jira/browse/MPMD-327;>[MPMD-327] Upgrade to PMD 6.42.0 Dependency updates https://issues.apache.org/jira/browse/MPMD-326;>[MPMD-326] Set Maven 3.1.1 as minimum version Commits https://github.com/apache/maven-pmd-plugin/commit/b8a794e37e4cb3bb986ce044f3ef8df0dd392ed1;>b8a794e [maven-release-plugin] prepare release maven-pmd-plugin-3.16.0 https://github.com/apache/maven-pmd-plugin/commit/6fc39ec2428a9fd68319da39f89d2191ac3ad25b;>6fc39ec [MPMD-323] ResourceManager should use project base dir instead of pom https://github.com/apache/maven-pmd-plugin/commit/4eae72c6c6f394c0c65fc4994eead9d06a6544f2;>4eae72c [MPMD-324] Ruleset URLs have hyphen replaced with forwardslash https://github.com/apache/maven-pmd-plugin/commit/64e35f73c27107c192b33b856f549fa66953b305;>64e35f7 Make maven core provided scope https://github.com/apache/maven-pmd-plugin/commit/1dd8d0007fcf5d48571b9483bd3865a57d8e5383;>1dd8d00 [MPMD-327] Upgrade to PMD 6.42.0 https://github.com/apache/maven-pmd-plugin/commit/fae45251df926bb2e91ac14914b374c5f0ed28ed;>fae4525 [MPMD-327] Upgrade to PMD 6.41.0 https://github.com/apache/maven-pmd-plugin/commit/80e8aabe537063ddb64887c4dc18ca6c91be19e8;>80e8aab (doc) Update README.md https://github.com/apache/maven-pmd-plugin/commit/3fffd9cc7c0bea9ddd8489c9a7b4fee264d2d2c0;>3fffd9c [MPMD-328] Shared Github Actions (https://github-redirect.dependabot.com/apache/maven-pmd-plugin/issues/48;>#48) https://github.com/apache/maven-pmd-plugin/commit/2175d5e3936d0f4718da6f890a442cfc60cd617e;>2175d5e [MPMD-327] Upgrade to PMD 6.40.0 https://github.com/apache/maven-pmd-plugin/commit/b8ac1fbc41b2b7e69bb6d8c0a336119e8fdd2d26;>b8ac1fb [MPMD-327] Upgrade to PMD 6.39.0 Additional commits viewable in https://github.com/apache/maven-pmd-plugin/compare/maven-pmd-plugin-3.10.0...maven-pmd-plugin-3.16.0;>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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:
[jira] [Commented] (LOG4J2-3432) RollingFileAppender fails after 100 backup cycles if filePattern contains "%04i" .
[
https://issues.apache.org/jira/browse/LOG4J2-3432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17506621#comment-17506621
]
Gary D. Gregory commented on LOG4J2-3432:
-
I asked because the current version should be the baseline for fixing bugs or
improving documentation.
> RollingFileAppender fails after 100 backup cycles if filePattern contains
> "%04i" .
> --
>
> Key: LOG4J2-3432
> URL: https://issues.apache.org/jira/browse/LOG4J2-3432
> Project: Log4j 2
> Issue Type: Bug
> Components: Appenders
>Affects Versions: 2.17.1, 2.17.2
> Environment: * Red Hat Enterprise Linux Server release 6.10 (Santiago)
> * java version "1.8.0_181"
> Java(TM) SE Runtime Environment (build 1.8.0_181-b13)
> Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode)
> * 301873 Mar 9 07:53 log4j-api-2.17.1.jar
> 1790452 Mar 9 07:53 log4j-core-2.17.1.jar
>
>Reporter: Carl Smotricz
>Assignee: Ralph Goers
>Priority: Major
> Attachments: Main.java, log4j2.xml, runit.sh
>
>
> If a {{%i}} formatter in a filePattern includes a width specifier, e.g. "%4i"
> or "%04i", file renaming fails after a certain fixed number of cycles. After
> that, successive backups are renamed to the maximum cycle number and
> overwrite previous files of that same cycle number, regardless of min and max
> settings on the appender. Here are some failure modes I've found by testing:
> * if {{filePattern}} contains {{{}%06i{}}}, cycling breaks after 100.
> * if {{filePattern}} contains {{{}%006i{}}}, it breaks after 100 also.
> * if {{filePattern}} contains {{{}%6i{}}}, it breaks after 10.
> * if {{filePattern}} contains {{%06i}} and
> {{{}DefaultRolloverStrategy.min{}}}=1, {{{}max{}}}=9, it breaks after
> just 1.
> Now, the doc doesn't mention the %i spec supporting width and leading zero
> modifiers in the manner of printf() or String.format() . Yet, those
> variations (which I think other users will also be tempted to try) work -
> until they don't. So apparently width and padding on that spec are
> implemented but buggy.
> The doc for RollingRandomAccessFileAppender explicitly recommends these
> format modifiers:
> {quote}... and/or a %i which represents an integer counter. The integer
> counter allows specifying a padding, like %3i for space-padding the counter
> to 3 digits or (usually more useful) %03i for zero-padding the counter to 3
> digits.
> {quote}
> ...but I haven't verified that the problem occurs with that appender as well.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Assigned] (LOG4J2-3432) RollingFileAppender fails after 100 backup cycles if filePattern contains "%04i" .
[
https://issues.apache.org/jira/browse/LOG4J2-3432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers reassigned LOG4J2-3432:
---
Assignee: Ralph Goers
> RollingFileAppender fails after 100 backup cycles if filePattern contains
> "%04i" .
> --
>
> Key: LOG4J2-3432
> URL: https://issues.apache.org/jira/browse/LOG4J2-3432
> Project: Log4j 2
> Issue Type: Bug
> Components: Appenders
>Affects Versions: 2.17.1, 2.17.2
> Environment: * Red Hat Enterprise Linux Server release 6.10 (Santiago)
> * java version "1.8.0_181"
> Java(TM) SE Runtime Environment (build 1.8.0_181-b13)
> Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode)
> * 301873 Mar 9 07:53 log4j-api-2.17.1.jar
> 1790452 Mar 9 07:53 log4j-core-2.17.1.jar
>
>Reporter: Carl Smotricz
>Assignee: Ralph Goers
>Priority: Major
> Attachments: Main.java, log4j2.xml, runit.sh
>
>
> If a {{%i}} formatter in a filePattern includes a width specifier, e.g. "%4i"
> or "%04i", file renaming fails after a certain fixed number of cycles. After
> that, successive backups are renamed to the maximum cycle number and
> overwrite previous files of that same cycle number, regardless of min and max
> settings on the appender. Here are some failure modes I've found by testing:
> * if {{filePattern}} contains {{{}%06i{}}}, cycling breaks after 100.
> * if {{filePattern}} contains {{{}%006i{}}}, it breaks after 100 also.
> * if {{filePattern}} contains {{{}%6i{}}}, it breaks after 10.
> * if {{filePattern}} contains {{%06i}} and
> {{{}DefaultRolloverStrategy.min{}}}=1, {{{}max{}}}=9, it breaks after
> just 1.
> Now, the doc doesn't mention the %i spec supporting width and leading zero
> modifiers in the manner of printf() or String.format() . Yet, those
> variations (which I think other users will also be tempted to try) work -
> until they don't. So apparently width and padding on that spec are
> implemented but buggy.
> The doc for RollingRandomAccessFileAppender explicitly recommends these
> format modifiers:
> {quote}... and/or a %i which represents an integer counter. The integer
> counter allows specifying a padding, like %3i for space-padding the counter
> to 3 digits or (usually more useful) %03i for zero-padding the counter to 3
> digits.
> {quote}
> ...but I haven't verified that the problem occurs with that appender as well.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (LOG4J2-3432) RollingFileAppender fails after 100 backup cycles if filePattern contains "%04i" .
[
https://issues.apache.org/jira/browse/LOG4J2-3432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17506594#comment-17506594
]
Ralph Goers commented on LOG4J2-3432:
-
I'm not surprised. I don't believe we made any changes to the Rolling Appenders
in 2.17.1 so I'm not sure why Gary asked you to test it. Assigning this to
myself as I typically work on these kinds of issues but that isn't a guarantee
that I will get to it quickly.
> RollingFileAppender fails after 100 backup cycles if filePattern contains
> "%04i" .
> --
>
> Key: LOG4J2-3432
> URL: https://issues.apache.org/jira/browse/LOG4J2-3432
> Project: Log4j 2
> Issue Type: Bug
> Components: Appenders
>Affects Versions: 2.17.1, 2.17.2
> Environment: * Red Hat Enterprise Linux Server release 6.10 (Santiago)
> * java version "1.8.0_181"
> Java(TM) SE Runtime Environment (build 1.8.0_181-b13)
> Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode)
> * 301873 Mar 9 07:53 log4j-api-2.17.1.jar
> 1790452 Mar 9 07:53 log4j-core-2.17.1.jar
>
>Reporter: Carl Smotricz
>Priority: Major
> Attachments: Main.java, log4j2.xml, runit.sh
>
>
> If a {{%i}} formatter in a filePattern includes a width specifier, e.g. "%4i"
> or "%04i", file renaming fails after a certain fixed number of cycles. After
> that, successive backups are renamed to the maximum cycle number and
> overwrite previous files of that same cycle number, regardless of min and max
> settings on the appender. Here are some failure modes I've found by testing:
> * if {{filePattern}} contains {{{}%06i{}}}, cycling breaks after 100.
> * if {{filePattern}} contains {{{}%006i{}}}, it breaks after 100 also.
> * if {{filePattern}} contains {{{}%6i{}}}, it breaks after 10.
> * if {{filePattern}} contains {{%06i}} and
> {{{}DefaultRolloverStrategy.min{}}}=1, {{{}max{}}}=9, it breaks after
> just 1.
> Now, the doc doesn't mention the %i spec supporting width and leading zero
> modifiers in the manner of printf() or String.format() . Yet, those
> variations (which I think other users will also be tempted to try) work -
> until they don't. So apparently width and padding on that spec are
> implemented but buggy.
> The doc for RollingRandomAccessFileAppender explicitly recommends these
> format modifiers:
> {quote}... and/or a %i which represents an integer counter. The integer
> counter allows specifying a padding, like %3i for space-padding the counter
> to 3 digits or (usually more useful) %03i for zero-padding the counter to 3
> digits.
> {quote}
> ...but I haven't verified that the problem occurs with that appender as well.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (LOG4J2-3416) Line Number Not getting printed in log file
[
https://issues.apache.org/jira/browse/LOG4J2-3416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17506591#comment-17506591
]
Ralph Goers commented on LOG4J2-3416:
-
I have a suspicion this is related to
[https://bz.apache.org/bugzilla/show_bug.cgi?id=61601] which indicates the
version you are using doesn't support multi-release jars, but I can't be sure.
I'm also not sure why the result would be what you are seeing. With that, the
result should be a failure when running in a JDK > 8, not a failure with Java
8. Without a test that fails for you though we are just guessing.
> Line Number Not getting printed in log file
> ---
>
> 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
> Attachments: log4j2.xml
>
>
> 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)
[GitHub] [logging-log4j2] ppkarwasz commented on pull request #794: [LOG4J2-3419] Add a Log4j 1.x level name pattern converter
ppkarwasz commented on pull request #794: URL: https://github.com/apache/logging-log4j2/pull/794#issuecomment-1067347143 @garydgregory, it's rather used internally. For custom Log4j 1.x levels it will give the level name without the class name suffix. For custom Log4j 2.x levels it should give the same result as `%p`. -- 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-3393) JSON template layout performance regression
[
https://issues.apache.org/jira/browse/LOG4J2-3393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17506555#comment-17506555
]
ASF subversion and git services commented on LOG4J2-3393:
-
Commit aaef74c3c9fa18dda4dd4b3b15769cacdf219cb1 in logging-log4j2's branch
refs/heads/LOG4J2-3393 from Volkan Yazici
[ https://gitbox.apache.org/repos/asf?p=logging-log4j2.git;h=aaef74c ]
LOG4J2-3393 Make JsonWriter garbage-free for StringMaps.
> JSON template layout performance regression
> ---
>
> Key: LOG4J2-3393
> URL: https://issues.apache.org/jira/browse/LOG4J2-3393
> Project: Log4j 2
> Issue Type: Improvement
> Components: JsonTemplateLayout
>Affects Versions: 2.17.1
>Reporter: Volkan Yazici
>Assignee: Volkan Yazici
>Priority: Major
>
> JTL performance is used to be on par with \{{log4j2-ecs-layout}}, though this
> is not the case anymore, there is a slight degradation. This story aims to
> investigate what is going on and fix it.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (LOG4J2-3393) JSON template layout performance regression
[
https://issues.apache.org/jira/browse/LOG4J2-3393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17506559#comment-17506559
]
ASF subversion and git services commented on LOG4J2-3393:
-
Commit 51e5112235cf25a8f965df5a2f763219dbf9c24a in logging-log4j2's branch
refs/heads/LOG4J2-3393 from Volkan Yazici
[ https://gitbox.apache.org/repos/asf?p=logging-log4j2.git;h=51e5112 ]
LOG4J2-3393 Clean up LcsLayout and all other mess.
> JSON template layout performance regression
> ---
>
> Key: LOG4J2-3393
> URL: https://issues.apache.org/jira/browse/LOG4J2-3393
> Project: Log4j 2
> Issue Type: Improvement
> Components: JsonTemplateLayout
>Affects Versions: 2.17.1
>Reporter: Volkan Yazici
>Assignee: Volkan Yazici
>Priority: Major
>
> JTL performance is used to be on par with \{{log4j2-ecs-layout}}, though this
> is not the case anymore, there is a slight degradation. This story aims to
> investigate what is going on and fix it.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (LOG4J2-3393) JSON template layout performance regression
[
https://issues.apache.org/jira/browse/LOG4J2-3393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17506551#comment-17506551
]
ASF subversion and git services commented on LOG4J2-3393:
-
Commit 8fdbe5cb0eed7e3e12b97406482da838b93cd074 in logging-log4j2's branch
refs/heads/LOG4J2-3393 from Volkan Yazici
[ https://gitbox.apache.org/repos/asf?p=logging-log4j2.git;h=8fdbe5c ]
LOG4J2-3393 Remove redundant branching in JsonTemplateLayout.
> JSON template layout performance regression
> ---
>
> Key: LOG4J2-3393
> URL: https://issues.apache.org/jira/browse/LOG4J2-3393
> Project: Log4j 2
> Issue Type: Improvement
> Components: JsonTemplateLayout
>Affects Versions: 2.17.1
>Reporter: Volkan Yazici
>Assignee: Volkan Yazici
>Priority: Major
>
> JTL performance is used to be on par with \{{log4j2-ecs-layout}}, though this
> is not the case anymore, there is a slight degradation. This story aims to
> investigate what is going on and fix it.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (LOG4J2-3393) JSON template layout performance regression
[
https://issues.apache.org/jira/browse/LOG4J2-3393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17506557#comment-17506557
]
ASF subversion and git services commented on LOG4J2-3393:
-
Commit 16950442c0aef219dc23dde6fed2e0c91396f4da in logging-log4j2's branch
refs/heads/LOG4J2-3393 from Volkan Yazici
[ https://gitbox.apache.org/repos/asf?p=logging-log4j2.git;h=1695044 ]
LOG4J2-3393 Fix revapi issues.
> JSON template layout performance regression
> ---
>
> Key: LOG4J2-3393
> URL: https://issues.apache.org/jira/browse/LOG4J2-3393
> Project: Log4j 2
> Issue Type: Improvement
> Components: JsonTemplateLayout
>Affects Versions: 2.17.1
>Reporter: Volkan Yazici
>Assignee: Volkan Yazici
>Priority: Major
>
> JTL performance is used to be on par with \{{log4j2-ecs-layout}}, though this
> is not the case anymore, there is a slight degradation. This story aims to
> investigate what is going on and fix it.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (LOG4J2-3393) JSON template layout performance regression
[
https://issues.apache.org/jira/browse/LOG4J2-3393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17506549#comment-17506549
]
ASF subversion and git services commented on LOG4J2-3393:
-
Commit 9ecef909bbeac678f000365e802800db7e2fa08d in logging-log4j2's branch
refs/heads/LOG4J2-3393 from Volkan Yazici
[ https://gitbox.apache.org/repos/asf?p=logging-log4j2.git;h=9ecef90 ]
LOG4J2-3393 Clean up LcsLayout and all other mess.
> JSON template layout performance regression
> ---
>
> Key: LOG4J2-3393
> URL: https://issues.apache.org/jira/browse/LOG4J2-3393
> Project: Log4j 2
> Issue Type: Improvement
> Components: JsonTemplateLayout
>Affects Versions: 2.17.1
>Reporter: Volkan Yazici
>Assignee: Volkan Yazici
>Priority: Major
>
> JTL performance is used to be on par with \{{log4j2-ecs-layout}}, though this
> is not the case anymore, there is a slight degradation. This story aims to
> investigate what is going on and fix it.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (LOG4J2-3393) JSON template layout performance regression
[
https://issues.apache.org/jira/browse/LOG4J2-3393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17506552#comment-17506552
]
ASF subversion and git services commented on LOG4J2-3393:
-
Commit f5b172e9b4525042b3205e3d3b0fafb803f9a419 in logging-log4j2's branch
refs/heads/LOG4J2-3393 from Volkan Yazici
[ https://gitbox.apache.org/repos/asf?p=logging-log4j2.git;h=f5b172e ]
LOG4J2-3393 Inline context acquisition in JsonTemplateLayout.
> JSON template layout performance regression
> ---
>
> Key: LOG4J2-3393
> URL: https://issues.apache.org/jira/browse/LOG4J2-3393
> Project: Log4j 2
> Issue Type: Improvement
> Components: JsonTemplateLayout
>Affects Versions: 2.17.1
>Reporter: Volkan Yazici
>Assignee: Volkan Yazici
>Priority: Major
>
> JTL performance is used to be on par with \{{log4j2-ecs-layout}}, though this
> is not the case anymore, there is a slight degradation. This story aims to
> investigate what is going on and fix it.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (LOG4J2-3393) JSON template layout performance regression
[
https://issues.apache.org/jira/browse/LOG4J2-3393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17506556#comment-17506556
]
ASF subversion and git services commented on LOG4J2-3393:
-
Commit 04a8214215471f0f4c74410904e4a161f6f6fdb6 in logging-log4j2's branch
refs/heads/LOG4J2-3393 from Volkan Yazici
[ https://gitbox.apache.org/repos/asf?p=logging-log4j2.git;h=04a8214 ]
LOG4J2-3393 Clean-up wrong BiConsumer usages.
> JSON template layout performance regression
> ---
>
> Key: LOG4J2-3393
> URL: https://issues.apache.org/jira/browse/LOG4J2-3393
> Project: Log4j 2
> Issue Type: Improvement
> Components: JsonTemplateLayout
>Affects Versions: 2.17.1
>Reporter: Volkan Yazici
>Assignee: Volkan Yazici
>Priority: Major
>
> JTL performance is used to be on par with \{{log4j2-ecs-layout}}, though this
> is not the case anymore, there is a slight degradation. This story aims to
> investigate what is going on and fix it.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (LOG4J2-3393) JSON template layout performance regression
[
https://issues.apache.org/jira/browse/LOG4J2-3393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17506558#comment-17506558
]
ASF subversion and git services commented on LOG4J2-3393:
-
Commit fcf85c7cc46bbfc1e7c972a4d37d8b34c5e03af2 in logging-log4j2's branch
refs/heads/LOG4J2-3393 from Volkan Yazici
[ https://gitbox.apache.org/repos/asf?p=logging-log4j2.git;h=fcf85c7 ]
LOG4J2-3393 Optimize MessageResolver for CharSequence.
> JSON template layout performance regression
> ---
>
> Key: LOG4J2-3393
> URL: https://issues.apache.org/jira/browse/LOG4J2-3393
> Project: Log4j 2
> Issue Type: Improvement
> Components: JsonTemplateLayout
>Affects Versions: 2.17.1
>Reporter: Volkan Yazici
>Assignee: Volkan Yazici
>Priority: Major
>
> JTL performance is used to be on par with \{{log4j2-ecs-layout}}, though this
> is not the case anymore, there is a slight degradation. This story aims to
> investigate what is going on and fix it.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (LOG4J2-3393) JSON template layout performance regression
[
https://issues.apache.org/jira/browse/LOG4J2-3393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17506550#comment-17506550
]
ASF subversion and git services commented on LOG4J2-3393:
-
Commit 8b12d69e2afb393a7360dbedc70dc9238fabc021 in logging-log4j2's branch
refs/heads/LOG4J2-3393 from Volkan Yazici
[ https://gitbox.apache.org/repos/asf?p=logging-log4j2.git;h=8b12d69 ]
LOG4J2-3393 Avoid StringBuilderEncoder thread-local allocation in
JsonTemplateLayout.
> JSON template layout performance regression
> ---
>
> Key: LOG4J2-3393
> URL: https://issues.apache.org/jira/browse/LOG4J2-3393
> Project: Log4j 2
> Issue Type: Improvement
> Components: JsonTemplateLayout
>Affects Versions: 2.17.1
>Reporter: Volkan Yazici
>Assignee: Volkan Yazici
>Priority: Major
>
> JTL performance is used to be on par with \{{log4j2-ecs-layout}}, though this
> is not the case anymore, there is a slight degradation. This story aims to
> investigate what is going on and fix it.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (LOG4J2-3393) JSON template layout performance regression
[
https://issues.apache.org/jira/browse/LOG4J2-3393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17506553#comment-17506553
]
ASF subversion and git services commented on LOG4J2-3393:
-
Commit 041dd8a23b7cd53a3f5f0833f4fbdf3ffe60255a in logging-log4j2's branch
refs/heads/LOG4J2-3393 from Volkan Yazici
[ https://gitbox.apache.org/repos/asf?p=logging-log4j2.git;h=041dd8a ]
LOG4J2-3393 JTL benchmark updates.
> JSON template layout performance regression
> ---
>
> Key: LOG4J2-3393
> URL: https://issues.apache.org/jira/browse/LOG4J2-3393
> Project: Log4j 2
> Issue Type: Improvement
> Components: JsonTemplateLayout
>Affects Versions: 2.17.1
>Reporter: Volkan Yazici
>Assignee: Volkan Yazici
>Priority: Major
>
> JTL performance is used to be on par with \{{log4j2-ecs-layout}}, though this
> is not the case anymore, there is a slight degradation. This story aims to
> investigate what is going on and fix it.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (LOG4J2-3393) JSON template layout performance regression
[
https://issues.apache.org/jira/browse/LOG4J2-3393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17506554#comment-17506554
]
ASF subversion and git services commented on LOG4J2-3393:
-
Commit 0ada37170dbfc9d1845cf3ba4a99c94ce41d1fe9 in logging-log4j2's branch
refs/heads/LOG4J2-3393 from Volkan Yazici
[ https://gitbox.apache.org/repos/asf?p=logging-log4j2.git;h=0ada371 ]
LOG4J2-3393 Make TextEncoderHelper.encodeText() fallbacks JIT-friendly.
> JSON template layout performance regression
> ---
>
> Key: LOG4J2-3393
> URL: https://issues.apache.org/jira/browse/LOG4J2-3393
> Project: Log4j 2
> Issue Type: Improvement
> Components: JsonTemplateLayout
>Affects Versions: 2.17.1
>Reporter: Volkan Yazici
>Assignee: Volkan Yazici
>Priority: Major
>
> JTL performance is used to be on par with \{{log4j2-ecs-layout}}, though this
> is not the case anymore, there is a slight degradation. This story aims to
> investigate what is going on and fix it.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[GitHub] [logging-log4j2] ppkarwasz opened a new pull request #794: [LOG4J2-3419] Add a Log4j 1.x level name pattern converter
ppkarwasz opened a new pull request #794: URL: https://github.com/apache/logging-log4j2/pull/794 When custom levels are in play the names of Log4j 1.x custom levels (which are not unique) and those of Log4j 2.x custom levels (which must be unique) do not match. There is a need therefore for a pattern converter specific to Log4j 1.x. -- 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] [Updated] (LOG4J2-3432) RollingFileAppender fails after 100 backup cycles if filePattern contains "%04i" .
[
https://issues.apache.org/jira/browse/LOG4J2-3432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carl Smotricz updated LOG4J2-3432:
--
Affects Version/s: 2.17.2
> RollingFileAppender fails after 100 backup cycles if filePattern contains
> "%04i" .
> --
>
> Key: LOG4J2-3432
> URL: https://issues.apache.org/jira/browse/LOG4J2-3432
> Project: Log4j 2
> Issue Type: Bug
> Components: Appenders
>Affects Versions: 2.17.1, 2.17.2
> Environment: * Red Hat Enterprise Linux Server release 6.10 (Santiago)
> * java version "1.8.0_181"
> Java(TM) SE Runtime Environment (build 1.8.0_181-b13)
> Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode)
> * 301873 Mar 9 07:53 log4j-api-2.17.1.jar
> 1790452 Mar 9 07:53 log4j-core-2.17.1.jar
>
>Reporter: Carl Smotricz
>Priority: Major
> Attachments: Main.java, log4j2.xml, runit.sh
>
>
> If a {{%i}} formatter in a filePattern includes a width specifier, e.g. "%4i"
> or "%04i", file renaming fails after a certain fixed number of cycles. After
> that, successive backups are renamed to the maximum cycle number and
> overwrite previous files of that same cycle number, regardless of min and max
> settings on the appender. Here are some failure modes I've found by testing:
> * if {{filePattern}} contains {{{}%06i{}}}, cycling breaks after 100.
> * if {{filePattern}} contains {{{}%006i{}}}, it breaks after 100 also.
> * if {{filePattern}} contains {{{}%6i{}}}, it breaks after 10.
> * if {{filePattern}} contains {{%06i}} and
> {{{}DefaultRolloverStrategy.min{}}}=1, {{{}max{}}}=9, it breaks after
> just 1.
> Now, the doc doesn't mention the %i spec supporting width and leading zero
> modifiers in the manner of printf() or String.format() . Yet, those
> variations (which I think other users will also be tempted to try) work -
> until they don't. So apparently width and padding on that spec are
> implemented but buggy.
> The doc for RollingRandomAccessFileAppender explicitly recommends these
> format modifiers:
> {quote}... and/or a %i which represents an integer counter. The integer
> counter allows specifying a padding, like %3i for space-padding the counter
> to 3 digits or (usually more useful) %03i for zero-padding the counter to 3
> digits.
> {quote}
> ...but I haven't verified that the problem occurs with that appender as well.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (LOG4J2-3416) Line Number Not getting printed in log file
[
https://issues.apache.org/jira/browse/LOG4J2-3416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17506329#comment-17506329
]
Sagar Salal commented on LOG4J2-3416:
-
[~rgoers] [~vy] We are using jars provided by you fetched via maven.
Java Version : 1.8
Tomcat version : 8.0.33
Logging has been impacted after changing version to 2.15 and then to 2.17.2.
Earlier we were using 2.5, now also if I change the version to 2.5 it is
working fine, printing line number and method.
> Line Number Not getting printed in log file
> ---
>
> 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
> Attachments: log4j2.xml
>
>
> 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 printed in log file
[
https://issues.apache.org/jira/browse/LOG4J2-3416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17506309#comment-17506309
]
Ralph Goers commented on LOG4J2-3416:
-
See [https://logging.apache.org/log4j/2.x/manual/async.html#AllAsync] for
information on how async logging is enabled for all loggers. Since Volkan has
already attempted to replicate this and failed I am going to have to ask you to
create a sample program that illustrates the problem.
Also, what Java version are you using? Are you using the log4j-jars as provided
by us or are you "shading" them. I am guessing you are using Tomcat. If so,
what version is it?
> Line Number Not getting printed in log file
> ---
>
> 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
> Attachments: log4j2.xml
>
>
> 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-3393) JSON template layout performance regression
[
https://issues.apache.org/jira/browse/LOG4J2-3393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17506209#comment-17506209
]
ASF subversion and git services commented on LOG4J2-3393:
-
Commit 970e80e15688a79df46de78e7207699414159b63 in logging-log4j2's branch
refs/heads/LOG4J2-3393 from Volkan Yazici
[ https://gitbox.apache.org/repos/asf?p=logging-log4j2.git;h=970e80e ]
LOG4J2-3393 Remove redundant branching in JsonTemplateLayout.
> JSON template layout performance regression
> ---
>
> Key: LOG4J2-3393
> URL: https://issues.apache.org/jira/browse/LOG4J2-3393
> Project: Log4j 2
> Issue Type: Improvement
> Components: JsonTemplateLayout
>Affects Versions: 2.17.1
>Reporter: Volkan Yazici
>Assignee: Volkan Yazici
>Priority: Major
>
> JTL performance is used to be on par with \{{log4j2-ecs-layout}}, though this
> is not the case anymore, there is a slight degradation. This story aims to
> investigate what is going on and fix it.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (LOG4J2-3393) JSON template layout performance regression
[
https://issues.apache.org/jira/browse/LOG4J2-3393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17506211#comment-17506211
]
ASF subversion and git services commented on LOG4J2-3393:
-
Commit 8a48540001c53e8a9a4166c37d54480baaf05ad9 in logging-log4j2's branch
refs/heads/LOG4J2-3393 from Volkan Yazici
[ https://gitbox.apache.org/repos/asf?p=logging-log4j2.git;h=8a48540 ]
LOG4J2-3393 JTL benchmark updates.
> JSON template layout performance regression
> ---
>
> Key: LOG4J2-3393
> URL: https://issues.apache.org/jira/browse/LOG4J2-3393
> Project: Log4j 2
> Issue Type: Improvement
> Components: JsonTemplateLayout
>Affects Versions: 2.17.1
>Reporter: Volkan Yazici
>Assignee: Volkan Yazici
>Priority: Major
>
> JTL performance is used to be on par with \{{log4j2-ecs-layout}}, though this
> is not the case anymore, there is a slight degradation. This story aims to
> investigate what is going on and fix it.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (LOG4J2-3393) JSON template layout performance regression
[
https://issues.apache.org/jira/browse/LOG4J2-3393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17506213#comment-17506213
]
ASF subversion and git services commented on LOG4J2-3393:
-
Commit 6a19108e8100f0ba272d70368efba16f17d9432d in logging-log4j2's branch
refs/heads/LOG4J2-3393 from Volkan Yazici
[ https://gitbox.apache.org/repos/asf?p=logging-log4j2.git;h=6a19108 ]
LOG4J2-3393 Make JsonWriter garbage-free for StringMaps.
> JSON template layout performance regression
> ---
>
> Key: LOG4J2-3393
> URL: https://issues.apache.org/jira/browse/LOG4J2-3393
> Project: Log4j 2
> Issue Type: Improvement
> Components: JsonTemplateLayout
>Affects Versions: 2.17.1
>Reporter: Volkan Yazici
>Assignee: Volkan Yazici
>Priority: Major
>
> JTL performance is used to be on par with \{{log4j2-ecs-layout}}, though this
> is not the case anymore, there is a slight degradation. This story aims to
> investigate what is going on and fix it.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (LOG4J2-3393) JSON template layout performance regression
[
https://issues.apache.org/jira/browse/LOG4J2-3393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17506208#comment-17506208
]
ASF subversion and git services commented on LOG4J2-3393:
-
Commit 264ae844ed6fcb95e351a7bd6487bc50a9b25152 in logging-log4j2's branch
refs/heads/LOG4J2-3393 from Volkan Yazici
[ https://gitbox.apache.org/repos/asf?p=logging-log4j2.git;h=264ae84 ]
LOG4J2-3393 Avoid StringBuilderEncoder thread-local allocation in
JsonTemplateLayout.
> JSON template layout performance regression
> ---
>
> Key: LOG4J2-3393
> URL: https://issues.apache.org/jira/browse/LOG4J2-3393
> Project: Log4j 2
> Issue Type: Improvement
> Components: JsonTemplateLayout
>Affects Versions: 2.17.1
>Reporter: Volkan Yazici
>Assignee: Volkan Yazici
>Priority: Major
>
> JTL performance is used to be on par with \{{log4j2-ecs-layout}}, though this
> is not the case anymore, there is a slight degradation. This story aims to
> investigate what is going on and fix it.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (LOG4J2-3393) JSON template layout performance regression
[
https://issues.apache.org/jira/browse/LOG4J2-3393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17506210#comment-17506210
]
ASF subversion and git services commented on LOG4J2-3393:
-
Commit c907fcdd52fc14a04083856bdb3ddbbbd5b554d1 in logging-log4j2's branch
refs/heads/LOG4J2-3393 from Volkan Yazici
[ https://gitbox.apache.org/repos/asf?p=logging-log4j2.git;h=c907fcd ]
LOG4J2-3393 Inline context acquisition in JsonTemplateLayout.
> JSON template layout performance regression
> ---
>
> Key: LOG4J2-3393
> URL: https://issues.apache.org/jira/browse/LOG4J2-3393
> Project: Log4j 2
> Issue Type: Improvement
> Components: JsonTemplateLayout
>Affects Versions: 2.17.1
>Reporter: Volkan Yazici
>Assignee: Volkan Yazici
>Priority: Major
>
> JTL performance is used to be on par with \{{log4j2-ecs-layout}}, though this
> is not the case anymore, there is a slight degradation. This story aims to
> investigate what is going on and fix it.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (LOG4J2-3393) JSON template layout performance regression
[
https://issues.apache.org/jira/browse/LOG4J2-3393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17506212#comment-17506212
]
ASF subversion and git services commented on LOG4J2-3393:
-
Commit 81905f95cbdb4a135c26a754ecfdefb447761ed1 in logging-log4j2's branch
refs/heads/LOG4J2-3393 from Volkan Yazici
[ https://gitbox.apache.org/repos/asf?p=logging-log4j2.git;h=81905f9 ]
LOG4J2-3393 Make TextEncoderHelper.encodeText() fallbacks JIT-friendly.
> JSON template layout performance regression
> ---
>
> Key: LOG4J2-3393
> URL: https://issues.apache.org/jira/browse/LOG4J2-3393
> Project: Log4j 2
> Issue Type: Improvement
> Components: JsonTemplateLayout
>Affects Versions: 2.17.1
>Reporter: Volkan Yazici
>Assignee: Volkan Yazici
>Priority: Major
>
> JTL performance is used to be on par with \{{log4j2-ecs-layout}}, though this
> is not the case anymore, there is a slight degradation. This story aims to
> investigate what is going on and fix it.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (LOG4J2-3393) JSON template layout performance regression
[
https://issues.apache.org/jira/browse/LOG4J2-3393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17506214#comment-17506214
]
ASF subversion and git services commented on LOG4J2-3393:
-
Commit 69608b94d07885c52d9691b2107d06d42b395349 in logging-log4j2's branch
refs/heads/LOG4J2-3393 from Volkan Yazici
[ https://gitbox.apache.org/repos/asf?p=logging-log4j2.git;h=69608b9 ]
LOG4J2-3393 Clean-up wrong BiConsumer usages.
> JSON template layout performance regression
> ---
>
> Key: LOG4J2-3393
> URL: https://issues.apache.org/jira/browse/LOG4J2-3393
> Project: Log4j 2
> Issue Type: Improvement
> Components: JsonTemplateLayout
>Affects Versions: 2.17.1
>Reporter: Volkan Yazici
>Assignee: Volkan Yazici
>Priority: Major
>
> JTL performance is used to be on par with \{{log4j2-ecs-layout}}, though this
> is not the case anymore, there is a slight degradation. This story aims to
> investigate what is going on and fix it.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (LOG4J2-3393) JSON template layout performance regression
[
https://issues.apache.org/jira/browse/LOG4J2-3393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17506207#comment-17506207
]
ASF subversion and git services commented on LOG4J2-3393:
-
Commit 3f6a9af70bcab0d4e80c90a0cbcd2a6becac9791 in logging-log4j2's branch
refs/heads/LOG4J2-3393 from Volkan Yazici
[ https://gitbox.apache.org/repos/asf?p=logging-log4j2.git;h=3f6a9af ]
LOG4J2-3393 Replace lambdas with classes to ease performance troubleshooting.
> JSON template layout performance regression
> ---
>
> Key: LOG4J2-3393
> URL: https://issues.apache.org/jira/browse/LOG4J2-3393
> Project: Log4j 2
> Issue Type: Improvement
> Components: JsonTemplateLayout
>Affects Versions: 2.17.1
>Reporter: Volkan Yazici
>Assignee: Volkan Yazici
>Priority: Major
>
> JTL performance is used to be on par with \{{log4j2-ecs-layout}}, though this
> is not the case anymore, there is a slight degradation. This story aims to
> investigate what is going on and fix it.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (LOG4J2-3393) JSON template layout performance regression
[
https://issues.apache.org/jira/browse/LOG4J2-3393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17506216#comment-17506216
]
ASF subversion and git services commented on LOG4J2-3393:
-
Commit 227d598703487a089dd0141f1323011a30b75962 in logging-log4j2's branch
refs/heads/LOG4J2-3393 from Volkan Yazici
[ https://gitbox.apache.org/repos/asf?p=logging-log4j2.git;h=227d598 ]
LOG4J2-3393 Optimize MessageResolver for CharSequence.
> JSON template layout performance regression
> ---
>
> Key: LOG4J2-3393
> URL: https://issues.apache.org/jira/browse/LOG4J2-3393
> Project: Log4j 2
> Issue Type: Improvement
> Components: JsonTemplateLayout
>Affects Versions: 2.17.1
>Reporter: Volkan Yazici
>Assignee: Volkan Yazici
>Priority: Major
>
> JTL performance is used to be on par with \{{log4j2-ecs-layout}}, though this
> is not the case anymore, there is a slight degradation. This story aims to
> investigate what is going on and fix it.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (LOG4J2-3393) JSON template layout performance regression
[
https://issues.apache.org/jira/browse/LOG4J2-3393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17506215#comment-17506215
]
ASF subversion and git services commented on LOG4J2-3393:
-
Commit 6e6bd235ebdad89a27944a94e30f60c9b52982b8 in logging-log4j2's branch
refs/heads/LOG4J2-3393 from Volkan Yazici
[ https://gitbox.apache.org/repos/asf?p=logging-log4j2.git;h=6e6bd23 ]
LOG4J2-3393 Fix revapi issues.
> JSON template layout performance regression
> ---
>
> Key: LOG4J2-3393
> URL: https://issues.apache.org/jira/browse/LOG4J2-3393
> Project: Log4j 2
> Issue Type: Improvement
> Components: JsonTemplateLayout
>Affects Versions: 2.17.1
>Reporter: Volkan Yazici
>Assignee: Volkan Yazici
>Priority: Major
>
> JTL performance is used to be on par with \{{log4j2-ecs-layout}}, though this
> is not the case anymore, there is a slight degradation. This story aims to
> investigate what is going on and fix it.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (LOG4J2-3432) RollingFileAppender fails after 100 backup cycles if filePattern contains "%04i" .
[
https://issues.apache.org/jira/browse/LOG4J2-3432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17506197#comment-17506197
]
Carl Smotricz commented on LOG4J2-3432:
---
Hi [~ggregory] , thank you for your attention!
In short: *YES, problem is also in 2.17.2 .*
I just
* downloaded 2.17.2,
* removed the old 2.17.1 jars,
* cleaned and rebuilt with the new jars (api and core),
* re-ran my test:
Failure mode is exactly the same.
> RollingFileAppender fails after 100 backup cycles if filePattern contains
> "%04i" .
> --
>
> Key: LOG4J2-3432
> URL: https://issues.apache.org/jira/browse/LOG4J2-3432
> Project: Log4j 2
> Issue Type: Bug
> Components: Appenders
>Affects Versions: 2.17.1
> Environment: * Red Hat Enterprise Linux Server release 6.10 (Santiago)
> * java version "1.8.0_181"
> Java(TM) SE Runtime Environment (build 1.8.0_181-b13)
> Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode)
> * 301873 Mar 9 07:53 log4j-api-2.17.1.jar
> 1790452 Mar 9 07:53 log4j-core-2.17.1.jar
>
>Reporter: Carl Smotricz
>Priority: Major
> Attachments: Main.java, log4j2.xml, runit.sh
>
>
> If a {{%i}} formatter in a filePattern includes a width specifier, e.g. "%4i"
> or "%04i", file renaming fails after a certain fixed number of cycles. After
> that, successive backups are renamed to the maximum cycle number and
> overwrite previous files of that same cycle number, regardless of min and max
> settings on the appender. Here are some failure modes I've found by testing:
> * if {{filePattern}} contains {{{}%06i{}}}, cycling breaks after 100.
> * if {{filePattern}} contains {{{}%006i{}}}, it breaks after 100 also.
> * if {{filePattern}} contains {{{}%6i{}}}, it breaks after 10.
> * if {{filePattern}} contains {{%06i}} and
> {{{}DefaultRolloverStrategy.min{}}}=1, {{{}max{}}}=9, it breaks after
> just 1.
> Now, the doc doesn't mention the %i spec supporting width and leading zero
> modifiers in the manner of printf() or String.format() . Yet, those
> variations (which I think other users will also be tempted to try) work -
> until they don't. So apparently width and padding on that spec are
> implemented but buggy.
> The doc for RollingRandomAccessFileAppender explicitly recommends these
> format modifiers:
> {quote}... and/or a %i which represents an integer counter. The integer
> counter allows specifying a padding, like %3i for space-padding the counter
> to 3 digits or (usually more useful) %03i for zero-padding the counter to 3
> digits.
> {quote}
> ...but I haven't verified that the problem occurs with that appender as well.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (LOG4J2-3416) Line Number Not getting printed in log file
[
https://issues.apache.org/jira/browse/LOG4J2-3416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17506183#comment-17506183
]
Sagar Salal commented on LOG4J2-3416:
-
[~vy] As mentioned by [~rgoers] If i would be using asynchronous logging then
how can i enable location there?
> Line Number Not getting printed in log file
> ---
>
> 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
> Attachments: log4j2.xml
>
>
> 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 printed in log file
[
https://issues.apache.org/jira/browse/LOG4J2-3416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17506179#comment-17506179
]
Sagar Salal commented on LOG4J2-3416:
-
[~vy] Where I can find these properties. I am using Spring framework.
> Line Number Not getting printed in log file
> ---
>
> 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
> Attachments: log4j2.xml
>
>
> 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)
[GitHub] [logging-log4j2] vy merged pull request #793: Bump logbackVersion from 1.2.3 to 1.2.11
vy merged pull request #793: URL: https://github.com/apache/logging-log4j2/pull/793 -- 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-3416) Line Number Not getting printed in log file
[
https://issues.apache.org/jira/browse/LOG4J2-3416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17506171#comment-17506171
]
Volkan Yazici commented on LOG4J2-3416:
---
[~sagarsalal], mind sharing your JVM flags too, please? (Maybe you're enabling
a certain Log4j feature via JVM system properties.)
> Line Number Not getting printed in log file
> ---
>
> 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
> Attachments: log4j2.xml
>
>
> 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 printed in log file
[
https://issues.apache.org/jira/browse/LOG4J2-3416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17506163#comment-17506163
]
Sagar Salal commented on LOG4J2-3416:
-
[~vy] Tried with 2.17.2. Still facing same issue.
> Line Number Not getting printed in log file
> ---
>
> 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
> Attachments: log4j2.xml
>
>
> 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 printed in log file
[
https://issues.apache.org/jira/browse/LOG4J2-3416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17506132#comment-17506132
]
Volkan Yazici commented on LOG4J2-3416:
---
[~sagarsalal], can you try with 2.17.2 and report back, please?
> Line Number Not getting printed in log file
> ---
>
> 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
> Attachments: log4j2.xml
>
>
> 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] [Reopened] (LOG4J2-3419) Unable to create custom logging level using log4j 2 Bridge API
[
https://issues.apache.org/jira/browse/LOG4J2-3419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ragini Gawande reopened LOG4J2-3419:
[~pkarwasz] ,
I am reopening this Jira because we are getting a small issues
2022-03-14 15:24:13,177 Main[3520] :main: com.test.common.logging.Test
ERROR#com.test.common.logging.Level - Can print ERROR
2022-03-14 15:24:13,181 Main[3520] :main: com.test.common.logging.Test
INFO#com.test.common.logging.Level - Can print Info
2022-03-14 15:24:13,181 Main[3520] :main: com.test.common.logging.Test
FINE#com.test.common.logging.Level - Can print FINE
Here instead on printing just Level name ERROR, its printing
ERROR#com.test.common.logging.Level
> Unable to create custom logging level using log4j 2 Bridge API
> --
>
> Key: LOG4J2-3419
> URL: https://issues.apache.org/jira/browse/LOG4J2-3419
> Project: Log4j 2
> Issue Type: Bug
> Components: Log4j 1.2 bridge
>Affects Versions: 2.17.1
> Environment: Using log4j 2 bridge API: log4j-1.2-api-2.17.1.jar
>Reporter: Ragini Gawande
>Assignee: Piotr Karwasz
>Priority: Blocker
> Fix For: 2.17.3
>
> Attachments: DemoCustom.zip
>
>
> Unable to create custom logging level using log4j 2 Bridge API
> Following did not create a custom logging level
> *public static final int FINE_INT = 13000;*
> *public static final Level FINE = new Level(FINE_INT, "FINE", 7);*
>
> Using FINE logging level is considered to be DEBUG level by default while
> printing it
> *Adding log:*
> log.log({*}Level.FINE{*},"PRINT: Level.FINE log");
>
> *Expected log printed:*
> 2022-02-25 15:50:09,208 Main[6788] :main: example.com.Test *FINE* - PRINT:
> Level.FINE log
>
> *Actual log printed:*
> 2022-02-25 15:50:09,208 Main[6788] :main: example.com.Test *DEBUG* - PRINT:
> Level.FINE log
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (LOG4J2-3416) Line Number Not getting printed in log file
[
https://issues.apache.org/jira/browse/LOG4J2-3416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17506121#comment-17506121
]
Sagar Salal commented on LOG4J2-3416:
-
not 2.17.2 but tried with 2.17 and 2.15.
> Line Number Not getting printed in log file
> ---
>
> 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
> Attachments: log4j2.xml
>
>
> 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 printed in log file
[
https://issues.apache.org/jira/browse/LOG4J2-3416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17506115#comment-17506115
]
Sagar Salal commented on LOG4J2-3416:
-
[~vy] I dont know but if by chance I am using asynchronous logging. How can i
enable location?
> Line Number Not getting printed in log file
> ---
>
> 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
> Attachments: log4j2.xml
>
>
> 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 printed in log file
[
https://issues.apache.org/jira/browse/LOG4J2-3416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17506117#comment-17506117
]
Volkan Yazici commented on LOG4J2-3416:
---
[~sagarsalal], do you observe the problem in 2.17.2 too?
> Line Number Not getting printed in log file
> ---
>
> 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
> Attachments: log4j2.xml
>
>
> 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)
[GitHub] [logging-log4j2] vy commented on pull request #793: Bump logbackVersion from 1.2.3 to 1.2.11
vy commented on pull request #793: URL: https://github.com/apache/logging-log4j2/pull/793#issuecomment-1066584678 @dependabot rebase -- 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-3416) Line Number Not getting printed in log file
[
https://issues.apache.org/jira/browse/LOG4J2-3416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17506109#comment-17506109
]
Sagar Salal commented on LOG4J2-3416:
-
[~vy] For me it is giving below output
2022-03-14 13:57:50,111 [http-nio2-8080-exec-16] INFO
c.p.p.a.s.w.i.className.(): \{abc=111,pqr=2, Id=202203141} - Invalid mode
Version that I have used : 2.17.0
> Line Number Not getting printed in log file
> ---
>
> 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
> Attachments: log4j2.xml
>
>
> 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] [Closed] (LOG4J2-3419) Unable to create custom logging level using log4j 2 Bridge API
[
https://issues.apache.org/jira/browse/LOG4J2-3419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ragini Gawande closed LOG4J2-3419.
--
> Unable to create custom logging level using log4j 2 Bridge API
> --
>
> Key: LOG4J2-3419
> URL: https://issues.apache.org/jira/browse/LOG4J2-3419
> Project: Log4j 2
> Issue Type: Bug
> Components: Log4j 1.2 bridge
>Affects Versions: 2.17.1
> Environment: Using log4j 2 bridge API: log4j-1.2-api-2.17.1.jar
>Reporter: Ragini Gawande
>Assignee: Piotr Karwasz
>Priority: Blocker
> Fix For: 2.17.3
>
> Attachments: DemoCustom.zip
>
>
> Unable to create custom logging level using log4j 2 Bridge API
> Following did not create a custom logging level
> *public static final int FINE_INT = 13000;*
> *public static final Level FINE = new Level(FINE_INT, "FINE", 7);*
>
> Using FINE logging level is considered to be DEBUG level by default while
> printing it
> *Adding log:*
> log.log({*}Level.FINE{*},"PRINT: Level.FINE log");
>
> *Expected log printed:*
> 2022-02-25 15:50:09,208 Main[6788] :main: example.com.Test *FINE* - PRINT:
> Level.FINE log
>
> *Actual log printed:*
> 2022-02-25 15:50:09,208 Main[6788] :main: example.com.Test *DEBUG* - PRINT:
> Level.FINE log
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (LOG4J2-3419) Unable to create custom logging level using log4j 2 Bridge API
[
https://issues.apache.org/jira/browse/LOG4J2-3419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17506105#comment-17506105
]
Ragini Gawande commented on LOG4J2-3419:
Thanks [~pkarwasz] for getting this issue solved.
> Unable to create custom logging level using log4j 2 Bridge API
> --
>
> Key: LOG4J2-3419
> URL: https://issues.apache.org/jira/browse/LOG4J2-3419
> Project: Log4j 2
> Issue Type: Bug
> Components: Log4j 1.2 bridge
>Affects Versions: 2.17.1
> Environment: Using log4j 2 bridge API: log4j-1.2-api-2.17.1.jar
>Reporter: Ragini Gawande
>Assignee: Piotr Karwasz
>Priority: Blocker
> Fix For: 2.17.3
>
> Attachments: DemoCustom.zip
>
>
> Unable to create custom logging level using log4j 2 Bridge API
> Following did not create a custom logging level
> *public static final int FINE_INT = 13000;*
> *public static final Level FINE = new Level(FINE_INT, "FINE", 7);*
>
> Using FINE logging level is considered to be DEBUG level by default while
> printing it
> *Adding log:*
> log.log({*}Level.FINE{*},"PRINT: Level.FINE log");
>
> *Expected log printed:*
> 2022-02-25 15:50:09,208 Main[6788] :main: example.com.Test *FINE* - PRINT:
> Level.FINE log
>
> *Actual log printed:*
> 2022-02-25 15:50:09,208 Main[6788] :main: example.com.Test *DEBUG* - PRINT:
> Level.FINE log
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (LOG4J2-3416) Line Number Not getting printed in log file
[
https://issues.apache.org/jira/browse/LOG4J2-3416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17506095#comment-17506095
]
Volkan Yazici commented on LOG4J2-3416:
---
[~sagarsalal], your configuration works for me without a problem.
I have adopted your {{log4j2.xml}} as follows:
{code:xml}
{code}
I have created a simple Java class:
{code:java}
package com.xyz;
import org.apache.logging.log4j.LogManager;
import org.apache.logging.log4j.Logger;
import org.apache.logging.log4j.ThreadContext;
public class Log4j2_3416 {
private static final Logger LOGGER = LogManager.getLogger();
public static void main(String[] args) {
ThreadContext.put("env", "mock");
LOGGER.trace("this should not get logged");
LOGGER.info("this should be logged");
}
}
{code}
Ran the code against Log4j 2.17.2 and got the following output:
{code}
$ zcat /tmp/LOG4J2-3416/mock-xyz.log.2022-03-14-09-59.gz
2022-03-14 09:51:16,630 [main] INFO c.x.Log4j2_3416.main():12 {env=mock} -
this should be logged
{code}
See the line number and the method name above.
> Line Number Not getting printed in log file
> ---
>
> 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
> Attachments: log4j2.xml
>
>
> 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-3419) Unable to create custom logging level using log4j 2 Bridge API
[
https://issues.apache.org/jira/browse/LOG4J2-3419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17506083#comment-17506083
]
Tukesh commented on LOG4J2-3419:
Hi Gary,
I tested 2.17.3-snapshot and I got desired results. I am closing this JIRA.
Thank you.
> Unable to create custom logging level using log4j 2 Bridge API
> --
>
> Key: LOG4J2-3419
> URL: https://issues.apache.org/jira/browse/LOG4J2-3419
> Project: Log4j 2
> Issue Type: Bug
> Components: Log4j 1.2 bridge
>Affects Versions: 2.17.1
> Environment: Using log4j 2 bridge API: log4j-1.2-api-2.17.1.jar
>Reporter: Ragini Gawande
>Assignee: Piotr Karwasz
>Priority: Blocker
> Fix For: 2.17.3
>
> Attachments: DemoCustom.zip
>
>
> Unable to create custom logging level using log4j 2 Bridge API
> Following did not create a custom logging level
> *public static final int FINE_INT = 13000;*
> *public static final Level FINE = new Level(FINE_INT, "FINE", 7);*
>
> Using FINE logging level is considered to be DEBUG level by default while
> printing it
> *Adding log:*
> log.log({*}Level.FINE{*},"PRINT: Level.FINE log");
>
> *Expected log printed:*
> 2022-02-25 15:50:09,208 Main[6788] :main: example.com.Test *FINE* - PRINT:
> Level.FINE log
>
> *Actual log printed:*
> 2022-02-25 15:50:09,208 Main[6788] :main: example.com.Test *DEBUG* - PRINT:
> Level.FINE log
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (LOG4J2-3431) log4j bridge API :- Log message filtering based on UtilLoggingLevel fails and all messages are written into log files
[
https://issues.apache.org/jira/browse/LOG4J2-3431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17506082#comment-17506082
]
Tukesh commented on LOG4J2-3431:
Hi Gary,
I tested 2.17.3-snapshot and I got desired results. I am closing this JIRA.
Thank you.
> log4j bridge API :- Log message filtering based on UtilLoggingLevel fails and
> all messages are written into log files
> -
>
> Key: LOG4J2-3431
> URL: https://issues.apache.org/jira/browse/LOG4J2-3431
> Project: Log4j 2
> Issue Type: Bug
> Environment: JDK 1.8
>
> -Dlog4j1.compatibility=true
> # log4j-1.2-api-2.17.2.jar
> # log4j-api-2.17.2.jar
> # log4j-core-2.17.2.jar
>
>
>Reporter: Tukesh
>Assignee: Piotr Karwasz
>Priority: Major
>
> log4j bridge API :- Log message filtering based on UtilLoggingLevel fails and
> all messages are written into log files
>
> {code:java}
> // demo code
> package test.logger;import org.apache.log4j.Logger;
> import org.apache.log4j.helpers.UtilLoggingLevel;import java.io.*;
> import java.sql.SQLException;
> import java.util.concurrent.TimeUnit;
> public class LoggerExample{
> static Logger log = Logger.getLogger(LoggerExample.class.getName());
>
> public static void main(String[] args)throws IOException,SQLException{
> System.out.println("I'm running...");
> while(true){
> System.out.println("I'm running...");
>
> log.info("Log4j-shell this is a info message");
>
> log.log(UtilLoggingLevel.INFO,"INFO");
> log.log(UtilLoggingLevel.FINE,"FINE");
> log.log(UtilLoggingLevel.FINER,"FINER");
> log.log(UtilLoggingLevel.FINEST,"FINEST");
> log.log(UtilLoggingLevel.CONFIG,"CONIG");
>
> try {
> TimeUnit.MILLISECONDS.sleep(1000);
> } catch (InterruptedException e) {
> e.printStackTrace();
> }
> }
> }
> } {code}
> {code:java}
> log4j.rootLogger=FINE#org.apache.log4j.helpers.UtilLoggingLevel,DMCC_TRACE_LOGGER
>
> log4j.appender.DMCC_TRACE_LOGGER.Threshold=FINE#org.apache.log4j.helpers.UtilLoggingLevel
> log4j.appender.DMCC_TRACE_LOGGER=org.apache.log4j.RollingFileAppender
> log4j.appender.DMCC_TRACE_LOGGER.File=Dmcc-trace.log
> log4j.appender.DMCC_TRACE_LOGGER.Append=true
> log4j.appender.DMCC_TRACE_LOGGER.layout=org.apache.log4j.PatternLayout
> log4j.appender.DMCC_TRACE_LOGGER.layout.ConversionPattern=%d
> DmccMain[%X{PID}] :%t: %c %-4p - %m%n
> log4j.appender.DMCC_TRACE_LOGGER.maxFileSize=10MB
> log4j.appender.DMCC_TRACE_LOGGER.maxBackupIndex=20
> {code}
>
>
> +*Investigation :-*+
> convertLevel function from OptionConverter.java doesn't consider
> UtilLoggingLevel level for mapping. so it sets Level as DEBUG for
> UtilLoggingLevel classes.
> {code:java}
> // code placeholder
> final org.apache.logging.log4j.Level level = levelStr == null ?
> org.apache.logging.log4j.Level.ERROR :
> OptionConverter.convertLevel(levelStr, org.apache.logging.log4j.Level.DEBUG);
> loggerConfig.setLevel(level);
> LOGGER.debug("Logger {} level set to {}", loggerName, level);
>
>
> OptionConverter.java :-
> public static org.apache.logging.log4j.Level convertLevel(final Level
> level) {
> if (level == null) {
> return org.apache.logging.log4j.Level.ERROR;
> }
> if (level.isGreaterOrEqual(Level.FATAL)) {
> return org.apache.logging.log4j.Level.FATAL;
> } else if (level.isGreaterOrEqual(Level.ERROR)) {
> return org.apache.logging.log4j.Level.ERROR;
> } else if (level.isGreaterOrEqual(Level.WARN)) {
> return org.apache.logging.log4j.Level.WARN;
> } else if (level.isGreaterOrEqual(Level.INFO)) {
> return org.apache.logging.log4j.Level.INFO;
> } else if (level.isGreaterOrEqual(Level.DEBUG)) {
> return org.apache.logging.log4j.Level.DEBUG;
> } else if (level.isGreaterOrEqual(Level.TRACE)) {
> return org.apache.logging.log4j.Level.TRACE;
> }
> return org.apache.logging.log4j.Level.ALL;
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Closed] (LOG4J2-3431) log4j bridge API :- Log message filtering based on UtilLoggingLevel fails and all messages are written into log files
[
https://issues.apache.org/jira/browse/LOG4J2-3431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tukesh closed LOG4J2-3431.
--
Hi Gary,
I tested 2.17.3-snapshot and I got desired results. I am closing this JIRA.
Thank you.
> log4j bridge API :- Log message filtering based on UtilLoggingLevel fails and
> all messages are written into log files
> -
>
> Key: LOG4J2-3431
> URL: https://issues.apache.org/jira/browse/LOG4J2-3431
> Project: Log4j 2
> Issue Type: Bug
> Environment: JDK 1.8
>
> -Dlog4j1.compatibility=true
> # log4j-1.2-api-2.17.2.jar
> # log4j-api-2.17.2.jar
> # log4j-core-2.17.2.jar
>
>
>Reporter: Tukesh
>Assignee: Piotr Karwasz
>Priority: Major
>
> log4j bridge API :- Log message filtering based on UtilLoggingLevel fails and
> all messages are written into log files
>
> {code:java}
> // demo code
> package test.logger;import org.apache.log4j.Logger;
> import org.apache.log4j.helpers.UtilLoggingLevel;import java.io.*;
> import java.sql.SQLException;
> import java.util.concurrent.TimeUnit;
> public class LoggerExample{
> static Logger log = Logger.getLogger(LoggerExample.class.getName());
>
> public static void main(String[] args)throws IOException,SQLException{
> System.out.println("I'm running...");
> while(true){
> System.out.println("I'm running...");
>
> log.info("Log4j-shell this is a info message");
>
> log.log(UtilLoggingLevel.INFO,"INFO");
> log.log(UtilLoggingLevel.FINE,"FINE");
> log.log(UtilLoggingLevel.FINER,"FINER");
> log.log(UtilLoggingLevel.FINEST,"FINEST");
> log.log(UtilLoggingLevel.CONFIG,"CONIG");
>
> try {
> TimeUnit.MILLISECONDS.sleep(1000);
> } catch (InterruptedException e) {
> e.printStackTrace();
> }
> }
> }
> } {code}
> {code:java}
> log4j.rootLogger=FINE#org.apache.log4j.helpers.UtilLoggingLevel,DMCC_TRACE_LOGGER
>
> log4j.appender.DMCC_TRACE_LOGGER.Threshold=FINE#org.apache.log4j.helpers.UtilLoggingLevel
> log4j.appender.DMCC_TRACE_LOGGER=org.apache.log4j.RollingFileAppender
> log4j.appender.DMCC_TRACE_LOGGER.File=Dmcc-trace.log
> log4j.appender.DMCC_TRACE_LOGGER.Append=true
> log4j.appender.DMCC_TRACE_LOGGER.layout=org.apache.log4j.PatternLayout
> log4j.appender.DMCC_TRACE_LOGGER.layout.ConversionPattern=%d
> DmccMain[%X{PID}] :%t: %c %-4p - %m%n
> log4j.appender.DMCC_TRACE_LOGGER.maxFileSize=10MB
> log4j.appender.DMCC_TRACE_LOGGER.maxBackupIndex=20
> {code}
>
>
> +*Investigation :-*+
> convertLevel function from OptionConverter.java doesn't consider
> UtilLoggingLevel level for mapping. so it sets Level as DEBUG for
> UtilLoggingLevel classes.
> {code:java}
> // code placeholder
> final org.apache.logging.log4j.Level level = levelStr == null ?
> org.apache.logging.log4j.Level.ERROR :
> OptionConverter.convertLevel(levelStr, org.apache.logging.log4j.Level.DEBUG);
> loggerConfig.setLevel(level);
> LOGGER.debug("Logger {} level set to {}", loggerName, level);
>
>
> OptionConverter.java :-
> public static org.apache.logging.log4j.Level convertLevel(final Level
> level) {
> if (level == null) {
> return org.apache.logging.log4j.Level.ERROR;
> }
> if (level.isGreaterOrEqual(Level.FATAL)) {
> return org.apache.logging.log4j.Level.FATAL;
> } else if (level.isGreaterOrEqual(Level.ERROR)) {
> return org.apache.logging.log4j.Level.ERROR;
> } else if (level.isGreaterOrEqual(Level.WARN)) {
> return org.apache.logging.log4j.Level.WARN;
> } else if (level.isGreaterOrEqual(Level.INFO)) {
> return org.apache.logging.log4j.Level.INFO;
> } else if (level.isGreaterOrEqual(Level.DEBUG)) {
> return org.apache.logging.log4j.Level.DEBUG;
> } else if (level.isGreaterOrEqual(Level.TRACE)) {
> return org.apache.logging.log4j.Level.TRACE;
> }
> return org.apache.logging.log4j.Level.ALL;
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (LOG4J2-3419) Unable to create custom logging level using log4j 2 Bridge API
[
https://issues.apache.org/jira/browse/LOG4J2-3419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17506062#comment-17506062
]
Piotr Karwasz commented on LOG4J2-3419:
---
It's a snapshot available on: https://repository.apache.org/snapshots/ (it's a
Maven repository).
If you are not using a dependency management system such as Maven or Gradle,
take the latest jar from:
https://repository.apache.org/content/groups/snapshots/org/apache/logging/log4j/log4j-1.2-api/2.17.3-SNAPSHOT/
> Unable to create custom logging level using log4j 2 Bridge API
> --
>
> Key: LOG4J2-3419
> URL: https://issues.apache.org/jira/browse/LOG4J2-3419
> Project: Log4j 2
> Issue Type: Bug
> Components: Log4j 1.2 bridge
>Affects Versions: 2.17.1
> Environment: Using log4j 2 bridge API: log4j-1.2-api-2.17.1.jar
>Reporter: Ragini Gawande
>Assignee: Piotr Karwasz
>Priority: Blocker
> Fix For: 2.17.3
>
> Attachments: DemoCustom.zip
>
>
> Unable to create custom logging level using log4j 2 Bridge API
> Following did not create a custom logging level
> *public static final int FINE_INT = 13000;*
> *public static final Level FINE = new Level(FINE_INT, "FINE", 7);*
>
> Using FINE logging level is considered to be DEBUG level by default while
> printing it
> *Adding log:*
> log.log({*}Level.FINE{*},"PRINT: Level.FINE log");
>
> *Expected log printed:*
> 2022-02-25 15:50:09,208 Main[6788] :main: example.com.Test *FINE* - PRINT:
> Level.FINE log
>
> *Actual log printed:*
> 2022-02-25 15:50:09,208 Main[6788] :main: example.com.Test *DEBUG* - PRINT:
> Level.FINE log
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[GitHub] [logging-log4j-scala] vy merged pull request #19: sbt 1.6.2
vy merged pull request #19: URL: https://github.com/apache/logging-log4j-scala/pull/19 -- 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-log4net] fluffynuts merged pull request #80: Link Correction.
fluffynuts merged pull request #80: URL: https://github.com/apache/logging-log4net/pull/80 -- 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-3419) Unable to create custom logging level using log4j 2 Bridge API
[
https://issues.apache.org/jira/browse/LOG4J2-3419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17506049#comment-17506049
]
Ragini Gawande commented on LOG4J2-3419:
[~pkarwasz] ,
When can we find the link to new version 2.17.3
[https://logging.apache.org/log4j/2.x/download.html] this link has the latest
as 2.17.2
> Unable to create custom logging level using log4j 2 Bridge API
> --
>
> Key: LOG4J2-3419
> URL: https://issues.apache.org/jira/browse/LOG4J2-3419
> Project: Log4j 2
> Issue Type: Bug
> Components: Log4j 1.2 bridge
>Affects Versions: 2.17.1
> Environment: Using log4j 2 bridge API: log4j-1.2-api-2.17.1.jar
>Reporter: Ragini Gawande
>Assignee: Piotr Karwasz
>Priority: Blocker
> Fix For: 2.17.3
>
> Attachments: DemoCustom.zip
>
>
> Unable to create custom logging level using log4j 2 Bridge API
> Following did not create a custom logging level
> *public static final int FINE_INT = 13000;*
> *public static final Level FINE = new Level(FINE_INT, "FINE", 7);*
>
> Using FINE logging level is considered to be DEBUG level by default while
> printing it
> *Adding log:*
> log.log({*}Level.FINE{*},"PRINT: Level.FINE log");
>
> *Expected log printed:*
> 2022-02-25 15:50:09,208 Main[6788] :main: example.com.Test *FINE* - PRINT:
> Level.FINE log
>
> *Actual log printed:*
> 2022-02-25 15:50:09,208 Main[6788] :main: example.com.Test *DEBUG* - PRINT:
> Level.FINE log
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
