[jira] [Comment Edited] (LOG4J2-1361) AsyncAppender never recovers from OutOfMemoryError in AsyncThread.run

[ https://issues.apache.org/jira/browse/LOG4J2-1361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15233340#comment-15233340 ] Remko Popma edited comment on LOG4J2-1361 at 4/9/16 4:14 AM: -

[jira] [Commented] (LOG4J2-1361) AsyncAppender never recovers from OutOfMemoryError in AsyncThread.run

[ https://issues.apache.org/jira/browse/LOG4J2-1361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15233340#comment-15233340 ] Remko Popma commented on LOG4J2-1361: - [Async Loggers|http://logging.apache.org/log4j

Re: Jenkins build is back to normal : Log4j 2.x #1857

Build bliss: achieved! Sent from my iPhone > On 2016/04/09, at 10:33, Apache Jenkins Server > wrote: > > See > > > - > To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.a

Jenkins build is back to normal : Log4j 2.x #1857

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

Re: Build failed in Jenkins: Log4j 2.x #1856

Added that server to the list of excluded servers and restarted the build. Ralph > On Apr 8, 2016, at 5:02 PM, Remko Popma wrote: > > Progress! All tests passed. > > The problem is > ERROR: Failed to deploy artifacts: Could not transfer artifact > org.apache.logging.log4j:log4j:pom:2.6-20160

Re: Build failed in Jenkins: Log4j 2.x #1856

Progress! All tests passed. The problem is ERROR: Failed to deploy artifacts: Could not transfer artifact org.apache.logging.log4j:log4j:pom:2.6-20160408.162043-195 from/to apache.snapshots.https (https://repository.apache.org/content/repositories/snapshots): Failed to transfer file: https:/

[jira] [Comment Edited] (LOG4J2-1356) Update GelfLayout to utilize gc-free mechanism for LogEvent processing

[ https://issues.apache.org/jira/browse/LOG4J2-1356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15233173#comment-15233173 ] Remko Popma edited comment on LOG4J2-1356 at 4/8/16 11:57 PM: -

[jira] [Commented] (LOG4J2-1356) Update GelfLayout to utilize gc-free mechanism for LogEvent processing

[ https://issues.apache.org/jira/browse/LOG4J2-1356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15233173#comment-15233173 ] Remko Popma commented on LOG4J2-1356: - I'll try to take a look as soon as I can. Are

Build failed in Jenkins: Log4j 2.x #1856

See Changes: [rpopma] LOG4J2-1291 fix NPE in TextEncoderHelper when system property [rpopma] ignore broken test for now until I figure out underlying cause -- [...truncated 20687 lines...] Tests run

[jira] [Commented] (LOG4J2-1329) API change: let Message.getFormattedMessage() return CharSequence instead of String

[ https://issues.apache.org/jira/browse/LOG4J2-1329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15232416#comment-15232416 ] Mikael Ståldal commented on LOG4J2-1329: It is done now, in branch LOG4J2-1356 >

[jira] [Commented] (LOG4J2-1356) Update GelfLayout to utilize gc-free mechanism for LogEvent processing

[ https://issues.apache.org/jira/browse/LOG4J2-1356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15232101#comment-15232101 ] Mikael Ståldal commented on LOG4J2-1356: [~rem...@yahoo.com] Does this looks good

Jenkins build is still unstable: Log4j 2.x #1855

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

[jira] [Created] (LOG4J2-1361) AsyncAppender never recovers from OutOfMemoryError in AsyncThread.run

Dan Berindei created LOG4J2-1361: Summary: AsyncAppender never recovers from OutOfMemoryError in AsyncThread.run Key: LOG4J2-1361 URL: https://issues.apache.org/jira/browse/LOG4J2-1361 Project: Log4j

[jira] [Comment Edited] (LOG4J2-1350) Circuit Breaker for log system to avoid DOS by recursion

[ https://issues.apache.org/jira/browse/LOG4J2-1350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15231859#comment-15231859 ] Steffen Offermann edited comment on LOG4J2-1350 at 4/8/16 8:26 AM:

[jira] [Commented] (LOG4J2-1350) Circuit Breaker for log system to avoid DOS by recursion

[ https://issues.apache.org/jira/browse/LOG4J2-1350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15231859#comment-15231859 ] Steffen Offermann commented on LOG4J2-1350: --- Our problems looks very much like

[jira] [Commented] (LOG4J2-1350) Circuit Breaker for log system to avoid DOS by recursion

[ https://issues.apache.org/jira/browse/LOG4J2-1350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15231758#comment-15231758 ] Steffen Offermann commented on LOG4J2-1350: --- Sorry, Remko - picked the wrong su

[jira] [Commented] (LOG4J2-1360) Add bridge to JDK9 System.Logger interface

[ https://issues.apache.org/jira/browse/LOG4J2-1360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15231757#comment-15231757 ] Remko Popma commented on LOG4J2-1360: - That JEP reminded me of https://xkcd.com/927/

[jira] [Comment Edited] (LOG4J2-1350) Circuit Breaker for log system to avoid DOS by recursion

[ https://issues.apache.org/jira/browse/LOG4J2-1350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15231692#comment-15231692 ] Steffen Offermann edited comment on LOG4J2-1350 at 4/8/16 7:04 AM:

[jira] [Commented] (LOG4J2-1350) Circuit Breaker for log system to avoid DOS by recursion

[ https://issues.apache.org/jira/browse/LOG4J2-1350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15231749#comment-15231749 ] Remko Popma commented on LOG4J2-1350: - [~SteffenO] My suggestion was to give the Asyn