Build failed in Jenkins: Log4j 2 2.x #3856

See Changes: [rgoers] LOG4J2-2586 - remove unnecessary log event -- [...truncated 1.16 MB...] Uploaded:

Build failed in Jenkins: Log4j 2 3.x #379

See Changes: [rgoers] LOG4J2-2586 - remove unnecessary log event -- [...truncated 1.62 MB...] [JENKINS] Archiving

[jira] [Commented] (LOG4J2-2586) TCP Appender should support a host name resolving to multiple IP addresses

[ https://issues.apache.org/jira/browse/LOG4J2-2586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16814879#comment-16814879 ] ASF subversion and git services commented on LOG4J2-2586: - Commit

[jira] [Commented] (LOG4J2-2586) TCP Appender should support a host name resolving to multiple IP addresses

[ https://issues.apache.org/jira/browse/LOG4J2-2586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16814878#comment-16814878 ] ASF subversion and git services commented on LOG4J2-2586: - Commit

Build failed in Jenkins: Log4j 2 2.x #3855

See Changes: [rgoers] LOG4J2-2586 - TCP Appender should support a host name resolving to -- [...truncated 1.16 MB...] Deploying the main artifact

Jenkins build became unstable: Log4j 2 3.x #378

See

[jira] [Closed] (LOG4J2-2586) TCP Appender should support a host name resolving to multiple IP addresses

[ https://issues.apache.org/jira/browse/LOG4J2-2586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers closed LOG4J2-2586. --- Resolution: Fixed Fix Version/s: 2.12.0 > TCP Appender should support a host name resolving

[jira] [Commented] (LOG4J2-2586) TCP Appender should support a host name resolving to multiple IP addresses

[ https://issues.apache.org/jira/browse/LOG4J2-2586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16814610#comment-16814610 ] ASF subversion and git services commented on LOG4J2-2586: - Commit

[jira] [Commented] (LOG4J2-2586) TCP Appender should support a host name resolving to multiple IP addresses

[ https://issues.apache.org/jira/browse/LOG4J2-2586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16814609#comment-16814609 ] ASF subversion and git services commented on LOG4J2-2586: - Commit

[jira] [Commented] (LOG4J2-636) IOException: Stream Closed RollingRandomAccessFile

[ https://issues.apache.org/jira/browse/LOG4J2-636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16814584#comment-16814584 ] Ralph Goers commented on LOG4J2-636: [~Aaron Awakening] That reasoning seems plausible.

[jira] [Comment Edited] (LOG4J2-2587) Deadlock Bug

[ https://issues.apache.org/jira/browse/LOG4J2-2587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16814521#comment-16814521 ] Ralph Goers edited comment on LOG4J2-2587 at 4/10/19 3:10 PM: -- Looking at

[jira] [Commented] (LOG4J2-2587) Deadlock Bug

[ https://issues.apache.org/jira/browse/LOG4J2-2587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16814521#comment-16814521 ] Ralph Goers commented on LOG4J2-2587: - Looking at the stack trace I find myself wondering why you

[jira] [Commented] (LOG4J2-636) IOException: Stream Closed RollingRandomAccessFile

[ https://issues.apache.org/jira/browse/LOG4J2-636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16814500#comment-16814500 ] Gary Gregory commented on LOG4J2-636: - It would be nice if we'd normalize the path before using it so

[jira] [Commented] (LOG4J2-2587) Deadlock Bug

[ https://issues.apache.org/jira/browse/LOG4J2-2587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16814498#comment-16814498 ] Gary Gregory commented on LOG4J2-2587: -- [~aakinde], Version 2.7 is quite an old version. Please

[jira] [Created] (LOG4J2-2587) Deadlock Bug

Adetunji Akinde created LOG4J2-2587: --- Summary: Deadlock Bug Key: LOG4J2-2587 URL: https://issues.apache.org/jira/browse/LOG4J2-2587 Project: Log4j 2 Issue Type: Bug Components: