[jira] [Commented] (LOG4J2-1828) add support for prudent mode in Log4j 2

[ https://issues.apache.org/jira/browse/LOG4J2-1828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16990753#comment-16990753 ] Ralph Goers commented on LOG4J2-1828: - Implementing this for the RollingFileAppender

Jenkins build is still unstable: Log4j 2 2.x #4051

See

[GitHub] [logging-log4j2] rgoers commented on issue #306: [LOG4J2-2678] Add LogEvent timestamp to Kafka ProducerRecord

rgoers commented on issue #306: [LOG4J2-2678] Add LogEvent timestamp to Kafka ProducerRecord URL: https://github.com/apache/logging-log4j2/pull/306#issuecomment-562917363 I applied this to master and when I ran the test I get ``` [INFO] Running org.apache.logging.log4j.kafka.appender.

[jira] [Work logged] (LOG4J2-2678) Add LogEvent timestamp to ProducerRecord in KafkaAppender

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

[jira] [Work logged] (LOG4J2-1192) Dynamic Subject for SMTP Appender

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

[GitHub] [logging-log4j2] rgoers commented on issue #308: LOG4J2-1192 (support dynamic Subject)

rgoers commented on issue #308: LOG4J2-1192 (support dynamic Subject) URL: https://github.com/apache/logging-log4j2/pull/308#issuecomment-562917090 Please provide a unit test for this. Also, if you would like it in a Log4j 2.x release then please provide an equivalent patch on the release-2

[GitHub] [logging-log4j2] rgoers commented on issue #319: log4j-kafka added with "retryCount" function

rgoers commented on issue #319: log4j-kafka added with "retryCount" function URL: https://github.com/apache/logging-log4j2/pull/319#issuecomment-562916875 After applying the patch and fixing the typo in KafkaAppenderTest.xml the KafkaAppenderTest is failing with: ```[INFO] Running o

[jira] [Resolved] (LOG4J2-2688) [web] session attribute lookup support

[ https://issues.apache.org/jira/browse/LOG4J2-2688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-2688. - Fix Version/s: 3.0.0 Resolution: Fixed The pull request was merged to master. No PR was s

[jira] [Commented] (LOG4J2-2688) [web] session attribute lookup support

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

[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=16990740#comment-16990740 ] ASF subversion and git services commented on LOG4J2-2523: - Commi

[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=16990737#comment-16990737 ] ASF subversion and git services commented on LOG4J2-2523: - Commi

[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=16990738#comment-16990738 ] ASF subversion and git services commented on LOG4J2-2523: - Commi

[jira] [Work logged] (LOG4J2-2688) [web] session attribute lookup support

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

[GitHub] [logging-log4j2] rgoers merged pull request #287: [LOG4J2-2688] adding support for session attributes in log4j-web

rgoers merged pull request #287: [LOG4J2-2688] adding support for session attributes in log4j-web URL: https://github.com/apache/logging-log4j2/pull/287 This is an automated message from the Apache Git Service. To respond to

Jenkins build is still unstable: Log4j 2 2.x #4050

See

[jira] [Resolved] (LOG4J2-2058) java.locale.providers set to HOST causes Log4j2 to crash in Java 9

[ https://issues.apache.org/jira/browse/LOG4J2-2058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-2058. - Fix Version/s: 2.13.0 Resolution: Fixed I have applied what I believe is a fix but I have

[jira] [Commented] (LOG4J2-2058) java.locale.providers set to HOST causes Log4j2 to crash in Java 9

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

[jira] [Commented] (LOG4J2-2058) java.locale.providers set to HOST causes Log4j2 to crash in Java 9

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

[jira] [Commented] (LOG4J2-2058) java.locale.providers set to HOST causes Log4j2 to crash in Java 9

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

[jira] [Commented] (LOG4J2-2058) java.locale.providers set to HOST causes Log4j2 to crash in Java 9

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

[jira] [Commented] (LOG4J2-2058) java.locale.providers set to HOST causes Log4j2 to crash in Java 9

[ https://issues.apache.org/jira/browse/LOG4J2-2058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16990716#comment-16990716 ] Ralph Goers commented on LOG4J2-2058: - I have created a test but no matter what I do

[jira] [Commented] (LOG4J2-2435) Unrecognized conversion specifier [logger] from Junit5 with Java 10 and locale C

[ https://issues.apache.org/jira/browse/LOG4J2-2435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16990714#comment-16990714 ] Ralph Goers commented on LOG4J2-2435: - LOG4J2-2058 and this one seem to have the sam

[jira] [Resolved] (LOG4J2-2435) Unrecognized conversion specifier [logger] from Junit5 with Java 10 and locale C

[ https://issues.apache.org/jira/browse/LOG4J2-2435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-2435. - Resolution: Duplicate Resolving this as a duplicate although it contains useful information. >

[jira] [Commented] (LOG4J2-2435) Unrecognized conversion specifier [logger] from Junit5 with Java 10 and locale C

[ https://issues.apache.org/jira/browse/LOG4J2-2435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16990700#comment-16990700 ] Ralph Goers commented on LOG4J2-2435: - I am trying to reproduce this. I can see that

[jira] [Closed] (LOG4J2-2725) RingBufferLogEvent.clear() is not called in case of OutOfMemoryError (or any other exception/error)

[ https://issues.apache.org/jira/browse/LOG4J2-2725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak closed LOG4J2-2725. Closing this ticket because the test was able to reproduce the reported scenario. > RingBufferLogEve

[jira] [Resolved] (LOG4J2-2725) RingBufferLogEvent.clear() is not called in case of OutOfMemoryError (or any other exception/error)

[ https://issues.apache.org/jira/browse/LOG4J2-2725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak resolved LOG4J2-2725. -- Resolution: Fixed I've merged the fix and a test which reproduced the bug into release-2.x and

[jira] [Updated] (LOG4J2-2725) RingBufferLogEvent.clear() is not called in case of OutOfMemoryError (or any other exception/error)

[ https://issues.apache.org/jira/browse/LOG4J2-2725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carter Kozak updated LOG4J2-2725: - Fix Version/s: 2.13.0 > RingBufferLogEvent.clear() is not called in case of OutOfMemoryError (or

Jenkins build is still unstable: Log4j 2 2.x #4049

See

Jenkins build is still unstable: Log4j 2 2.x #4048

See

[jira] [Commented] (LOG4J2-2725) RingBufferLogEvent.clear() is not called in case of OutOfMemoryError (or any other exception/error)

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

[jira] [Commented] (LOG4J2-2725) RingBufferLogEvent.clear() is not called in case of OutOfMemoryError (or any other exception/error)

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

[jira] [Work logged] (LOG4J2-2725) RingBufferLogEvent.clear() is not called in case of OutOfMemoryError (or any other exception/error)

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

[jira] [Work logged] (LOG4J2-2725) RingBufferLogEvent.clear() is not called in case of OutOfMemoryError (or any other exception/error)

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

[jira] [Commented] (LOG4J2-2725) RingBufferLogEvent.clear() is not called in case of OutOfMemoryError (or any other exception/error)

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

[GitHub] [logging-log4j2] carterkozak commented on issue #317: LOG4J2-2725 - Added try/finally around event.execute() for RingBufferLogEventHandler

carterkozak commented on issue #317: LOG4J2-2725 - Added try/finally around event.execute() for RingBufferLogEventHandler URL: https://github.com/apache/logging-log4j2/pull/317#issuecomment-562894119 I have a test which reproduces, pushing shortly.

[GitHub] [logging-log4j2] carterkozak merged pull request #317: LOG4J2-2725 - Added try/finally around event.execute() for RingBufferLogEventHandler

carterkozak merged pull request #317: LOG4J2-2725 - Added try/finally around event.execute() for RingBufferLogEventHandler URL: https://github.com/apache/logging-log4j2/pull/317 This is an automated message from the Apache

[jira] [Work logged] (LOG4J2-2725) RingBufferLogEvent.clear() is not called in case of OutOfMemoryError (or any other exception/error)

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

[jira] [Work logged] (LOG4J2-2725) RingBufferLogEvent.clear() is not called in case of OutOfMemoryError (or any other exception/error)

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

[jira] [Commented] (LOG4J2-2725) RingBufferLogEvent.clear() is not called in case of OutOfMemoryError (or any other exception/error)

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

[GitHub] [logging-log4j2] carterkozak commented on issue #316: LOG4J2-2725 - Added try/finally around event.execute() for RingBufferLogEventHandler

carterkozak commented on issue #316: LOG4J2-2725 - Added try/finally around event.execute() for RingBufferLogEventHandler URL: https://github.com/apache/logging-log4j2/pull/316#issuecomment-562893976 Thanks for your contribution @anikosss! --

[GitHub] [logging-log4j2] carterkozak merged pull request #316: LOG4J2-2725 - Added try/finally around event.execute() for RingBufferLogEventHandler

carterkozak merged pull request #316: LOG4J2-2725 - Added try/finally around event.execute() for RingBufferLogEventHandler URL: https://github.com/apache/logging-log4j2/pull/316 This is an automated message from the Apache G

Jenkins build is still unstable: Log4j 2 2.x #4047

See

[jira] [Closed] (LOG4J2-2563) NullPointerException in ScriptManager during factory.getParameter(KEY_THREADING)

[ https://issues.apache.org/jira/browse/LOG4J2-2563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers closed LOG4J2-2563. --- Resolution: Abandoned Closing due to lack of feedback. > NullPointerException in ScriptManager duri

[jira] [Commented] (LOG4J2-2682) TimeBasedTriggeringPolicy needs improved interval

[ https://issues.apache.org/jira/browse/LOG4J2-2682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16990615#comment-16990615 ] Ralph Goers commented on LOG4J2-2682: - Robert, are you still working on this? > Tim

[jira] [Created] (LOG4NET-639) RollingFileAppender can't identify invalid filename

GaoHu created LOG4NET-639: - Summary: RollingFileAppender can't identify invalid filename Key: LOG4NET-639 URL: https://issues.apache.org/jira/browse/LOG4NET-639 Project: Log4net Issue Type: Bug