[jira] [Resolved] (LOG4J2-2858) More flexible configuration of WaitStrategy of Disruptor

[ https://issues.apache.org/jira/browse/LOG4J2-2858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak resolved LOG4J2-2858. -- Fix Version/s: (was: 2.13.3) 2.14.0 Resolution: Fixed Merged int

[jira] [Commented] (LOG4J2-2858) More flexible configuration of WaitStrategy of Disruptor

[ https://issues.apache.org/jira/browse/LOG4J2-2858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17159499#comment-17159499 ] ASF subversion and git services commented on LOG4J2-2858: - Commi

[jira] [Commented] (LOG4J2-2858) More flexible configuration of WaitStrategy of Disruptor

[ https://issues.apache.org/jira/browse/LOG4J2-2858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17159501#comment-17159501 ] ASF subversion and git services commented on LOG4J2-2858: - Commi

[jira] [Commented] (LOG4J2-2858) More flexible configuration of WaitStrategy of Disruptor

[ https://issues.apache.org/jira/browse/LOG4J2-2858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17159500#comment-17159500 ] ASF subversion and git services commented on LOG4J2-2858: - Commi

[CI][FAILURE] log4j/master#105 has potential issues

There is a build failure in log4j/master. Build: https://builds.apache.org/job/log4j/job/master/105/ Logs: https://builds.apache.org/job/log4j/job/master/105/console Test results: https://builds.apache.org/job/log4j/job/master/105/testReport/ Changes: https://builds.apache.org/job/log4j/job/maste

[CI][FAILURE] log4j/master#104 has potential issues

There is a build failure in log4j/master. Build: https://builds.apache.org/job/log4j/job/master/104/ Logs: https://builds.apache.org/job/log4j/job/master/104/console Test results: https://builds.apache.org/job/log4j/job/master/104/testReport/ Changes: https://builds.apache.org/job/log4j/job/maste

[jira] [Commented] (LOG4J2-2858) More flexible configuration of WaitStrategy of Disruptor

[ https://issues.apache.org/jira/browse/LOG4J2-2858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17159479#comment-17159479 ] ASF subversion and git services commented on LOG4J2-2858: - Commi

[jira] [Work logged] (LOG4J2-2858) More flexible configuration of WaitStrategy of Disruptor

[ https://issues.apache.org/jira/browse/LOG4J2-2858?focusedWorklogId=459950&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-459950 ] ASF GitHub Bot logged work on LOG4J2-2858: -- Author: ASF GitHub Bot

[GitHub] [logging-log4j2] carterkozak merged pull request #361: LOG4J2-2858: More flexible configuration of WaitStrategy of Disruptor

carterkozak merged pull request #361: URL: https://github.com/apache/logging-log4j2/pull/361 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above

[GitHub] [logging-log4j2] carterkozak closed pull request #389: LOG4J2-2895: Async logging avoids blocking on Log4jThreads

carterkozak closed pull request #389: URL: https://github.com/apache/logging-log4j2/pull/389 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above

[GitHub] [logging-log4j2] carterkozak commented on pull request #387: LOG4J2-2867: RingBufferLogEventTranslator uses a static ContextDataInjector

carterkozak commented on pull request #387: URL: https://github.com/apache/logging-log4j2/pull/387#issuecomment-659661553 committed to release-2.x and master This is an automated message from the Apache Git Service. To respon

[GitHub] [logging-log4j2] carterkozak closed pull request #387: LOG4J2-2867: RingBufferLogEventTranslator uses a static ContextDataInjector

carterkozak closed pull request #387: URL: https://github.com/apache/logging-log4j2/pull/387 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above

[jira] [Work logged] (LOG4J2-2867) ContextDataProvider will cause concurrent threads blocking at the first logging time

[ https://issues.apache.org/jira/browse/LOG4J2-2867?focusedWorklogId=459948&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-459948 ] ASF GitHub Bot logged work on LOG4J2-2867: -- Author: ASF GitHub Bot

[GitHub] [logging-log4j2] carterkozak commented on pull request #388: LOG4J2-2837: Disruptor and JUL no longer recursively start the AsyncLoggerDisruptor

carterkozak commented on pull request #388: URL: https://github.com/apache/logging-log4j2/pull/388#issuecomment-659661589 committed to release-2.x and master This is an automated message from the Apache Git Service. To respon

[GitHub] [logging-log4j2] carterkozak commented on pull request #389: LOG4J2-2895: Async logging avoids blocking on Log4jThreads

carterkozak commented on pull request #389: URL: https://github.com/apache/logging-log4j2/pull/389#issuecomment-659661612 committed to release-2.x and master This is an automated message from the Apache Git Service. To respon

[GitHub] [logging-log4j2] carterkozak closed pull request #388: LOG4J2-2837: Disruptor and JUL no longer recursively start the AsyncLoggerDisruptor

carterkozak closed pull request #388: URL: https://github.com/apache/logging-log4j2/pull/388 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above

[jira] [Work logged] (LOG4J2-2867) ContextDataProvider will cause concurrent threads blocking at the first logging time

[ https://issues.apache.org/jira/browse/LOG4J2-2867?focusedWorklogId=459947&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-459947 ] ASF GitHub Bot logged work on LOG4J2-2867: -- Author: ASF GitHub Bot

[CI][FAILURE] log4j/master#103 has potential issues

There is a build failure in log4j/master. Build: https://builds.apache.org/job/log4j/job/master/103/ Logs: https://builds.apache.org/job/log4j/job/master/103/console Test results: https://builds.apache.org/job/log4j/job/master/103/testReport/ Changes: https://builds.apache.org/job/log4j/job/maste

[jira] [Commented] (LOG4J2-2837) Fully asynchronous logging results in two disruptors being created

[ https://issues.apache.org/jira/browse/LOG4J2-2837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17159475#comment-17159475 ] ASF subversion and git services commented on LOG4J2-2837: - Commi

[jira] [Commented] (LOG4J2-2895) Async logging should avoid submitting work from Log4jThread threads

[ https://issues.apache.org/jira/browse/LOG4J2-2895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17159474#comment-17159474 ] ASF subversion and git services commented on LOG4J2-2895: - Commi

[jira] [Commented] (LOG4J2-2867) ContextDataProvider will cause concurrent threads blocking at the first logging time

[ https://issues.apache.org/jira/browse/LOG4J2-2867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17159476#comment-17159476 ] ASF subversion and git services commented on LOG4J2-2867: - Commi

[jira] [Closed] (LOG4J2-2895) Async logging should avoid submitting work from Log4jThread threads

[ https://issues.apache.org/jira/browse/LOG4J2-2895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak closed LOG4J2-2895. > Async logging should avoid submitting work from Log4jThread threads > --

[jira] [Updated] (LOG4J2-2895) Async logging should avoid submitting work from Log4jThread threads

[ https://issues.apache.org/jira/browse/LOG4J2-2895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak updated LOG4J2-2895: - Fix Version/s: 2.14.0 > Async logging should avoid submitting work from Log4jThread threads > --

[jira] [Resolved] (LOG4J2-2837) Fully asynchronous logging results in two disruptors being created

[ https://issues.apache.org/jira/browse/LOG4J2-2837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak resolved LOG4J2-2837. -- Resolution: Fixed > Fully asynchronous logging results in two disruptors being created > -

[jira] [Updated] (LOG4J2-2837) Fully asynchronous logging results in two disruptors being created

[ https://issues.apache.org/jira/browse/LOG4J2-2837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak updated LOG4J2-2837: - Fix Version/s: 2.14.0 > Fully asynchronous logging results in two disruptors being created > ---

[jira] [Resolved] (LOG4J2-2895) Async logging should avoid submitting work from Log4jThread threads

[ https://issues.apache.org/jira/browse/LOG4J2-2895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak resolved LOG4J2-2895. -- Resolution: Fixed > Async logging should avoid submitting work from Log4jThread threads >

[jira] [Closed] (LOG4J2-2837) Fully asynchronous logging results in two disruptors being created

[ https://issues.apache.org/jira/browse/LOG4J2-2837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak closed LOG4J2-2837. > Fully asynchronous logging results in two disruptors being created > ---

[jira] [Commented] (LOG4J2-2895) Async logging should avoid submitting work from Log4jThread threads

[ https://issues.apache.org/jira/browse/LOG4J2-2895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17159470#comment-17159470 ] ASF subversion and git services commented on LOG4J2-2895: - Commi

[jira] [Commented] (LOG4J2-2867) ContextDataProvider will cause concurrent threads blocking at the first logging time

[ https://issues.apache.org/jira/browse/LOG4J2-2867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17159472#comment-17159472 ] ASF subversion and git services commented on LOG4J2-2867: - Commi

[jira] [Commented] (LOG4J2-2837) Fully asynchronous logging results in two disruptors being created

[ https://issues.apache.org/jira/browse/LOG4J2-2837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17159471#comment-17159471 ] ASF subversion and git services commented on LOG4J2-2837: - Commi

[jira] [Updated] (LOG4J2-2896) Missing Method : get Host in SyslogAppender in Log4j 2.13.3

[ https://issues.apache.org/jira/browse/LOG4J2-2896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Milind Pawar updated LOG4J2-2896: - Description: Hi Team, While working with SyslogAppender in version log4j 2.13.3, I had a requir

[jira] [Updated] (LOG4J2-2896) Missing Method : get Host in SyslogAppender in Log4j 2.13.3

[ https://issues.apache.org/jira/browse/LOG4J2-2896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Milind Pawar updated LOG4J2-2896: - Priority: Blocker (was: Major) > Missing Method : get Host in SyslogAppender in Log4j 2.13.3 >

[jira] [Created] (LOG4J2-2896) Missing Method : get Host in SyslogAppender in Log4j 2.13.3

Milind Pawar created LOG4J2-2896: Summary: Missing Method : get Host in SyslogAppender in Log4j 2.13.3 Key: LOG4J2-2896 URL: https://issues.apache.org/jira/browse/LOG4J2-2896 Project: Log4j 2

[GitHub] [logging-log4net] SymbioticKilla edited a comment on pull request #61: include source zip in release process

SymbioticKilla edited a comment on pull request #61: URL: https://github.com/apache/logging-log4net/pull/61#issuecomment-659392987 Hi, Thanks for your efforts! Does this version fix https://www.whitesourcesoftware.com/vulnerability-database/CVE-2018-1285 ? If yes, will it be re

[GitHub] [logging-log4net] SymbioticKilla commented on pull request #61: include source zip in release process

SymbioticKilla commented on pull request #61: URL: https://github.com/apache/logging-log4net/pull/61#issuecomment-659392987 Hi, Thanks for your efforts! Does this version fixes https://www.whitesourcesoftware.com/vulnerability-database/CVE-2018-1285 ? If yes, will it be release

[GitHub] [logging-log4cxx] stephen-webb opened a new pull request #29: Prevent filenamepatterntestcase from failing

stephen-webb opened a new pull request #29: URL: https://github.com/apache/logging-log4cxx/pull/29 when the test is run in a time zone east of the prime meridian This is an automated message from the Apache Git Service. To re