[jira] [Created] (LOG4J2-3488) RollingFileAppender foes not start when associated with FailoverAppender

2022-04-24 Thread Haresh (Jira)
Haresh created LOG4J2-3488: -- Summary: RollingFileAppender foes not start when associated with FailoverAppender Key: LOG4J2-3488 URL: https://issues.apache.org/jira/browse/LOG4J2-3488 Project: Log4j 2

[GitHub] [logging-log4j2] remkop commented on pull request #829: LOG4J2-3473 garbage-free default disruptor WaitStrategy

2022-04-24 Thread GitBox
remkop commented on PR #829: URL: https://github.com/apache/logging-log4j2/pull/829#issuecomment-110803 I realize this PR is a bit difficult to review. This is the commit in the LDAP disruptor repo that has the change we are trying to introduce here: https://github.com/LMAX-Exchan

[jira] [Closed] (LOG4J2-3472) Allow configuration of custom Disruptor WaitStrategy

2022-04-24 Thread Remko Popma (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-3472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma closed LOG4J2-3472. --- Merged into master also now. > Allow configuration of custom Disruptor WaitStrategy > -

[GitHub] [logging-log4j2] remkop commented on pull request #830: LOG4J2-3472 (master) make disruptor WaitStrategy configurable in Log4j configuration

2022-04-24 Thread GitBox
remkop commented on PR #830: URL: https://github.com/apache/logging-log4j2/pull/830#issuecomment-1108028679 It took a while, but in the end all tests passed. (I had to suppress XmlSchemaTest, which is failing for some unrelated reason. I re-enabled XmlSchemaTest after confirming that

[jira] [Commented] (LOG4J2-3472) Allow configuration of custom Disruptor WaitStrategy

2022-04-24 Thread ASF subversion and git services (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-3472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17527293#comment-17527293 ] ASF subversion and git services commented on LOG4J2-3472: - Commi

[GitHub] [logging-log4j2] remkop merged pull request #830: LOG4J2-3472 (master) make disruptor WaitStrategy configurable in Log4j configuration

2022-04-24 Thread GitBox
remkop merged PR #830: URL: https://github.com/apache/logging-log4j2/pull/830 -- 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 to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@

[jira] [Commented] (LOG4J2-3487) The LoggerConfig includeLocation defaults to true in 2.17.2

2022-04-24 Thread Ralph Goers (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-3487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17527247#comment-17527247 ] Ralph Goers commented on LOG4J2-3487: - The default isn't that simple. AbstractLogger

[GitHub] [logging-log4j2] remkop commented on pull request #830: LOG4J2-3472 (master) make disruptor WaitStrategy configurable in Log4j configuration

2022-04-24 Thread GitBox
remkop commented on PR #830: URL: https://github.com/apache/logging-log4j2/pull/830#issuecomment-1107911963 @jvz Ah yes of course. Thank you Matt! -- 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 to go to

[GitHub] [logging-log4j2] jvz commented on pull request #830: LOG4J2-3472 (master) make disruptor WaitStrategy configurable in Log4j configuration

2022-04-24 Thread GitBox
jvz commented on PR #830: URL: https://github.com/apache/logging-log4j2/pull/830#issuecomment-1107905963 Ah, that would be because in master, tests for `log4j-api`, `log4j-plugins`, and `log4j-core` all have dedicated `-test` modules which contain both source and test code. JPMS combined wi

[jira] [Created] (LOG4J2-3487) The LoggerConfig includeLocation defaults to true in 2.17.2

2022-04-24 Thread Dave Messink (Jira)
Dave Messink created LOG4J2-3487: Summary: The LoggerConfig includeLocation defaults to true in 2.17.2 Key: LOG4J2-3487 URL: https://issues.apache.org/jira/browse/LOG4J2-3487 Project: Log4j 2

[jira] [Commented] (LOG4J2-2872) Unable to parse Custom Log Levels

2022-04-24 Thread ASF subversion and git services (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-2872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17527235#comment-17527235 ] ASF subversion and git services commented on LOG4J2-2872: - Commi

[jira] [Commented] (LOG4J2-2872) Unable to parse Custom Log Levels

2022-04-24 Thread ASF subversion and git services (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-2872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17527232#comment-17527232 ] ASF subversion and git services commented on LOG4J2-2872: - Commi

[jira] [Commented] (LOG4J2-3475) RegexFilter does not respect useRawMsg option in some cases

2022-04-24 Thread ASF subversion and git services (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-3475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17527236#comment-17527236 ] ASF subversion and git services commented on LOG4J2-3475: - Commi

[jira] [Commented] (LOG4J2-3440) Log4j 1.2 bridge getAllAppenders() returns null enumeration

2022-04-24 Thread ASF subversion and git services (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17527234#comment-17527234 ] ASF subversion and git services commented on LOG4J2-3440: - Commi

[jira] [Commented] (LOG4J2-3475) RegexFilter does not respect useRawMsg option in some cases

2022-04-24 Thread ASF subversion and git services (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-3475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17527237#comment-17527237 ] ASF subversion and git services commented on LOG4J2-3475: - Commi

[jira] [Commented] (LOG4J2-3462) Duplicate dependency in pom.xml

2022-04-24 Thread ASF subversion and git services (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-3462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17527233#comment-17527233 ] ASF subversion and git services commented on LOG4J2-3462: - Commi

[jira] [Commented] (LOG4J2-3439) log4j2 Spring Cloud config integration with MTLS gives NullPointerException

2022-04-24 Thread ASF subversion and git services (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-3439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17527230#comment-17527230 ] ASF subversion and git services commented on LOG4J2-3439: - Commi

[jira] [Commented] (LOG4J2-3429) Code Sample for Custom Config has Syntax Errors

2022-04-24 Thread ASF subversion and git services (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-3429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17527231#comment-17527231 ] ASF subversion and git services commented on LOG4J2-3429: - Commi

[GitHub] [logging-log4j2] remkop opened a new pull request, #830: LOG4J2-3472 (master) make disruptor WaitStrategy configurable in Log4j configuration

2022-04-24 Thread GitBox
remkop opened a new pull request, #830: URL: https://github.com/apache/logging-log4j2/pull/830 Raising this as a separate PR because I can't get the master branch to build in my local environment... Does anyone have cycles to look at this? ``` [ERROR] Failed to execute goal

[jira] [Assigned] (LOG4J2-2788) Replace ThreadContext.EmptyIterator with JDK variant

2022-04-24 Thread Piotr Karwasz (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-2788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Karwasz reassigned LOG4J2-2788: - Assignee: Piotr Karwasz > Replace ThreadContext.EmptyIterator with JDK variant > --