[jira] [Commented] (LOG4J2-2133) Log4J 2 appears incompatible with Android platform due to inclusion of Java 9 classes (class file version 53)

[ https://issues.apache.org/jira/browse/LOG4J2-2133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16276133#comment-16276133 ] Ralph Goers commented on LOG4J2-2133: - Yes, it can be an automatic module. But as I said previously,

[jira] [Commented] (LOG4J2-2133) Log4J 2 appears incompatible with Android platform due to inclusion of Java 9 classes (class file version 53)

[ https://issues.apache.org/jira/browse/LOG4J2-2133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16276152#comment-16276152 ] Oleg Kalnichevski commented on LOG4J2-2133: --- @[~ralph_go...@dslextreme.com] I think I have

[jira] [Comment Edited] (LOG4J2-2133) Log4J 2 appears incompatible with Android platform due to inclusion of Java 9 classes (class file version 53)

[ https://issues.apache.org/jira/browse/LOG4J2-2133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16276045#comment-16276045 ] Gary Gregory edited comment on LOG4J2-2133 at 12/3/17 7:38 PM: --- With KISS I

[jira] [Commented] (LOG4J2-2133) Log4J 2 appears incompatible with Android platform due to inclusion of Java 9 classes (class file version 53)

[ https://issues.apache.org/jira/browse/LOG4J2-2133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16276066#comment-16276066 ] Ralph Goers commented on LOG4J2-2133: - In addition to

[jira] [Comment Edited] (LOG4J2-2133) Log4J 2 appears incompatible with Android platform due to inclusion of Java 9 classes (class file version 53)

[ https://issues.apache.org/jira/browse/LOG4J2-2133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16276133#comment-16276133 ] Ralph Goers edited comment on LOG4J2-2133 at 12/3/17 10:28 PM: --- Yes, it can

[jira] [Commented] (LOG4J2-2133) Log4J 2 appears incompatible with Android platform due to inclusion of Java 9 classes (class file version 53)

[ https://issues.apache.org/jira/browse/LOG4J2-2133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16276026#comment-16276026 ] Ralph Goers commented on LOG4J2-2133: - [~jvz] We definitely should link to upstream tickets as well

[jira] [Comment Edited] (LOG4J2-2133) Log4J 2 appears incompatible with Android platform due to inclusion of Java 9 classes (class file version 53)

[ https://issues.apache.org/jira/browse/LOG4J2-2133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16276066#comment-16276066 ] Ralph Goers edited comment on LOG4J2-2133 at 12/3/17 8:14 PM: -- In addition

[jira] [Commented] (LOG4J2-2133) Log4J 2 appears incompatible with Android platform due to inclusion of Java 9 classes (class file version 53)

[ https://issues.apache.org/jira/browse/LOG4J2-2133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16276136#comment-16276136 ] Remko Popma commented on LOG4J2-2133: - [~olegk], would you mind adding version information on the

[jira] [Comment Edited] (LOG4J2-2133) Log4J 2 appears incompatible with Android platform due to inclusion of Java 9 classes (class file version 53)

[ https://issues.apache.org/jira/browse/LOG4J2-2133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16275995#comment-16275995 ] Remko Popma edited comment on LOG4J2-2133 at 12/3/17 10:12 PM: --- [~olegk] I

[jira] [Updated] (LOG4J2-2140) MutableLogEvent instances get reused before flushing when using a NoSql Appender with a bufferSize

[ https://issues.apache.org/jira/browse/LOG4J2-2140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yasas Gunarathne updated LOG4J2-2140: - Summary: MutableLogEvent instances get reused before flushing when using a NoSql

[jira] [Commented] (LOG4J2-2139) JSONLayout ability to rename keys in log output - particularly locationInfo "source"

[ https://issues.apache.org/jira/browse/LOG4J2-2139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16276190#comment-16276190 ] Remko Popma commented on LOG4J2-2139: - Is this really a duplicate of LOG4J2-667? That ticket seems to

[jira] [Comment Edited] (LOG4J2-667) Add customization for JSON Layout keys and values

[ https://issues.apache.org/jira/browse/LOG4J2-667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16276195#comment-16276195 ] Remko Popma edited comment on LOG4J2-667 at 12/4/17 1:38 AM: - Something like a

[jira] [Commented] (LOG4J2-2139) JSONLayout ability to rename keys in log output - particularly locationInfo "source"

[ https://issues.apache.org/jira/browse/LOG4J2-2139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16276260#comment-16276260 ] Ralph Goers commented on LOG4J2-2139: - This could easily be a duplicate of LOG4J2-667 if we implement

[jira] [Created] (LOG4J2-2140) MutableLogEvent instances get overwritten before flushing when using a NoSql Appender with a bufferSize

Yasas Gunarathne created LOG4J2-2140: Summary: MutableLogEvent instances get overwritten before flushing when using a NoSql Appender with a bufferSize Key: LOG4J2-2140 URL:

[jira] [Updated] (LOG4J2-2140) MutableLogEvent instances get overwritten before flushing when using a NoSql Appender with a bufferSize

[ https://issues.apache.org/jira/browse/LOG4J2-2140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yasas Gunarathne updated LOG4J2-2140: - Description: When using *NoSql* Appender with a *bufferSize* configured

[jira] [Commented] (LOG4J2-667) Add customization for JSON Layout keys and values

[ https://issues.apache.org/jira/browse/LOG4J2-667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16276201#comment-16276201 ] Daniel Kirkdorffer commented on LOG4J2-667: --- I should note that in many cases we find ourselves

[jira] [Commented] (LOG4J2-2139) JSONLayout ability to rename keys in log output - particularly locationInfo "source"

[ https://issues.apache.org/jira/browse/LOG4J2-2139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16276193#comment-16276193 ] Daniel Kirkdorffer commented on LOG4J2-2139: There is a little overlap between the two

[jira] [Updated] (LOG4J2-2140) MutableLogEvent instances get overwritten before flushing when using a NoSql Appender with a bufferSize

[ https://issues.apache.org/jira/browse/LOG4J2-2140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yasas Gunarathne updated LOG4J2-2140: - Description: When using *NoSql* Appender with a *bufferSize* configured

[jira] [Comment Edited] (LOG4J2-667) Add customization for JSON Layout keys and values

[ https://issues.apache.org/jira/browse/LOG4J2-667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16276180#comment-16276180 ] Daniel Kirkdorffer edited comment on LOG4J2-667 at 12/4/17 12:47 AM: -

[jira] [Commented] (LOG4J2-2139) JSONLayout ability to rename keys in log output - particularly locationInfo "source"

[ https://issues.apache.org/jira/browse/LOG4J2-2139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16276212#comment-16276212 ] Remko Popma commented on LOG4J2-2139: - Daniel, I briefly investigated what would be involved to

[jira] [Commented] (LOG4J2-2139) JSONLayout ability to rename keys in log output - particularly locationInfo "source"

[ https://issues.apache.org/jira/browse/LOG4J2-2139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16276219#comment-16276219 ] Daniel Kirkdorffer commented on LOG4J2-2139: Yes, I kind of suspect it isn't going to be an

[jira] [Commented] (LOG4J2-667) Add customization for JSON Layout keys and values

[ https://issues.apache.org/jira/browse/LOG4J2-667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16276249#comment-16276249 ] Ralph Goers commented on LOG4J2-667: [~rem...@yahoo.com] Yup, that sounds like exactly what I had in

[jira] [Updated] (LOG4J2-2140) MutableLogEvent instances get overwritten before flushing when using a NoSql Appender with a bufferSize

[ https://issues.apache.org/jira/browse/LOG4J2-2140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yasas Gunarathne updated LOG4J2-2140: - Description: When using *NoSql* Appender with a *bufferSize* configured

[jira] [Commented] (LOG4J2-2140) MutableLogEvent instances get reused before flushing when using a NoSql Appender with a bufferSize

[ https://issues.apache.org/jira/browse/LOG4J2-2140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16276299#comment-16276299 ] Remko Popma commented on LOG4J2-2140: - This reminds me of LOG4J2-2060 which was fixed in Log4j

[jira] [Commented] (LOG4J2-2140) MutableLogEvent instances get reused before flushing when using a NoSql Appender with a bufferSize

[ https://issues.apache.org/jira/browse/LOG4J2-2140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16276409#comment-16276409 ] Yasas Gunarathne commented on LOG4J2-2140: -- Thank you very much for the prompt reply. Issue is

[jira] [Updated] (LOG4J2-2140) MutableLogEvent instances get reused before flushing when using a NoSql Appender with a bufferSize

[ https://issues.apache.org/jira/browse/LOG4J2-2140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yasas Gunarathne updated LOG4J2-2140: - Fix Version/s: 2.10.0 > MutableLogEvent instances get reused before flushing when using

[jira] [Resolved] (LOG4J2-2139) JSONLayout ability to rename keys in log output - particularly locationInfo "source"

[ https://issues.apache.org/jira/browse/LOG4J2-2139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal resolved LOG4J2-2139. Resolution: Duplicate > JSONLayout ability to rename keys in log output - particularly

[jira] [Commented] (LOG4J2-2133) Log4J 2 appears incompatible with Android platform due to inclusion of Java 9 classes (class file version 53)

[ https://issues.apache.org/jira/browse/LOG4J2-2133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16275995#comment-16275995 ] Ralph Goers commented on LOG4J2-2133: - [~olegk] I think this problem is to get worse for Android

[jira] [Comment Edited] (LOG4J2-2133) Log4J 2 appears incompatible with Android platform due to inclusion of Java 9 classes (class file version 53)

[ https://issues.apache.org/jira/browse/LOG4J2-2133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16275995#comment-16275995 ] Ralph Goers edited comment on LOG4J2-2133 at 12/3/17 4:47 PM: -- [~olegk] I

[jira] [Commented] (LOG4J2-2133) Log4J 2 appears incompatible with Android platform due to inclusion of Java 9 classes (class file version 53)

[ https://issues.apache.org/jira/browse/LOG4J2-2133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16276017#comment-16276017 ] Ralph Goers commented on LOG4J2-2133: - I don't see how KISS applies to module-info. KISS means use

[jira] [Comment Edited] (LOG4J2-2133) Log4J 2 appears incompatible with Android platform due to inclusion of Java 9 classes (class file version 53)

[ https://issues.apache.org/jira/browse/LOG4J2-2133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16276017#comment-16276017 ] Ralph Goers edited comment on LOG4J2-2133 at 12/3/17 6:08 PM: -- I don't see

[jira] [Commented] (LOG4J2-2133) Log4J 2 appears incompatible with Android platform due to inclusion of Java 9 classes (class file version 53)

[ https://issues.apache.org/jira/browse/LOG4J2-2133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16276024#comment-16276024 ] Matt Sicker commented on LOG4J2-2133: - While JSON might be more common in the wild, I think adding