[jira] [Commented] (LOG4J2-1626) Port Windows Event Log Appender from Log4j 1.2

[ https://issues.apache.org/jira/browse/LOG4J2-1626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15535137#comment-15535137 ] Matt Sicker commented on LOG4J2-1626: - Requiring Windows to make a Log4j 2 release is somewhat of a

[jira] [Comment Edited] (LOG4J2-1626) Port Windows Event Log Appender from Log4j 1.2

[ https://issues.apache.org/jira/browse/LOG4J2-1626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15535106#comment-15535106 ] Gary Gregory edited comment on LOG4J2-1626 at 9/30/16 5:40 AM: --- I have a

[jira] [Commented] (LOG4J2-1626) Port Windows Event Log Appender from Log4j 1.2

[ https://issues.apache.org/jira/browse/LOG4J2-1626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15535106#comment-15535106 ] Gary Gregory commented on LOG4J2-1626: -- I have a customer that uses the NTLogEventAppender with

[jira] [Commented] (LOG4J2-1626) Port Windows Event Log Appender from Log4j 1.2

[ https://issues.apache.org/jira/browse/LOG4J2-1626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15535088#comment-15535088 ] Remko Popma commented on LOG4J2-1626: - Do we really need to support this appender? Wasn't this one of

[jira] [Commented] (LOG4J2-1626) Port Windows Event Log Appender from Log4j 1.2

[ https://issues.apache.org/jira/browse/LOG4J2-1626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15535051#comment-15535051 ] Ralph Goers commented on LOG4J2-1626: - Please don't add this to the log4j 2 build. I would prefer we

[jira] [Created] (LOG4J2-1626) Port Windows Event Log Appender from Log4j 1.2

Gary Gregory created LOG4J2-1626: Summary: Port Windows Event Log Appender from Log4j 1.2 Key: LOG4J2-1626 URL: https://issues.apache.org/jira/browse/LOG4J2-1626 Project: Log4j 2 Issue Type:

[jira] [Closed] (LOG4J2-1620) 2.7-rc1: RollingFileAppender immediateFlush default value should be true, not false

[ https://issues.apache.org/jira/browse/LOG4J2-1620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sascha Scholz closed LOG4J2-1620. - Successfully tested master (6bedc20e375a54b7887ebff5b799f0612c314bf2) > 2.7-rc1:

[jira] [Resolved] (LOG4J2-1620) 2.7-rc1: RollingFileAppender immediateFlush default value should be true, not false

[ https://issues.apache.org/jira/browse/LOG4J2-1620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory resolved LOG4J2-1620. -- Resolution: Fixed Thank you for your report Sascha. Fixed in Git master. Please verify and

[jira] [Closed] (LOG4J2-1506) Unregister JMX ignores log4j2.disable.jmx property

[ https://issues.apache.org/jira/browse/LOG4J2-1506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Johannes Schleger closed LOG4J2-1506. - > Unregister JMX ignores log4j2.disable.jmx property >

Re: [VOTE] Release Log4j 2.7-rc1

Please wait to cut rc2, I am fixing a regression: https://issues.apache.org/jira/browse/LOG4J2-1620 Gary On Thu, Sep 29, 2016 at 9:31 AM, Mikael Ståldal wrote: > I created JIRA issues for the Kafka and Flume appender timeout issues, and > I have fixed both of them in

Re: logging-log4j2 git commit: LOG4J2-1506 patch by Johannes Schleger to catch Throwable instead of Exception

On Thu, Sep 29, 2016 at 8:50 AM, Remko Popma wrote: > Thank you. > YW :-) > > Sent from my iPhone > > On 29 Sep 2016, at 9:07, Gary Gregory wrote: > > On Wed, Sep 28, 2016 at 3:47 PM, Gary Gregory > wrote: > >> On Wed,

[jira] [Updated] (LOG4J2-1620) 2.7-rc1: RollingFileAppender immediateFlush default value should be true, not false

[ https://issues.apache.org/jira/browse/LOG4J2-1620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1620: - Summary: 2.7-rc1: RollingFileAppender immediateFlush default value should be true, not false

[jira] [Assigned] (LOG4J2-1620) 2.7-rc1: RollingFileAppender immediateFlush default value changed

[ https://issues.apache.org/jira/browse/LOG4J2-1620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory reassigned LOG4J2-1620: Assignee: Gary Gregory > 2.7-rc1: RollingFileAppender immediateFlush default value

[jira] [Updated] (LOG4J2-1620) 2.7-rc1: RollingFileAppender immediateFlush default value changed

[ https://issues.apache.org/jira/browse/LOG4J2-1620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1620: - Affects Version/s: (was: 2.7) > 2.7-rc1: RollingFileAppender immediateFlush default value

[jira] [Updated] (LOG4J2-1620) 2.7-rc1: RollingFileAppender immediateFlush default value changed

[ https://issues.apache.org/jira/browse/LOG4J2-1620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1620: - Affects Version/s: 2.7 > 2.7-rc1: RollingFileAppender immediateFlush default value changed >

[jira] [Updated] (LOG4J2-1623) Configurable JVM shutdown hook timeout

[ https://issues.apache.org/jira/browse/LOG4J2-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal updated LOG4J2-1623: --- Issue Type: Improvement (was: New Feature) > Configurable JVM shutdown hook timeout >

Re: [VOTE] Release Log4j 2.7-rc1

I created JIRA issues for the Kafka and Flume appender timeout issues, and I have fixed both of them in master branch. https://issues.apache.org/jira/browse/LOG4J2-1624 https://issues.apache.org/jira/browse/LOG4J2-1625 I also created a JIRA issue for the JVM shutdown hook, but that not as easy to

[jira] [Updated] (LOG4J2-1625) FlumeAppender get shutdown timeout 0

[ https://issues.apache.org/jira/browse/LOG4J2-1625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal updated LOG4J2-1625: --- Fix Version/s: 2.7 > FlumeAppender get shutdown timeout 0 >

[jira] [Resolved] (LOG4J2-1625) FlumeAppender get shutdown timeout 0

[ https://issues.apache.org/jira/browse/LOG4J2-1625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal resolved LOG4J2-1625. Resolution: Fixed > FlumeAppender get shutdown timeout 0 >

[jira] [Updated] (LOG4J2-1624) KafkaAppender get shutdown timeout 0

[ https://issues.apache.org/jira/browse/LOG4J2-1624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal updated LOG4J2-1624: --- Fix Version/s: 2.7 > KafkaAppender get shutdown timeout 0 >

[jira] [Resolved] (LOG4J2-1624) KafkaAppender get shutdown timeout 0

[ https://issues.apache.org/jira/browse/LOG4J2-1624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal resolved LOG4J2-1624. Resolution: Fixed > KafkaAppender get shutdown timeout 0 >

[jira] [Created] (LOG4J2-1625) FlumeAppender get shutdown timeout 0

Mikael Ståldal created LOG4J2-1625: -- Summary: FlumeAppender get shutdown timeout 0 Key: LOG4J2-1625 URL: https://issues.apache.org/jira/browse/LOG4J2-1625 Project: Log4j 2 Issue Type: Bug

[jira] [Created] (LOG4J2-1624) KafkaAppender get shutdown timeout 0

Mikael Ståldal created LOG4J2-1624: -- Summary: KafkaAppender get shutdown timeout 0 Key: LOG4J2-1624 URL: https://issues.apache.org/jira/browse/LOG4J2-1624 Project: Log4j 2 Issue Type: Bug

Re: logging-log4j2 git commit: LOG4J2-1506 patch by Johannes Schleger to catch Throwable instead of Exception

Thank you. Sent from my iPhone > On 29 Sep 2016, at 9:07, Gary Gregory wrote: > >> On Wed, Sep 28, 2016 at 3:47 PM, Gary Gregory wrote: >>> On Wed, Sep 28, 2016 at 3:43 PM, Remko Popma wrote: >>> Hm, ok. >>>

Re: [VOTE] Release Log4j 2.7-rc1

Yes please, only fix the blockers for rc2. We can make a 2.7.1 soon after with more fixes if needed. As Gary always says, RERO! On 29 September 2016 at 08:45, Ralph Goers wrote: > The release is already delayed. So far we have two compatibility issues > that need to

[jira] [Updated] (LOG4J2-1618) ClassCastException at shutdown with JUL: casting SimpleLogger to Logger

[ https://issues.apache.org/jira/browse/LOG4J2-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raman Gupta updated LOG4J2-1618: Affects Version/s: 2.7 > ClassCastException at shutdown with JUL: casting SimpleLogger to Logger >

Re: [VOTE] Release Log4j 2.7-rc1

The release is already delayed. So far we have two compatibility issues that need to be fixed. Please create a Jira issue for the Flume Appender and the JVM shutdown hook. Lets gets those fixed. And perhaps we should stop doing things that aren’t directly focused on getting the release out as

[jira] [Commented] (LOG4J2-1618) ClassCastException at shutdown with JUL: casting SimpleLogger to Logger

[ https://issues.apache.org/jira/browse/LOG4J2-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15532812#comment-15532812 ] Raman Gupta commented on LOG4J2-1618: - [~garydgregory] Attached is a simple reproduction recipe. Also

[jira] [Updated] (LOG4J2-1618) ClassCastException at shutdown with JUL: casting SimpleLogger to Logger

[ https://issues.apache.org/jira/browse/LOG4J2-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raman Gupta updated LOG4J2-1618: Attachment: test-log4j2-1618.tar.gz > ClassCastException at shutdown with JUL: casting

Re: logging-log4j2 git commit: LOG4J2-1506 patch by Johannes Schleger to catch Throwable instead of Exception

I agree that we should narrow the catching to Exception and LinkageError. On Thu, Sep 29, 2016 at 12:09 AM, Gary Gregory wrote: > On Wed, Sep 28, 2016 at 10:23 AM, Gary Gregory > wrote: > >> On Wed, Sep 28, 2016 at 10:18 AM, Remko Popma

Re: pruning old branches

I deleted scala-fast-location On Wed, Sep 28, 2016 at 6:48 PM, Remko Popma wrote: > Can any of these branches be deleted? > > origin/2.0-beta1 (Ralph) > origin/AutoCloseableLock (Gary) > origin/StyledMessage (Gary) > origin/StyledXException (Gary) >

Re: [VOTE] Release Log4j 2.7-rc1

I think that it is unfortunate that the close timeout is always zero within the standard JVM shutdown hook (LoggerContext.java:275). I think that should be configurable. However, I don't want to delay the release for that, so let's fix that after the 2.7 release.

[jira] [Created] (LOG4J2-1623) Configurable JVM shutdown hook timeout

Mikael Ståldal created LOG4J2-1623: -- Summary: Configurable JVM shutdown hook timeout Key: LOG4J2-1623 URL: https://issues.apache.org/jira/browse/LOG4J2-1623 Project: Log4j 2 Issue Type: New

[jira] [Commented] (LOG4J2-1622) how to config a DailyRollingFileAppender like log4j1.x

[ https://issues.apache.org/jira/browse/LOG4J2-1622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15532468#comment-15532468 ] Tboy commented on LOG4J2-1622: -- in log4j1.x, using DailyRollingFileAppender to generate a daily log file.

[jira] [Commented] (LOG4J2-1622) how to config a DailyRollingFileAppender like log4j1.x

[ https://issues.apache.org/jira/browse/LOG4J2-1622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15532381#comment-15532381 ] Remko Popma commented on LOG4J2-1622: - [~Tboy] Does the description answer the question, or are you

[jira] [Updated] (LOG4J2-1622) how to config a DailyRollingFileAppender like log4j1.x

[ https://issues.apache.org/jira/browse/LOG4J2-1622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-1622: Description: like this: {code}

[jira] [Created] (LOG4J2-1622) how to config a DailyRollingFileAppender like log4j1.x

Tboy created LOG4J2-1622: Summary: how to config a DailyRollingFileAppender like log4j1.x Key: LOG4J2-1622 URL: https://issues.apache.org/jira/browse/LOG4J2-1622 Project: Log4j 2 Issue Type:

[jira] [Created] (LOG4J2-1621) RollingFileAppender can't generate daily file according to cron expressions

Tboy created LOG4J2-1621: Summary: RollingFileAppender can't generate daily file according to cron expressions Key: LOG4J2-1621 URL: https://issues.apache.org/jira/browse/LOG4J2-1621 Project: Log4j 2

[jira] [Commented] (LOG4J2-1235) org.apache.logging.log4j.core.appender.routing.IdlePurgePolicy not working correctly

[ https://issues.apache.org/jira/browse/LOG4J2-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15532005#comment-15532005 ] Ralph Goers commented on LOG4J2-1235: - Thanks for the report. The 2.7 rc1 release failed due to

Jenkins build is back to stable : Log4j 2.x #2395

See - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org