[jira] [Commented] (LOG4J2-2058) java.locale.providers set to HOST causes Log4j2 to crash in Java 9

[ https://issues.apache.org/jira/browse/LOG4J2-2058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16190563#comment-16190563 ] Gary Gregory commented on LOG4J2-2058: -- FYI: Applying this patch: {noformat} diff --git

[jira] [Issue Comment Deleted] (LOG4J2-2058) java.locale.providers set to HOST causes Log4j2 to crash in Java 9

[ https://issues.apache.org/jira/browse/LOG4J2-2058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-2058: - Comment: was deleted (was: What do your imports look like? Are you intending to use the Log4j 1

[jira] [Commented] (LOG4J2-2058) java.locale.providers set to HOST causes Log4j2 to crash in Java 9

[ https://issues.apache.org/jira/browse/LOG4J2-2058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16190556#comment-16190556 ] Gary Gregory commented on LOG4J2-2058: -- What do your imports look like? Are you intending to use the

[jira] [Closed] (LOG4NET-578) Type is not resolved for member 'log4net.Util.PropertiesDictionary'

[ https://issues.apache.org/jira/browse/LOG4NET-578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominik Psenner closed LOG4NET-578. --- Resolution: Not A Bug Assignee: Dominik Psenner Looks like the appdomain cant find the

[jira] [Comment Edited] (LOG4NET-578) Type is not resolved for member 'log4net.Util.PropertiesDictionary'

[ https://issues.apache.org/jira/browse/LOG4NET-578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16189977#comment-16189977 ] Blake edited comment on LOG4NET-578 at 10/3/17 5:06 PM: Unfortunately, this

[jira] [Commented] (LOG4NET-578) Type is not resolved for member 'log4net.Util.PropertiesDictionary'

[ https://issues.apache.org/jira/browse/LOG4NET-578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16189977#comment-16189977 ] Blake commented on LOG4NET-578: --- Unfortunately, this exception is resulting in 500 internal server error

[jira] [Updated] (LOG4NET-578) Type is not resolved for member 'log4net.Util.PropertiesDictionary'

[ https://issues.apache.org/jira/browse/LOG4NET-578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Blake updated LOG4NET-578: -- Summary: Type is not resolved for member 'log4net.Util.PropertiesDictionary' (was: Type is not resolved for

[jira] [Created] (LOG4NET-578) Type is not resolved for member 'log4net.Util.PropertiesDictionary,log4net

Blake created LOG4NET-578: - Summary: Type is not resolved for member 'log4net.Util.PropertiesDictionary,log4net Key: LOG4NET-578 URL: https://issues.apache.org/jira/browse/LOG4NET-578 Project: Log4net

Re: [jira] [Commented] (LOG4J2-1479) Help Apache Spark project to upgrade from Log4j 1.x to 2.x

ZooKeeper uses Log4j1.2 it needs some love too. I read end of life was 2015? On Oct 3, 2017 9:12 AM, "Remko Popma (JIRA)" wrote: > > [ https://issues.apache.org/jira/browse/LOG4J2-1479?page= > com.atlassian.jira.plugin.system.issuetabpanels:comment- >

[jira] [Commented] (LOG4J2-1479) Help Apache Spark project to upgrade from Log4j 1.x to 2.x

[ https://issues.apache.org/jira/browse/LOG4J2-1479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16189914#comment-16189914 ] Remko Popma commented on LOG4J2-1479: - If people are looking to help out, the most proactive way to

[jira] [Commented] (LOG4J2-1479) Help Apache Spark project to upgrade from Log4j 1.x to 2.x

[ https://issues.apache.org/jira/browse/LOG4J2-1479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16189787#comment-16189787 ] Jorge Sanchez commented on LOG4J2-1479: --- Is there anything that can be done from a LOG4J2

[jira] [Reopened] (LOG4NET-577) Log4net gives error on UpdateLogFilePath when logfilepath changes dynamically for an appender.

[ https://issues.apache.org/jira/browse/LOG4NET-577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nilesh R Deo reopened LOG4NET-577: -- Hi Dominik, Can you please elaborate on the edge cases that we need to take care of when we