[jira] [Commented] (LOG4J2-2880) High CPU consumption using StackWalker

[ https://issues.apache.org/jira/browse/LOG4J2-2880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17147197#comment-17147197 ] Hash Jang commented on LOG4J2-2880: --- Well, I hope you can eliminate the Stackwalker un

[jira] [Commented] (LOG4J2-2880) High CPU consumption using StackWalker

[ https://issues.apache.org/jira/browse/LOG4J2-2880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17147195#comment-17147195 ] Ralph Goers commented on LOG4J2-2880: - OK. If you believe this matches the JDK bug w

[jira] [Comment Edited] (LOG4J2-2880) High CPU consumption using StackWalker

[ https://issues.apache.org/jira/browse/LOG4J2-2880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17147185#comment-17147185 ] Hash Jang edited comment on LOG4J2-2880 at 6/28/20, 3:38 AM: -

[jira] [Commented] (LOG4J2-2880) High CPU consumption using StackWalker

[ https://issues.apache.org/jira/browse/LOG4J2-2880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17147185#comment-17147185 ] Hash Jang commented on LOG4J2-2880: --- By the way, there are four reactor-http-epoll- th

[jira] [Commented] (LOG4J2-2880) High CPU consumption using StackWalker

[ https://issues.apache.org/jira/browse/LOG4J2-2880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17147174#comment-17147174 ] Hash Jang commented on LOG4J2-2880: --- Thanks for the response. But I think we are not f

[jira] [Updated] (LOG4J2-2880) High CPU consumption using StackWalker

[ https://issues.apache.org/jira/browse/LOG4J2-2880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hash Jang updated LOG4J2-2880: -- Attachment: log4j2.xml > High CPU consumption using StackWalker >

[jira] [Comment Edited] (LOG4J2-2880) High CPU consumption using StackWalker

[ https://issues.apache.org/jira/browse/LOG4J2-2880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17147165#comment-17147165 ] Ralph Goers edited comment on LOG4J2-2880 at 6/28/20, 3:08 AM: ---

[jira] [Commented] (LOG4J2-2880) High CPU consumption using StackWalker

[ https://issues.apache.org/jira/browse/LOG4J2-2880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17147165#comment-17147165 ] Ralph Goers commented on LOG4J2-2880: - There is not enough information here to be ab

[jira] [Updated] (LOG4J2-2880) High CPU consumption using StackWalker

[ https://issues.apache.org/jira/browse/LOG4J2-2880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hash Jang updated LOG4J2-2880: -- Description: While using OpenJDK 11, there are possibility cause severe CPU consumption because of JD

[jira] [Created] (LOG4J2-2880) High CPU consumption using StackWalker

Hash Jang created LOG4J2-2880: - Summary: High CPU consumption using StackWalker Key: LOG4J2-2880 URL: https://issues.apache.org/jira/browse/LOG4J2-2880 Project: Log4j 2 Issue Type: Bug

[GitHub] [logging-log4j2] rgoers edited a comment on pull request #366: Allow clients to set the source manually.

rgoers edited a comment on pull request #366: URL: https://github.com/apache/logging-log4j2/pull/366#issuecomment-650652949 That is true, but it seems odd to add the StackTraceElement to things like traceEntry & traceExit and then ALSO add them to Messages. The location information isn't l

[GitHub] [logging-log4j2] rgoers commented on pull request #366: Allow clients to set the source manually.

rgoers commented on pull request #366: URL: https://github.com/apache/logging-log4j2/pull/366#issuecomment-650652949 That is true, but it seems odd to add the StackTraceElement to things like traceEntry & traceExit and then ALSO add them to Messages. The location information isn't logicall

[GitHub] [logging-log4j2] garydgregory commented on pull request #366: Allow clients to set the source manually.

garydgregory commented on pull request #366: URL: https://github.com/apache/logging-log4j2/pull/366#issuecomment-650650605 The breaking could be less using default methods FWIW... This is an automated message from the Apache

[GitHub] [logging-log4j2] rgoers commented on pull request #366: Allow clients to set the source manually.

rgoers commented on pull request #366: URL: https://github.com/apache/logging-log4j2/pull/366#issuecomment-650650281 This change is modifying the signatures of virtually all the Messages, which will break some existing users. What's more, clients who want to set the source manually already

[GitHub] [logging-log4j2] shawjef3 opened a new pull request #366: Allow clients to set the source manually.

shawjef3 opened a new pull request #366: URL: https://github.com/apache/logging-log4j2/pull/366 The purpose of this is to make it possible to improve performance. Getting the StackTraceElement for a message is somewhat expensive. Creating it manually is tedious and no one should do it, but