Re: Jenkins build became unstable: Log4j 2.x #1985

Weird: I only changed docs... Maybe this test is also vulnerable to timing issues... Sent from my iPhone > On 2016/06/01, at 0:18, Matt Sicker wrote: > > These look like real test failures this time. > >> On 31 May 2016 at 10:14, Apache Jenkins Server >> wrote: >> See

[jira] [Commented] (LOG4J2-1401) Support changing the log level for all messages related to some domain object

[ https://issues.apache.org/jira/browse/LOG4J2-1401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15307922#comment-15307922 ] Ralph Goers commented on LOG4J2-1401: - I don't remember if I created a Jira, but I ha

Re: Jenkins build became unstable: Log4j 2.x #1985

These look like real test failures this time. On 31 May 2016 at 10:14, Apache Jenkins Server wrote: > See > > > - > To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.a

Jenkins build became unstable: Log4j 2.x #1985

See - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org

[jira] [Commented] (LOG4J2-1401) Support changing the log level for all messages related to some domain object

[ https://issues.apache.org/jira/browse/LOG4J2-1401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15307838#comment-15307838 ] Remko Popma commented on LOG4J2-1401: - I will keep it in mind. Looks like there is at

[jira] [Commented] (LOG4J2-1401) Support changing the log level for all messages related to some domain object

[ https://issues.apache.org/jira/browse/LOG4J2-1401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15307715#comment-15307715 ] Mikael Ståldal commented on LOG4J2-1401: If you are going to work on ThreadContex

[jira] [Created] (LOG4J2-1401) Support changing the log level for all messages related to some domain object

Remko Popma created LOG4J2-1401: --- Summary: Support changing the log level for all messages related to some domain object Key: LOG4J2-1401 URL: https://issues.apache.org/jira/browse/LOG4J2-1401 Project:

[jira] [Commented] (LOG4J2-1390) Remove workaround for Kafka close timeout

[ https://issues.apache.org/jira/browse/LOG4J2-1390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15307700#comment-15307700 ] Remko Popma commented on LOG4J2-1390: - I agree that keeping the workaround is a good

[jira] [Commented] (LOG4J2-1397) Support ByteBufferLayout

[ https://issues.apache.org/jira/browse/LOG4J2-1397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15307652#comment-15307652 ] Remko Popma commented on LOG4J2-1397: - Linking to LOG4J2-1305 which allows binary log

[jira] [Resolved] (LOG4J2-1390) Remove workaround for Kafka close timeout

[ https://issues.apache.org/jira/browse/LOG4J2-1390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal resolved LOG4J2-1390. Resolution: Later We should keep support for Kafka client library version 0.8 for a while.

[jira] [Commented] (LOG4J2-1390) Remove workaround for Kafka close timeout

[ https://issues.apache.org/jira/browse/LOG4J2-1390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15307436#comment-15307436 ] Mikael Ståldal commented on LOG4J2-1390: According to a Kafka project member, usi

[jira] [Commented] (LOG4J2-1395) Faster Console appender

[ https://issues.apache.org/jira/browse/LOG4J2-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15307399#comment-15307399 ] Mikael Ståldal commented on LOG4J2-1395: So this gives about 5x performance boost

[jira] [Commented] (LOG4J2-1395) Faster Console appender

[ https://issues.apache.org/jira/browse/LOG4J2-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15307392#comment-15307392 ] Mikael Ståldal commented on LOG4J2-1395: My results with Java 8 on Linux. 1 thre