rgoers commented on pull request #365:
URL: https://github.com/apache/logging-log4j2/pull/365#issuecomment-650489261
This looks fine. I assume the same problem exists on the release-2.x branch.
This is an automated message fr
[
https://issues.apache.org/jira/browse/LOG4J2-2879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ayush Kumar updated LOG4J2-2879:
Description:
The extended stack trace value in jsonlayout can be extremely long, especially
if st
[
https://issues.apache.org/jira/browse/LOG4J2-2879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ayush Kumar updated LOG4J2-2879:
Description:
The extended stack trace value in jsonlayout can be extremely long, especially
if st
[
https://issues.apache.org/jira/browse/LOGCXX-510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17146677#comment-17146677
]
Robert Middleton commented on LOGCXX-510:
-
As far as I am aware, the dependencies
Ayush Kumar created LOG4J2-2879:
---
Summary: Large extendedStackTrace in JsonLayout
Key: LOG4J2-2879
URL: https://issues.apache.org/jira/browse/LOG4J2-2879
Project: Log4j 2
Issue Type: Improvemen
Hoffs opened a new pull request #365:
URL: https://github.com/apache/logging-log4j2/pull/365
The lower lookup example has extra opening bracket that renders the
configuration invalid.
This is an automated message from the Ap
[
https://issues.apache.org/jira/browse/LOGCXX-511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17146372#comment-17146372
]
Rajesh commented on LOGCXX-511:
---
Thank you so much "[~mattsicker]. I have sent mail to
dev
