buildbot exception in ASF Buildbot on log4j2-nightly

The Buildbot has detected a build exception on builder log4j2-nightly while building ASF Buildbot. Full details are available at: http://ci.apache.org/builders/log4j2-nightly/builds/75 Buildbot URL: http://ci.apache.org/ Buildslave for this Build: lares_ubuntu Build Reason: The Nightly

[jira] [Commented] (LOG4J2-1161) Builder like pattern to add values to MapMessage

[ https://issues.apache.org/jira/browse/LOG4J2-1161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14960415#comment-14960415 ] Mikael Ståldal commented on LOG4J2-1161: The "with" method need to be in each subclass in order

[jira] [Updated] (LOG4J2-1163) ERROR appender Failover has no parameter that matches element Failovers

[ https://issues.apache.org/jira/browse/LOG4J2-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Schröder updated LOG4J2-1163: Description: We are using the attached configuration with log4j2, which tries to use a

[jira] [Created] (LOG4J2-1163) ERROR appender Failover has no parameter that matches element Failovers

Martin Schröder created LOG4J2-1163: --- Summary: ERROR appender Failover has no parameter that matches element Failovers Key: LOG4J2-1163 URL: https://issues.apache.org/jira/browse/LOG4J2-1163

[jira] [Updated] (LOG4J2-1163) ERROR appender Failover has no parameter that matches element Failovers

[ https://issues.apache.org/jira/browse/LOG4J2-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Schröder updated LOG4J2-1163: Attachment: log4j2.xml > ERROR appender Failover has no parameter that matches element

[jira] [Commented] (LOG4J2-1161) Builder like pattern to add values to MapMessage

[ https://issues.apache.org/jira/browse/LOG4J2-1161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14960410#comment-14960410 ] Mikael Ståldal commented on LOG4J2-1161: I am all for a better name than "withValue". Is just

[jira] [Updated] (LOG4J2-1163) ERROR appender Failover has no parameter that matches element Failovers

[ https://issues.apache.org/jira/browse/LOG4J2-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Schröder updated LOG4J2-1163: Description: We are using the attached configuration with log4j2, which tries to use a

[jira] [Commented] (LOG4J2-381) Changes in SizeBasedTriggeringPolicy has no effects when automatic reconfiguration is on.

[ https://issues.apache.org/jira/browse/LOG4J2-381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14960539#comment-14960539 ] Alexander Khokhlov commented on LOG4J2-381: --- [~ralph.go...@dslextreme.com], do you have plans to

[jira] [Closed] (LOG4J2-581) No header output in RollingRandomAccessFile

[ https://issues.apache.org/jira/browse/LOG4J2-581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Khokhlov closed LOG4J2-581. - All ok > No header output in RollingRandomAccessFile >

[jira] [Commented] (LOG4J2-1087) Reload of RolloverStrategy doesn't work

[ https://issues.apache.org/jira/browse/LOG4J2-1087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14960603#comment-14960603 ] Alexander Khokhlov commented on LOG4J2-1087: I have a similar problem. See #LOG4J2-381. BTW,

[jira] [Comment Edited] (LOG4J2-381) Changes in SizeBasedTriggeringPolicy has no effects when automatic reconfiguration is on.

[ https://issues.apache.org/jira/browse/LOG4J2-381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14960539#comment-14960539 ] Alexander Khokhlov edited comment on LOG4J2-381 at 10/16/15 11:33 AM: --

Re: Is there anything besides the Logger name that uniquely identifies a Logger?

The LocalizedMessageFactory constructor taking a ResourceBundle does raise an issue. Java 8 added a getBaseBundleName() method, but there's nothing for 7. On 15 October 2015 at 17:42, Gary Gregory wrote: > Out of all the message factories, it looks like