[GitHub] [logging-log4j2] carterkozak commented on a change in pull request #335: Import of LogstashLayout as JsonTemplateLayout

carterkozak commented on a change in pull request #335: Import of LogstashLayout as JsonTemplateLayout URL: https://github.com/apache/logging-log4j2/pull/335#discussion_r405621721 ## File path: log4j-api/src/main/java/org/apache/logging/log4j/util/Strings.java ## @@ -55,14

[GitHub] [logging-log4j2] carterkozak commented on a change in pull request #335: Import of LogstashLayout as JsonTemplateLayout

carterkozak commented on a change in pull request #335: Import of LogstashLayout as JsonTemplateLayout URL: https://github.com/apache/logging-log4j2/pull/335#discussion_r405619866 ## File path: log4j-api/src/main/java/org/apache/logging/log4j/util/Strings.java ## @@ -286,4

[GitHub] [logging-log4j2] carterkozak commented on a change in pull request #335: Import of LogstashLayout as JsonTemplateLayout

carterkozak commented on a change in pull request #335: Import of LogstashLayout as JsonTemplateLayout URL: https://github.com/apache/logging-log4j2/pull/335#discussion_r405623558 ## File path: log4j-core/src/main/java/org/apache/logging/log4j/core/util/Throwables.java ##

[GitHub] [logging-log4j2] carterkozak commented on a change in pull request #335: Import of LogstashLayout as JsonTemplateLayout

carterkozak commented on a change in pull request #335: Import of LogstashLayout as JsonTemplateLayout URL: https://github.com/apache/logging-log4j2/pull/335#discussion_r405628150 ## File path: log4j-layout-json-template/src/main/java/org/apache/logging/log4j/layout/json/template/J

[GitHub] [logging-log4j2] rgoers commented on issue #335: Import of LogstashLayout as JsonTemplateLayout

rgoers commented on issue #335: Import of LogstashLayout as JsonTemplateLayout URL: https://github.com/apache/logging-log4j2/pull/335#issuecomment-611028572 mailing list. This is already too long. This is an automated message

[GitHub] [logging-log4j2] vy commented on issue #335: Import of LogstashLayout as JsonTemplateLayout

vy commented on issue #335: Import of LogstashLayout as JsonTemplateLayout URL: https://github.com/apache/logging-log4j2/pull/335#issuecomment-610976180 > The logging in the cloud docs need to be discussed or reverted. How shall we proceed? Do you want to discuss in the mailing list o

[jira] [Comment Edited] (LOG4J2-2589) Potential Memory Leak

[ https://issues.apache.org/jira/browse/LOG4J2-2589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17078099#comment-17078099 ] Stefan Höltker edited comment on LOG4J2-2589 at 4/8/20, 11:58 AM:

[jira] [Comment Edited] (LOG4J2-2589) Potential Memory Leak

[ https://issues.apache.org/jira/browse/LOG4J2-2589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17078099#comment-17078099 ] Stefan Höltker edited comment on LOG4J2-2589 at 4/8/20, 11:57 AM:

[jira] [Commented] (LOG4J2-2589) Potential Memory Leak

[ https://issues.apache.org/jira/browse/LOG4J2-2589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17078099#comment-17078099 ] Stefan Höltker commented on LOG4J2-2589: The AbstractConfiguration helped to "fl

[jira] [Updated] (LOG4J2-2589) Potential Memory Leak

[ https://issues.apache.org/jira/browse/LOG4J2-2589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Höltker updated LOG4J2-2589: --- Attachment: screenshot-3.png > Potential Memory Leak > -- > >

[jira] [Commented] (LOG4J2-2589) Potential Memory Leak

[ https://issues.apache.org/jira/browse/LOG4J2-2589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17078083#comment-17078083 ] Stefan Höltker commented on LOG4J2-2589: Ok i will have a look on the AbstractCo

[jira] [Commented] (LOG4J2-2589) Potential Memory Leak

[ https://issues.apache.org/jira/browse/LOG4J2-2589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17077919#comment-17077919 ] Ralph Goers commented on LOG4J2-2589: - Also, it would be great if you could add what

[jira] [Commented] (LOG4J2-2589) Potential Memory Leak

[ https://issues.apache.org/jira/browse/LOG4J2-2589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17077916#comment-17077916 ] Ralph Goers commented on LOG4J2-2589: - Look in AbstractConfiguration. > Potential M

[jira] [Commented] (LOG4J2-2589) Potential Memory Leak

[ https://issues.apache.org/jira/browse/LOG4J2-2589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17077899#comment-17077899 ] Stefan Höltker commented on LOG4J2-2589: Let me first thank you for your time an

[jira] [Updated] (LOG4J2-2589) Potential Memory Leak

[ https://issues.apache.org/jira/browse/LOG4J2-2589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Höltker updated LOG4J2-2589: --- Attachment: screenshot-2.png > Potential Memory Leak > -- > >

[jira] [Comment Edited] (LOG4J2-2589) Potential Memory Leak

[ https://issues.apache.org/jira/browse/LOG4J2-2589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17077892#comment-17077892 ] Ralph Goers edited comment on LOG4J2-2589 at 4/8/20, 7:06 AM:

[jira] [Comment Edited] (LOG4J2-2589) Potential Memory Leak

[ https://issues.apache.org/jira/browse/LOG4J2-2589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17077892#comment-17077892 ] Ralph Goers edited comment on LOG4J2-2589 at 4/8/20, 7:04 AM:

[jira] [Comment Edited] (LOG4J2-2589) Potential Memory Leak

[ https://issues.apache.org/jira/browse/LOG4J2-2589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17077892#comment-17077892 ] Ralph Goers edited comment on LOG4J2-2589 at 4/8/20, 7:04 AM:

[jira] [Comment Edited] (LOG4J2-2589) Potential Memory Leak

[ https://issues.apache.org/jira/browse/LOG4J2-2589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17077892#comment-17077892 ] Ralph Goers edited comment on LOG4J2-2589 at 4/8/20, 7:00 AM: