[jira] [Commented] (LOG4J2-1675) Compile-time incompatibility regarding SimpleMessage

[ https://issues.apache.org/jira/browse/LOG4J2-1675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16042303#comment-16042303 ] Ralph Goers commented on LOG4J2-1675: - Are we going to do anything with this or shoul

[jira] [Commented] (LOG4J2-1727) Calling static method during re-/undeploy causes memory leak in Tomcat

[ https://issues.apache.org/jira/browse/LOG4J2-1727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16042302#comment-16042302 ] Ralph Goers commented on LOG4J2-1727: - Log4j documents that it must be shutdown last

[jira] [Commented] (LOG4J2-1745) Add support for multi-release jars for JDK9+

[ https://issues.apache.org/jira/browse/LOG4J2-1745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16042300#comment-16042300 ] Ralph Goers commented on LOG4J2-1745: - I tried using multi-release jars and ran into

[jira] [Commented] (LOG4J2-1746) Add JDK9 build to Jenkins

[ https://issues.apache.org/jira/browse/LOG4J2-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16042299#comment-16042299 ] Ralph Goers commented on LOG4J2-1746: - I don't think we need this any more. > Add JD

[jira] [Commented] (LOG4J2-1793) Why there can't get thrown from LogEvent

[ https://issues.apache.org/jira/browse/LOG4J2-1793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16042297#comment-16042297 ] Ralph Goers commented on LOG4J2-1793: - Is there anything to do on this or can it be c

[jira] [Assigned] (LOG4J2-1794) Programmatic reconfiguration doesn't affect existing loggers

[ https://issues.apache.org/jira/browse/LOG4J2-1794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers reassigned LOG4J2-1794: --- Assignee: Ralph Goers > Programmatic reconfiguration doesn't affect existing loggers > -

[jira] [Assigned] (LOG4J2-1798) InterruptedException on RollingFileManager#rollover()

[ https://issues.apache.org/jira/browse/LOG4J2-1798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers reassigned LOG4J2-1798: --- Assignee: Ralph Goers > InterruptedException on RollingFileManager#rollover() >

[jira] [Assigned] (LOG4J2-1925) Having log4j-core on the compile classpath somehow breaks compilation even if I'm not calling it

[ https://issues.apache.org/jira/browse/LOG4J2-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers reassigned LOG4J2-1925: --- Assignee: Ralph Goers > Having log4j-core on the compile classpath somehow breaks compilatio

[jira] [Assigned] (LOG4J2-1906) DirectWriteRolloverStrategy not properly creating files

[ https://issues.apache.org/jira/browse/LOG4J2-1906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers reassigned LOG4J2-1906: --- Assignee: Ralph Goers > DirectWriteRolloverStrategy not properly creating files > --

[jira] [Assigned] (LOG4J2-1916) Nullpointer with DirectWriteRolloverStrategy

[ https://issues.apache.org/jira/browse/LOG4J2-1916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers reassigned LOG4J2-1916: --- Assignee: Ralph Goers > Nullpointer with DirectWriteRolloverStrategy > -

[jira] [Assigned] (LOG4J2-1894) Potential data race in ReconfigurationDeadlockTest

[ https://issues.apache.org/jira/browse/LOG4J2-1894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers reassigned LOG4J2-1894: --- Assignee: Ralph Goers > Potential data race in ReconfigurationDeadlockTest > ---

[jira] [Assigned] (LOG4J2-1928) RollingRandomAccessFileAppender with DirectWriteRolloverStrategy requires a fileName

[ https://issues.apache.org/jira/browse/LOG4J2-1928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers reassigned LOG4J2-1928: --- Assignee: Ralph Goers > RollingRandomAccessFileAppender with DirectWriteRolloverStrategy req

[jira] [Commented] (LOG4J2-1894) Potential data race in ReconfigurationDeadlockTest

[ https://issues.apache.org/jira/browse/LOG4J2-1894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16042293#comment-16042293 ] Ralph Goers commented on LOG4J2-1894: - There is a race here but it is accounted for b

[jira] [Commented] (LOG4J2-1729) CronTriggeringPolicy using "evaluateOnStartup" cause dead lock

[ https://issues.apache.org/jira/browse/LOG4J2-1729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16042285#comment-16042285 ] Ralph Goers commented on LOG4J2-1729: - Can you validate that this still happens with

[jira] [Assigned] (LOG4J2-1828) add support for prudent mode in Log4j 2

[ https://issues.apache.org/jira/browse/LOG4J2-1828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers reassigned LOG4J2-1828: --- Assignee: Ralph Goers > add support for prudent mode in Log4j 2 > --

[jira] [Commented] (LOG4J2-1841) Problems with consequences after LOG4J2-248

[ https://issues.apache.org/jira/browse/LOG4J2-1841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16042254#comment-16042254 ] Ralph Goers commented on LOG4J2-1841: - As I suggested in LOG4J2-248, this behavior sh

Re: [log4j2] org.apache.logging.log4j.message.MapMessage String vs. Object values.

Is it possible to use a FallbackAppender to fall back to a recreated version of itself? If not, perhaps a sort of RecoverableAppender wrapper or something may be useful. On 7 June 2017 at 07:41, Apache wrote: > The reason managers were split from the appender sis because appender are > recreated

[jira] [Commented] (LOG4J2-1934) JMS Appender does not know how to recover from a broken connection

[ https://issues.apache.org/jira/browse/LOG4J2-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16041816#comment-16041816 ] Matt Sicker commented on LOG4J2-1934: - As a workaround, can't you use a failover brok

Re: [log4j2] org.apache.logging.log4j.message.MapMessage String vs. Object values.

The reason managers were split from the appender sis because appender are recreated during reconfiguration while managers are reused. Ralph > On Jun 7, 2017, at 1:11 AM, Gary Gregory wrote: > > Hi All: > > I've completed all the clean ups I think were needed in the > GenericMapMessageSimple b

[logging-log4net] Git Push Summary

Hi, I just did a fresh clone of the log4net repository and noticed that this head had appeared in the git repository. I don't know where it came from but it looks like it was an artifact that was still there because of the svn -> git migration. The parents of this commit looked to me like a c

Re: [log4j2] org.apache.logging.log4j.message.MapMessage String vs. Object values.

Hi All: I've completed all the clean ups I think were needed in the GenericMapMessageSimple branch (the no-new-class branch). I will merge to master tomorrow unless I hear otherwise. Then I can look at painful it would be to fix https://issues.apache.org/jira/browse/LOG4J2-1934 Any advice there

[jira] [Created] (LOG4J2-1935) Add with(String, primitive) methods to org.apache.logging.log4j.message.MapMessage

Gary Gregory created LOG4J2-1935: Summary: Add with(String, primitive) methods to org.apache.logging.log4j.message.MapMessage Key: LOG4J2-1935 URL: https://issues.apache.org/jira/browse/LOG4J2-1935 Pr