[jira] [Commented] (LOG4J2-2031) Messages appear out of order in log file (was: Log4j2 log file not reflecting application log function calls)

2017-10-02 Thread Colin McDowell (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16187779#comment-16187779 ] Colin McDowell commented on LOG4J2-2031: Hi Remko, Appreciate the fix :) Is there an expected

[jira] [Commented] (LOG4J2-2031) Messages appear out of order in log file (was: Log4j2 log file not reflecting application log function calls)

2017-09-20 Thread ASF subversion and git services (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16173351#comment-16173351 ] ASF subversion and git services commented on LOG4J2-2031: - Commit

[jira] [Commented] (LOG4J2-2031) Messages appear out of order in log file (was: Log4j2 log file not reflecting application log function calls)

2017-09-20 Thread ASF subversion and git services (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16173352#comment-16173352 ] ASF subversion and git services commented on LOG4J2-2031: - Commit

[jira] [Commented] (LOG4J2-2031) Messages appear out of order in log file (was: Log4j2 log file not reflecting application log function calls)

2017-09-20 Thread ASF subversion and git services (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16173212#comment-16173212 ] ASF subversion and git services commented on LOG4J2-2031: - Commit

[jira] [Commented] (LOG4J2-2031) Messages appear out of order in log file (was: Log4j2 log file not reflecting application log function calls)

2017-09-20 Thread ASF subversion and git services (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16173196#comment-16173196 ] ASF subversion and git services commented on LOG4J2-2031: - Commit

[jira] [Commented] (LOG4J2-2031) Messages appear out of order in log file (was: Log4j2 log file not reflecting application log function calls)

2017-09-20 Thread ASF subversion and git services (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16173197#comment-16173197 ] ASF subversion and git services commented on LOG4J2-2031: - Commit

[jira] [Commented] (LOG4J2-2031) Messages appear out of order in log file (was: Log4j2 log file not reflecting application log function calls)

2017-09-11 Thread Colin McDowell (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16161643#comment-16161643 ] Colin McDowell commented on LOG4J2-2031: I looked up the Log4j2 documentation. Appears to have

Re: [jira] [Commented] (LOG4J2-2031) Messages appear out of order in log file (was: Log4j2 log file not reflecting application log function calls)

2017-09-10 Thread Remko Popma
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

Re: [jira] [Commented] (LOG4J2-2031) Messages appear out of order in log file (was: Log4j2 log file not reflecting application log function calls)

2017-09-10 Thread Dominik Psenner
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

Re: [jira] [Commented] (LOG4J2-2031) Messages appear out of order in log file (was: Log4j2 log file not reflecting application log function calls)

2017-09-10 Thread Dominik Psenner
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

[jira] [Commented] (LOG4J2-2031) Messages appear out of order in log file (was: Log4j2 log file not reflecting application log function calls)

2017-09-10 Thread Remko Popma (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16160342#comment-16160342 ] Remko Popma commented on LOG4J2-2031: - After thinking about this some more, I think it should be