[jira] [Work logged] (LOG4J2-2579) Don't normalize event names

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

[jira] [Work logged] (LOG4J2-2579) Don't normalize event names

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

[jira] [Commented] (LOG4J2-2579) Don't normalize event names

[ https://issues.apache.org/jira/browse/LOG4J2-2579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16846413#comment-16846413 ] Ralph Goers commented on LOG4J2-2579: - I made a couple of comments on the PR several

[GitHub] [logging-log4j-audit] rgoers commented on a change in pull request #20: LOG4J2-2579

rgoers commented on a change in pull request #20: LOG4J2-2579 URL: https://github.com/apache/logging-log4j-audit/pull/20#discussion_r283151380 ## File path: log4j-audit/log4j-audit-api/src/test/java/org/apache/logging/log4j/audit/AuditLoggerTest.java ## @@ -38,9 +38,7 @@

[GitHub] [logging-log4j-audit] rgoers commented on a change in pull request #20: LOG4J2-2579

rgoers commented on a change in pull request #20: LOG4J2-2579 URL: https://github.com/apache/logging-log4j-audit/pull/20#discussion_r283151298 ## File path: log4j-audit/log4j-audit-api/src/main/java/org/apache/logging/log4j/audit/LogEventFactory.java ## @@ -28,12 +28,7 @@

[jira] [Work logged] (LOG4J2-2610) Windows - File creationTime issue for RollingFileAppender, combined time/size policy

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

[GitHub] [logging-log4j2] JCgH4164838Gh792C124B5 commented on a change in pull request #271: Proposed fix for LOG4J2-2610 rollover issue:

JCgH4164838Gh792C124B5 commented on a change in pull request #271: Proposed fix for LOG4J2-2610 rollover issue: URL: https://github.com/apache/logging-log4j2/pull/271#discussion_r286768619 ## File path: log4j-core/src/main/java/org/apache/logging/log4j/core/appender/rolling/Rolling

[jira] [Work logged] (LOG4J2-2610) Windows - File creationTime issue for RollingFileAppender, combined time/size policy

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

[GitHub] [logging-log4j2] carterkozak commented on a change in pull request #271: Proposed fix for LOG4J2-2610 rollover issue:

carterkozak commented on a change in pull request #271: Proposed fix for LOG4J2-2610 rollover issue: URL: https://github.com/apache/logging-log4j2/pull/271#discussion_r286761819 ## File path: log4j-core/src/main/java/org/apache/logging/log4j/core/appender/rolling/RollingFileManager

[jira] [Work logged] (LOG4J2-2610) Windows - File creationTime issue for RollingFileAppender, combined time/size policy

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

[GitHub] [logging-log4j2] JCgH4164838Gh792C124B5 commented on a change in pull request #271: Proposed fix for LOG4J2-2610 rollover issue:

JCgH4164838Gh792C124B5 commented on a change in pull request #271: Proposed fix for LOG4J2-2610 rollover issue: URL: https://github.com/apache/logging-log4j2/pull/271#discussion_r286757558 ## File path: log4j-core/src/main/java/org/apache/logging/log4j/core/appender/rolling/Rolling

[jira] [Work logged] (LOG4J2-2606) Asynchronous logging when the queue is full results heavy CPU load

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

[GitHub] [logging-log4j2] carterkozak commented on issue #273: LOG4J2-2606: Substantially improve async logging performance under heavy load

carterkozak commented on issue #273: LOG4J2-2606: Substantially improve async logging performance under heavy load URL: https://github.com/apache/logging-log4j2/pull/273#issuecomment-495044519 Thank you for the review, no rush on the remaining pieces. I don't plan to merge any of this unti

[jira] [Work logged] (LOG4J2-2606) Asynchronous logging when the queue is full results heavy CPU load

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

[GitHub] [logging-log4j2] carterkozak commented on a change in pull request #273: LOG4J2-2606: Substantially improve async logging performance under heavy load

carterkozak commented on a change in pull request #273: LOG4J2-2606: Substantially improve async logging performance under heavy load URL: https://github.com/apache/logging-log4j2/pull/273#discussion_r286754726 ## File path: log4j-core/src/main/java/org/apache/logging/log4j/core/as

[jira] [Work logged] (LOG4J2-2606) Asynchronous logging when the queue is full results heavy CPU load

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

[GitHub] [logging-log4j2] carterkozak commented on a change in pull request #273: LOG4J2-2606: Substantially improve async logging performance under heavy load

carterkozak commented on a change in pull request #273: LOG4J2-2606: Substantially improve async logging performance under heavy load URL: https://github.com/apache/logging-log4j2/pull/273#discussion_r286754419 ## File path: log4j-core/src/main/java/org/apache/logging/log4j/core/as

[jira] [Work logged] (LOG4J2-2606) Asynchronous logging when the queue is full results heavy CPU load

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

[GitHub] [logging-log4j2] carterkozak commented on a change in pull request #273: LOG4J2-2606: Substantially improve async logging performance under heavy load

carterkozak commented on a change in pull request #273: LOG4J2-2606: Substantially improve async logging performance under heavy load URL: https://github.com/apache/logging-log4j2/pull/273#discussion_r286754343 ## File path: log4j-core/src/main/java/org/apache/logging/log4j/core/as

[jira] [Work logged] (LOG4J2-2606) Asynchronous logging when the queue is full results heavy CPU load

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

[GitHub] [logging-log4j2] remkop commented on issue #273: LOG4J2-2606: Substantially improve async logging performance under heavy load

remkop commented on issue #273: LOG4J2-2606: Substantially improve async logging performance under heavy load URL: https://github.com/apache/logging-log4j2/pull/273#issuecomment-495041705 I did an initial review, but I haven't looked at what the trade-offs are for the use of Semaphor versu

[jira] [Work logged] (LOG4J2-2606) Asynchronous logging when the queue is full results heavy CPU load

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

[GitHub] [logging-log4j2] remkop commented on a change in pull request #273: LOG4J2-2606: Substantially improve async logging performance under heavy load

remkop commented on a change in pull request #273: LOG4J2-2606: Substantially improve async logging performance under heavy load URL: https://github.com/apache/logging-log4j2/pull/273#discussion_r286750131 ## File path: log4j-core/src/main/java/org/apache/logging/log4j/core/async/D

[jira] [Work logged] (LOG4J2-2606) Asynchronous logging when the queue is full results heavy CPU load

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

[jira] [Work logged] (LOG4J2-2606) Asynchronous logging when the queue is full results heavy CPU load

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

[GitHub] [logging-log4j2] remkop commented on a change in pull request #273: LOG4J2-2606: Substantially improve async logging performance under heavy load

remkop commented on a change in pull request #273: LOG4J2-2606: Substantially improve async logging performance under heavy load URL: https://github.com/apache/logging-log4j2/pull/273#discussion_r286747891 ## File path: log4j-core/src/main/java/org/apache/logging/log4j/core/async/A

[GitHub] [logging-log4j2] remkop commented on a change in pull request #273: LOG4J2-2606: Substantially improve async logging performance under heavy load

remkop commented on a change in pull request #273: LOG4J2-2606: Substantially improve async logging performance under heavy load URL: https://github.com/apache/logging-log4j2/pull/273#discussion_r286747742 ## File path: log4j-core/src/main/java/org/apache/logging/log4j/core/async/A

[jira] [Work logged] (LOG4J2-2606) Asynchronous logging when the queue is full results heavy CPU load

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

[GitHub] [logging-log4j2] remkop commented on a change in pull request #273: LOG4J2-2606: Substantially improve async logging performance under heavy load

remkop commented on a change in pull request #273: LOG4J2-2606: Substantially improve async logging performance under heavy load URL: https://github.com/apache/logging-log4j2/pull/273#discussion_r286747814 ## File path: log4j-core/src/main/java/org/apache/logging/log4j/core/async/A

[GitHub] [logging-log4j2] remkop commented on a change in pull request #273: LOG4J2-2606: Substantially improve async logging performance under heavy load

remkop commented on a change in pull request #273: LOG4J2-2606: Substantially improve async logging performance under heavy load URL: https://github.com/apache/logging-log4j2/pull/273#discussion_r286747384 ## File path: log4j-core/src/main/java/org/apache/logging/log4j/core/async/A

[jira] [Work logged] (LOG4J2-2606) Asynchronous logging when the queue is full results heavy CPU load

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

Build failed in Jenkins: logging-log4net » PR-48 #1

See -- Branch indexing Connecting to https://api.github.com using dpsenner/** (dpsenner at github) Loading trusted files from base branch develop at f238e175ca4f23410af7a226a1e

[jira] [Work logged] (LOG4NET-587) Mutex ~ Access to the path is denied in log4net.Appender.RollingFileAppender.ActivateOptions()

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

[GitHub] [logging-log4net] mirec75 opened a new pull request #48: Fixes LOG4NET-587 Mutex ~ UnauthorizedAccessException Access to the path is denied

mirec75 opened a new pull request #48: Fixes LOG4NET-587 Mutex ~ UnauthorizedAccessException Access to the path is denied URL: https://github.com/apache/logging-log4net/pull/48 This pull request fixes [LOG4NET-587](https://issues.apache.org/jira/browse/LOG4NET-587) issue: Mutex ~ Unauthor

[jira] [Commented] (LOG4J2-2606) Asynchronous logging when the queue is full results heavy CPU load

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

[jira] [Work logged] (LOG4J2-2606) Asynchronous logging when the queue is full results heavy CPU load

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

[GitHub] [logging-log4j2] carterkozak commented on issue #273: LOG4J2-2606: Substantially improve async logging performance under heavy load

carterkozak commented on issue #273: LOG4J2-2606: Substantially improve async logging performance under heavy load URL: https://github.com/apache/logging-log4j2/pull/273#issuecomment-494816763 The WaitStrategy appears to be designed to awaken all producer threads each time an event from th

[GitHub] [logging-log4j2] carterkozak commented on issue #272: LOG4J2-2611: AsyncQueueFullPolicy configuration short values are case insensitive

carterkozak commented on issue #272: LOG4J2-2611: AsyncQueueFullPolicy configuration short values are case insensitive URL: https://github.com/apache/logging-log4j2/pull/272#issuecomment-494750958 That is correct. This is an

[GitHub] [logging-log4j2] garydgregory commented on issue #272: LOG4J2-2611: AsyncQueueFullPolicy configuration short values are case insensitive

garydgregory commented on issue #272: LOG4J2-2611: AsyncQueueFullPolicy configuration short values are case insensitive URL: https://github.com/apache/logging-log4j2/pull/272#issuecomment-494728510 You can add the new name and deprecate the old one, no?