[GitHub] [logging-log4j2] rimal commented on issue #215: LOG4J2-2427 log4j2 filter for logs with no markers

rimal commented on issue #215: LOG4J2-2427 log4j2 filter for logs with no markers URL: https://github.com/apache/logging-log4j2/pull/215#issuecomment-502552778 @rgoers I have added the documentation. Now the check is giving a build error. Not sure why, because I have not changed any code.

[jira] [Work logged] (LOG4J2-2427) Filter for logging logs with no marker set

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

[jira] [Commented] (LOG4J2-1852) Plugins lookup by package is not compatible with Spring Boot jar packaging

[ https://issues.apache.org/jira/browse/LOG4J2-1852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16865301#comment-16865301 ] Ralph Goers commented on LOG4J2-1852: - FWIW - LOG4J2-2621 was implemented in 3.0 to

[jira] [Work logged] (LOG4J2-2427) Filter for logging logs with no marker set

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

[GitHub] [logging-log4j2] rgoers commented on issue #215: LOG4J2-2427 log4j2 filter for logs with no markers

rgoers commented on issue #215: LOG4J2-2427 log4j2 filter for logs with no markers URL: https://github.com/apache/logging-log4j2/pull/215#issuecomment-502530133 I was about to merge this but then realized I would have to write the documentation for it. Is it possible you could update the P

[jira] [Work logged] (LOG4J2-2211) MainMapLookup ${main:--file} placeholder doesn't work

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

[GitHub] [logging-log4j2] rgoers commented on a change in pull request #145: fix bug LOG4J2-2211

rgoers commented on a change in pull request #145: fix bug LOG4J2-2211 URL: https://github.com/apache/logging-log4j2/pull/145#discussion_r200211890 ## File path: log4j-core/src/main/java/org/apache/logging/log4j/core/lookup/StrSubstitutor.java ## @@ -973,7 +973,8 @@ priva

[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=26&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-26 ] 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-502508705 Thanks @remkop! I don't have a use case where the semaphore would be better than a synchronized b

[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=261109&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-261109 ] 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-502506715 Thanks for the reminder! I thought a synchronized block would express the intentions better beca

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

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

[GitHub] [logging-log4j2] rgoers edited a comment on issue #271: Proposed fix for LOG4J2-2610 rollover issue:

rgoers edited a comment on issue #271: Proposed fix for LOG4J2-2610 rollover issue: URL: https://github.com/apache/logging-log4j2/pull/271#issuecomment-502503385 Thanks. That is perfect and is exactly what I expected. From the log we see ``` 2019-06-16 20:39:01,573 main DEBUG 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=261103&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-261103 ] ASF GitHub Bot logged work on LOG4J2-2610: -- Author: ASF GitHub Bot

[GitHub] [logging-log4j2] rgoers edited a comment on issue #271: Proposed fix for LOG4J2-2610 rollover issue:

rgoers edited a comment on issue #271: Proposed fix for LOG4J2-2610 rollover issue: URL: https://github.com/apache/logging-log4j2/pull/271#issuecomment-502503385 Thanks. That is perfect and is exactly what I expected. From the log we see ``` 2019-06-16 20:39:01,573 main DEBUG 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=261100&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-261100 ] ASF GitHub Bot logged work on LOG4J2-2610: -- Author: ASF GitHub Bot

[GitHub] [logging-log4j2] rgoers commented on issue #271: Proposed fix for LOG4J2-2610 rollover issue:

rgoers commented on issue #271: Proposed fix for LOG4J2-2610 rollover issue: URL: https://github.com/apache/logging-log4j2/pull/271#issuecomment-502503385 Thanks. That is perfect and is exactly what I expected. From the log we see `2019-06-16 20:39:01,573 main DEBUG RollingFileManager ex

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

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

[GitHub] [logging-log4j2] carterkozak commented on issue #271: Proposed fix for LOG4J2-2610 rollover issue:

carterkozak commented on issue #271: Proposed fix for LOG4J2-2610 rollover issue: URL: https://github.com/apache/logging-log4j2/pull/271#issuecomment-502499969 Ah, ran several more iterations and got a failure with trace enabled: https://gist.github.com/carterkozak/c6a3bc6cfc258744bb5feb8a

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

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

[GitHub] [logging-log4j2] carterkozak commented on issue #271: Proposed fix for LOG4J2-2610 rollover issue:

carterkozak commented on issue #271: Proposed fix for LOG4J2-2610 rollover issue: URL: https://github.com/apache/logging-log4j2/pull/271#issuecomment-502499719 You're right, I set the status logger level too early and failed to record anything while the test was running. I was not able

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

See Changes: [ckozak] LOG4J2-2631: RoutingAppender PurgePolicy implementations don't remove [ckozak] LOG4J2-2629: Avoid losing log events when the PurgePolicy races a log

[jira] [Closed] (LOG4J2-2629) RoutingAppender + purge policy race results in attempts to append to a closed appender

[ https://issues.apache.org/jira/browse/LOG4J2-2629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak closed LOG4J2-2629. > RoutingAppender + purge policy race results in attempts to append to a closed > appender >

[jira] [Reopened] (LOG4J2-2629) RoutingAppender + purge policy race results in attempts to append to a closed appender

[ https://issues.apache.org/jira/browse/LOG4J2-2629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak reopened LOG4J2-2629: -- Need to set affects and fix versions > RoutingAppender + purge policy race results in attempts to

[jira] [Resolved] (LOG4J2-2629) RoutingAppender + purge policy race results in attempts to append to a closed appender

[ https://issues.apache.org/jira/browse/LOG4J2-2629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak resolved LOG4J2-2629. -- Resolution: Fixed > RoutingAppender + purge policy race results in attempts to append to a clo

[jira] [Updated] (LOG4J2-2629) RoutingAppender + purge policy race results in attempts to append to a closed appender

[ https://issues.apache.org/jira/browse/LOG4J2-2629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak updated LOG4J2-2629: - Fix Version/s: 2.12.0 > RoutingAppender + purge policy race results in attempts to append to a c

[jira] [Updated] (LOG4J2-2629) RoutingAppender + purge policy race results in attempts to append to a closed appender

[ https://issues.apache.org/jira/browse/LOG4J2-2629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak updated LOG4J2-2629: - Affects Version/s: 2.11.2 > RoutingAppender + purge policy race results in attempts to append to

[jira] [Work logged] (LOG4J2-2629) RoutingAppender + purge policy race results in attempts to append to a closed appender

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

[jira] [Commented] (LOG4J2-2631) RoutingAppender purge policy should only stop appenders that the RoutingAppender has created

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

[jira] [Commented] (LOG4J2-2629) RoutingAppender + purge policy race results in attempts to append to a closed appender

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

[jira] [Closed] (LOG4J2-2629) RoutingAppender + purge policy race results in attempts to append to a closed appender

[ https://issues.apache.org/jira/browse/LOG4J2-2629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak closed LOG4J2-2629. > RoutingAppender + purge policy race results in attempts to append to a closed > appender >

[jira] [Commented] (LOG4J2-2629) RoutingAppender + purge policy race results in attempts to append to a closed appender

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

[jira] [Resolved] (LOG4J2-2629) RoutingAppender + purge policy race results in attempts to append to a closed appender

[ https://issues.apache.org/jira/browse/LOG4J2-2629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak resolved LOG4J2-2629. -- Resolution: Fixed > RoutingAppender + purge policy race results in attempts to append to a clo

[jira] [Commented] (LOG4J2-2629) RoutingAppender + purge policy race results in attempts to append to a closed appender

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

[jira] [Work logged] (LOG4J2-2631) RoutingAppender purge policy should only stop appenders that the RoutingAppender has created

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

[jira] [Closed] (LOG4J2-2631) RoutingAppender purge policy should only stop appenders that the RoutingAppender has created

[ https://issues.apache.org/jira/browse/LOG4J2-2631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak closed LOG4J2-2631. Resolution: Fixed > RoutingAppender purge policy should only stop appenders that the > RoutingApp

[jira] [Commented] (LOG4J2-2629) RoutingAppender + purge policy race results in attempts to append to a closed appender

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

[GitHub] [logging-log4j2] carterkozak merged pull request #278: LOG4J2-2631: RoutingAppender PurgePolicy implementations don't remove …

carterkozak merged pull request #278: LOG4J2-2631: RoutingAppender PurgePolicy implementations don't remove … URL: https://github.com/apache/logging-log4j2/pull/278 This is an automated message from the Apache Git Service. T

[jira] [Work logged] (LOG4J2-2629) RoutingAppender + purge policy race results in attempts to append to a closed appender

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

[jira] [Commented] (LOG4J2-2631) RoutingAppender purge policy should only stop appenders that the RoutingAppender has created

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

[GitHub] [logging-log4j2] carterkozak merged pull request #279: LOG4J2-2629: Avoid losing log events when the PurgePolicy races a log event

carterkozak merged pull request #279: LOG4J2-2629: Avoid losing log events when the PurgePolicy races a log event URL: https://github.com/apache/logging-log4j2/pull/279 This is an automated message from the Apache Git Servic

[GitHub] [logging-log4j2] carterkozak commented on issue #279: LOG4J2-2629: Avoid losing log events when the PurgePolicy races a log event

carterkozak commented on issue #279: LOG4J2-2629: Avoid losing log events when the PurgePolicy races a log event URL: https://github.com/apache/logging-log4j2/pull/279#issuecomment-502498413 Done, thanks for the quick review @rgoers!

[jira] [Work logged] (LOG4J2-2629) RoutingAppender + purge policy race results in attempts to append to a closed appender

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

[GitHub] [logging-log4j2] rgoers commented on issue #279: LOG4J2-2629: Avoid losing log events when the PurgePolicy races a log event

rgoers commented on issue #279: LOG4J2-2629: Avoid losing log events when the PurgePolicy races a log event URL: https://github.com/apache/logging-log4j2/pull/279#issuecomment-502497316 You will also have to apply this to release-2.x. As far as I am concerned you don't need another PR - ju

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

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

[GitHub] [logging-log4j2] rgoers commented on issue #271: Proposed fix for LOG4J2-2610 rollover issue:

rgoers commented on issue #271: Proposed fix for LOG4J2-2610 rollover issue: URL: https://github.com/apache/logging-log4j2/pull/271#issuecomment-502496843 Yes, I am pretty sure this is timing related. I just don't know if it is something in the test or something in the code. If you

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

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

[GitHub] [logging-log4j2] carterkozak commented on issue #271: Proposed fix for LOG4J2-2610 rollover issue:

carterkozak commented on issue #271: Proposed fix for LOG4J2-2610 rollover issue: URL: https://github.com/apache/logging-log4j2/pull/271#issuecomment-502492251 If I set the status logger level to trace and don't register the listener, I don't see anything helpful in the log surrounding fai

[GitHub] [logging-log4j2] carterkozak commented on issue #271: Proposed fix for LOG4J2-2610 rollover issue:

carterkozak commented on issue #271: Proposed fix for LOG4J2-2610 rollover issue: URL: https://github.com/apache/logging-log4j2/pull/271#issuecomment-502491851 I think we have a subtle race somewhere, when I keep `statusLogger.registerListener(this);` commented I can reproduce failures, bu

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

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

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

See

[jira] [Commented] (LOG4J2-2523) log4j-web should support header+attributes lookup

[ https://issues.apache.org/jira/browse/LOG4J2-2523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16865177#comment-16865177 ] Ralph Goers commented on LOG4J2-2523: - Fix was applied to master. Since the patch ha

[jira] [Resolved] (LOG4J2-2523) log4j-web should support header+attributes lookup

[ https://issues.apache.org/jira/browse/LOG4J2-2523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-2523. - Resolution: Fixed Fix Version/s: 3.0.0 > log4j-web should support header+attributes looku

[jira] [Commented] (LOG4J2-2523) log4j-web should support header+attributes lookup

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

[GitHub] [logging-log4j2] rgoers merged pull request #246: [LOG4J2-2523] adding support for request related lookup web module

rgoers merged pull request #246: [LOG4J2-2523] adding support for request related lookup web module URL: https://github.com/apache/logging-log4j2/pull/246 This is an automated message from the Apache Git Service. To respon

[jira] [Work logged] (LOG4J2-2523) log4j-web should support header+attributes lookup

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

[jira] [Commented] (LOG4J2-2523) log4j-web should support header+attributes lookup

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

[GitHub] [logging-log4j2] rgoers merged pull request #256: (doc) Clarify Default Rollover Strategy

rgoers merged pull request #256: (doc) Clarify Default Rollover Strategy URL: https://github.com/apache/logging-log4j2/pull/256 This is an automated message from the Apache Git Service. To respond to the message, please log o

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

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

[GitHub] [logging-log4j2] rgoers commented on issue #271: Proposed fix for LOG4J2-2610 rollover issue:

rgoers commented on issue #271: Proposed fix for LOG4J2-2610 rollover issue: URL: https://github.com/apache/logging-log4j2/pull/271#issuecomment-502486266 @carterkozak Even with the Suite I still cannot get it to fail. Can you apply the attached diff and see if it fails for you? If it

[jira] [Work logged] (LOG4J2-2629) RoutingAppender + purge policy race results in attempts to append to a closed appender

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

[GitHub] [logging-log4j2] carterkozak opened a new pull request #279: LOG4J2-2629: Avoid losing log events when the PurgePolicy races a log event

carterkozak opened a new pull request #279: LOG4J2-2629: Avoid losing log events when the PurgePolicy races a log event URL: https://github.com/apache/logging-log4j2/pull/279 Stacked on top of #278 This is an automated messag

[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=261059&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-261059 ] 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-502480491 Friendly ping on this. Not a rush, just want to make sure we don't forget about it for 2.12.0 :-)

[jira] [Work logged] (LOG4J2-2631) RoutingAppender purge policy should only stop appenders that the RoutingAppender has created

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

[GitHub] [logging-log4j2] carterkozak commented on a change in pull request #278: LOG4J2-2631: RoutingAppender PurgePolicy implementations don't remove …

carterkozak commented on a change in pull request #278: LOG4J2-2631: RoutingAppender PurgePolicy implementations don't remove … URL: https://github.com/apache/logging-log4j2/pull/278#discussion_r294096817 ## File path: log4j-core/src/main/java/org/apache/logging/log4j/core/appender

[GitHub] [logging-log4j2] carterkozak commented on a change in pull request #278: LOG4J2-2631: RoutingAppender PurgePolicy implementations don't remove …

carterkozak commented on a change in pull request #278: LOG4J2-2631: RoutingAppender PurgePolicy implementations don't remove … URL: https://github.com/apache/logging-log4j2/pull/278#discussion_r294096681 ## File path: log4j-core/src/main/java/org/apache/logging/log4j/core/appender

[jira] [Work logged] (LOG4J2-2631) RoutingAppender purge policy should only stop appenders that the RoutingAppender has created

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

[jira] [Work logged] (LOG4J2-2631) RoutingAppender purge policy should only stop appenders that the RoutingAppender has created

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

[GitHub] [logging-log4j2] carterkozak opened a new pull request #278: LOG4J2-2631: RoutingAppender IdlePolicy implementations don't remove …

carterkozak opened a new pull request #278: LOG4J2-2631: RoutingAppender IdlePolicy implementations don't remove … URL: https://github.com/apache/logging-log4j2/pull/278 …referenced appenders Note that this makes a behavior change to RoutingAppender.getAppenders where Routes based

[GitHub] [logging-log4j2] carterkozak commented on issue #271: Proposed fix for LOG4J2-2610 rollover issue:

carterkozak commented on issue #271: Proposed fix for LOG4J2-2610 rollover issue: URL: https://github.com/apache/logging-log4j2/pull/271#issuecomment-502475511 @rgoers I've been able to get the test to fail locally with this: #277 That said there could be something odd going on with the

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

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

[GitHub] [logging-log4j2] carterkozak opened a new pull request #277: Suite to reproduce LOG4J2-2613 test flakes

carterkozak opened a new pull request #277: Suite to reproduce LOG4J2-2613 test flakes URL: https://github.com/apache/logging-log4j2/pull/277 This is an automated message from the Apache Git Service. To respond to the messag

[jira] [Work logged] (LOG4J2-2613) Fix RollingAppenderSizeWithTimeTest.testAppender flakes

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

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

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

[GitHub] [logging-log4j2] rgoers commented on issue #271: Proposed fix for LOG4J2-2610 rollover issue:

rgoers commented on issue #271: Proposed fix for LOG4J2-2610 rollover issue: URL: https://github.com/apache/logging-log4j2/pull/271#issuecomment-502474319 I ran RollingAppenderSizeWithTimeTest in my Windows VM the other day and it failed. I am trying to diagnose the problem today and have r

[jira] [Closed] (LOG4J2-2423) Rolled files are not deleted when a date is used in the pattern

[ https://issues.apache.org/jira/browse/LOG4J2-2423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak closed LOG4J2-2423. Resolution: Not A Bug Closing this out as I misunderstood the functionality. > Rolled files are n