[jira] [Commented] (LOG4J2-2873) Failed to parse json string to LogEvent when massage type is MapMessage

[ https://issues.apache.org/jira/browse/LOG4J2-2873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17141585#comment-17141585 ] Ralph Goers commented on LOG4J2-2873: - I am very confused. In the issue description

[jira] [Commented] (LOG4J2-2873) Failed to parse json string to LogEvent when massage type is MapMessage

[ https://issues.apache.org/jira/browse/LOG4J2-2873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17141581#comment-17141581 ] Alla Gofman commented on LOG4J2-2873: - On server side I use PatternLayout with %map

[jira] [Updated] (LOG4J2-2873) Failed to parse json string to LogEvent when massage type is MapMessage

[ https://issues.apache.org/jira/browse/LOG4J2-2873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alla Gofman updated LOG4J2-2873: Description: I create LogEvent where message is of type MapMessage (key-value pairs). I send this

[jira] [Updated] (LOG4J2-2873) Failed to parse json string to LogEvent when massage type is MapMessage

[ https://issues.apache.org/jira/browse/LOG4J2-2873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alla Gofman updated LOG4J2-2873: Description: I create LogEvent where message is of type MapMessage (key-value pairs). I send this

[jira] [Updated] (LOG4J2-2873) Failed to parse json string to LogEvent when massage type is MapMessage

[ https://issues.apache.org/jira/browse/LOG4J2-2873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alla Gofman updated LOG4J2-2873: Description: I create LogEvent where message is of type MapMessage (key-value pairs). I send this

[CI][FAILURE] log4j/master#84 has potential issues

There is a build failure in log4j/master. Build: https://builds.apache.org/job/log4j/job/master/84/ Logs: https://builds.apache.org/job/log4j/job/master/84/console Test results: https://builds.apache.org/job/log4j/job/master/84/testReport/ Changes: https://builds.apache.org/job/log4j/job/master/8

[jira] [Commented] (LOGCXX-322) Crashes on exit from multithreaded program using log4cxx

[ https://issues.apache.org/jira/browse/LOGCXX-322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17141530#comment-17141530 ] Mark commented on LOGCXX-322: - What do you think to provide a "dispose" method for the aprini

[jira] [Closed] (LOG4J2-2877) Kubernetes Lookup fails to get container and image information

[ https://issues.apache.org/jira/browse/LOG4J2-2877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers closed LOG4J2-2877. --- Fix Version/s: 2.14.0 Resolution: Fixed > Kubernetes Lookup fails to get container and image

[jira] [Commented] (LOG4J2-2877) Kubernetes Lookup fails to get container and image information

[ https://issues.apache.org/jira/browse/LOG4J2-2877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17141522#comment-17141522 ] ASF subversion and git services commented on LOG4J2-2877: - Commi

[jira] [Commented] (LOG4J2-2877) Kubernetes Lookup fails to get container and image information

[ https://issues.apache.org/jira/browse/LOG4J2-2877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17141521#comment-17141521 ] ASF subversion and git services commented on LOG4J2-2877: - Commi

[GitHub] [logging-log4cxx] ams-tschoening merged pull request #26: Fix missing const in method getThreshold

ams-tschoening merged pull request #26: URL: https://github.com/apache/logging-log4cxx/pull/26 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL abov

[GitHub] [logging-log4cxx] ams-tschoening commented on pull request #26: Fix missing const in method getThreshold

ams-tschoening commented on pull request #26: URL: https://github.com/apache/logging-log4cxx/pull/26#issuecomment-647131780 Thanks for fixing! As this is a minor change, I won't update `changes.xml` for now. This is an autom

[CI][FAILURE] log4j/release-2.x#66 has potential issues

There is a build failure in log4j/release-2.x. Build: https://builds.apache.org/job/log4j/job/release-2.x/66/ Logs: https://builds.apache.org/job/log4j/job/release-2.x/66/console Test results: https://builds.apache.org/job/log4j/job/release-2.x/66/testReport/ Changes: https://builds.apache.org/jo