[
https://issues.apache.org/jira/browse/LOG4J2-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16160628#comment-16160628
]
Ralph Goers commented on LOG4J2-1925:
-
Oracle has closed JDK-8186647 as Won't Fix. No
I don't think that this should be the responsibility of the users. The library
needs to be safe to use even when used "wrongly".
Cases in point:
* we prevent infinite recursion when a collection is logged that contains
itself
* we agreed to catch and suppress exceptions thrown from domain obje
In addition to that a less aggressive (or lazy) mode of operation could
detect rogue recursions and throw in such a situation to prevent deadlocks.
The last mode of operation could do no checks at all, but that mode would
not prevent from deadlocks or infinite recursions at all.
On 10 Sep 2017 4:
I opt that everyone should use the library in a way that makes sure
deadlocks cannot happen. Trying to solve this by fancy "deadlock could
occur" mechanisms feels wrong.
A very restrictive mode of operation could enforce that all arguments
passed into a log event must be limited to immutable primi
[
https://issues.apache.org/jira/browse/LOG4J2-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16160342#comment-16160342
]
Remko Popma commented on LOG4J2-2031:
-
After thinking about this some more, I think i
[
https://issues.apache.org/jira/browse/LOG4J2-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma reassigned LOG4J2-2031:
---
Assignee: Remko Popma
> Messages appear out of order in log file (was: Log4j2 log file not r
[
https://issues.apache.org/jira/browse/LOG4J2-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma updated LOG4J2-2031:
Summary: Messages appear out of order in log file (was: Log4j2 log file not
reflecting application
