[jira] [Resolved] (LOG4J2-3598) Upgrade to SLF4J 2.0.1

[ https://issues.apache.org/jira/browse/LOG4J2-3598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Karwasz resolved LOG4J2-3598. --- Resolution: Fixed > Upgrade to SLF4J 2.0.1 > -- > > Key:

[GitHub] [logging-log4j2] ppkarwasz opened a new pull request, #1054: [LOG4J2-3598] Lazily evaluate the level in `Log4jEventBuilder`

ppkarwasz opened a new pull request, #1054: URL: https://github.com/apache/logging-log4j2/pull/1054 To ensure maximum compatibility with Logback and the changes in SLF4J 2.0.1 (cf. [SLF4J-560](https://jira.qos.ch/browse/SLF4J-560)) we create the `LogBuilder` lazily only when `log()` is call

[jira] [Created] (LOG4J2-3598) Upgrade to SLF4J 2.0.1

Piotr Karwasz created LOG4J2-3598: - Summary: Upgrade to SLF4J 2.0.1 Key: LOG4J2-3598 URL: https://issues.apache.org/jira/browse/LOG4J2-3598 Project: Log4j 2 Issue Type: Improvement

[jira] [Updated] (LOG4J2-3035) Refresh the Stale reference of Log File once the physical file is deleted by external process

[ https://issues.apache.org/jira/browse/LOG4J2-3035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Karwasz updated LOG4J2-3035: -- Fix Version/s: (was: 2.16.0) > Refresh the Stale reference of Log File once the physical f

[jira] [Updated] (LOG4J2-3596) Getting Out of Memory Exception after upgrading log4j from 1.x to 2.17.2

[ https://issues.apache.org/jira/browse/LOG4J2-3596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-3596: Issue Type: Question (was: Bug) > Getting Out of Memory Exception after upgrading log4j from 1.x

[jira] [Resolved] (LOG4J2-3596) Getting Out of Memory Exception after upgrading log4j from 1.x to 2.17.2

[ https://issues.apache.org/jira/browse/LOG4J2-3596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-3596. - Resolution: Information Provided > Getting Out of Memory Exception after upgrading log4j from 1.

[jira] [Commented] (LOG4J2-3596) Getting Out of Memory Exception after upgrading log4j from 1.x to 2.17.2

[ https://issues.apache.org/jira/browse/LOG4J2-3596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17604715#comment-17604715 ] Ralph Goers commented on LOG4J2-3596: - My guess is that this is happening because lo

[jira] [Created] (LOG4J2-3597) Application got struck with Deadlock on TimeoutBlockingWaitStrategy lock

Ramprasad created LOG4J2-3597: - Summary: Application got struck with Deadlock on TimeoutBlockingWaitStrategy lock Key: LOG4J2-3597 URL: https://issues.apache.org/jira/browse/LOG4J2-3597 Project: Log4j 2

[jira] [Comment Edited] (LOG4J2-3586) AppenderSkeleton substitute in Log4j2.17.

[ https://issues.apache.org/jira/browse/LOG4J2-3586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17604004#comment-17604004 ] Deepak Pareek edited comment on LOG4J2-3586 at 9/14/22 12:11 PM: -

[jira] [Created] (LOG4J2-3596) Getting Out of Memory Exception after upgrading log4j from 1.x to 2.17.2

sowjanya created LOG4J2-3596: Summary: Getting Out of Memory Exception after upgrading log4j from 1.x to 2.17.2 Key: LOG4J2-3596 URL: https://issues.apache.org/jira/browse/LOG4J2-3596 Project: Log4j 2

[jira] [Comment Edited] (LOG4J2-3586) AppenderSkeleton substitute in Log4j2.17.

[ https://issues.apache.org/jira/browse/LOG4J2-3586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17604004#comment-17604004 ] Deepak Pareek edited comment on LOG4J2-3586 at 9/14/22 10:55 AM: -

[jira] [Commented] (LOG4J2-3586) AppenderSkeleton substitute in Log4j2.17.

[ https://issues.apache.org/jira/browse/LOG4J2-3586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17604004#comment-17604004 ] Deepak Pareek commented on LOG4J2-3586: --- Hello [~rgoers] , Thank you Ralph, We ha

[GitHub] [logging-log4j2] dependabot[bot] commented on pull request #1041: Bump netty-all from 4.1.80.Final to 4.1.81.Final

dependabot[bot] commented on PR #1041: URL: https://github.com/apache/logging-log4j2/pull/1041#issuecomment-1246530182 Superseded by #1053. -- 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 spe

[GitHub] [logging-log4j2] dependabot[bot] closed pull request #1041: Bump netty-all from 4.1.80.Final to 4.1.81.Final

dependabot[bot] closed pull request #1041: Bump netty-all from 4.1.80.Final to 4.1.81.Final URL: https://github.com/apache/logging-log4j2/pull/1041 -- 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 th

[GitHub] [logging-log4j2] dependabot[bot] opened a new pull request, #1053: Bump netty-all from 4.1.80.Final to 4.1.82.Final

dependabot[bot] opened a new pull request, #1053: URL: https://github.com/apache/logging-log4j2/pull/1053 Bumps [netty-all](https://github.com/netty/netty) from 4.1.80.Final to 4.1.82.Final. Commits https://github.com/netty/netty/commit/47799635143d7a11b56c4a4e9a1e65ca221d28ca"

[jira] [Commented] (LOG4J2-3595) Supporting disruptor 4.x

[ https://issues.apache.org/jira/browse/LOG4J2-3595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17603928#comment-17603928 ] Ralph Goers commented on LOG4J2-3595: - This implies we would have to create a wrappe

[jira] [Commented] (LOG4J2-3593) StackLocator Reflection.getCallerClass warning is misleading / incorrect

[ https://issues.apache.org/jira/browse/LOG4J2-3593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17603920#comment-17603920 ] Ralph Goers commented on LOG4J2-3593: - Looks good to me. > StackLocator Reflection.