[jira] [Updated] (LOG4J2-1130) CsvLogEventLayout NanoTime timestamp is always zero.

[ https://issues.apache.org/jira/browse/LOG4J2-1130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-1130: Fix Version/s: (was: 2.8.1) 2.8.2 > CsvLogEventLayout NanoTime timest

[jira] [Updated] (LOG4J2-1593) Concrete Filter implementations should override equals and hashCode

[ https://issues.apache.org/jira/browse/LOG4J2-1593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-1593: Fix Version/s: (was: 2.8.1) 2.8.2 > Concrete Filter implementations sho

[jira] [Updated] (LOG4J2-1116) Web app-friendly thread locals for gc-free logging (was: upgrade to log4j2 causes too frequent minor gc)

[ https://issues.apache.org/jira/browse/LOG4J2-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-1116: Fix Version/s: (was: 2.8.1) 2.8.2 > Web app-friendly thread locals for

[jira] [Updated] (LOG4J2-1813) Provide shorter and more intuitive way to switch on Log4j internal debug logging

[ https://issues.apache.org/jira/browse/LOG4J2-1813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-1813: Fix Version/s: (was: 2.8.1) 2.8.2 > Provide shorter and more intuitive

[jira] [Updated] (LOG4J2-1594) Add support for adding and removing Filters via JMX

[ https://issues.apache.org/jira/browse/LOG4J2-1594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-1594: Fix Version/s: (was: 2.8.1) 2.8.2 > Add support for adding and remov

[jira] [Updated] (LOG4J2-1198) Add support for custom rollover strategy

[ https://issues.apache.org/jira/browse/LOG4J2-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-1198: Fix Version/s: (was: 2.8.1) 2.8.2 > Add support for custom rollo

[jira] [Updated] (LOG4J2-1705) Kotlin wrapper for Log4j 2 API

[ https://issues.apache.org/jira/browse/LOG4J2-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-1705: Fix Version/s: (was: 2.8.1) 2.8.2 > Kotlin wrapper for Log4j 2

[jira] [Updated] (LOG4J2-1699) Configurable Log File Permissions with PosixFilePermission

[ https://issues.apache.org/jira/browse/LOG4J2-1699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-1699: Fix Version/s: (was: 2.8.1) 2.8.2 > Configurable Log File Permissi

[jira] [Updated] (LOG4J2-1534) Create alias 'statusDestination' for 'dest' attribute in Configuration

[ https://issues.apache.org/jira/browse/LOG4J2-1534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-1534: Fix Version/s: (was: 2.8.1) 2.8.2 > Create alias 'statusDestinat

Re: Log4j-provider.properties API version

Likewise, I suspect that ProviderUtil should only list 2.6.0 as a compatible version since the implementation must be at that level or higher. Ralph > On Mar 3, 2017, at 11:58 AM, Ralph Goers <ralph.go...@dslextreme.com> wrote: > > The Log4jAPIVersion in log4j-provider.propertie

Log4j-provider.properties API version

The Log4jAPIVersion in log4j-provider.properties in log4j-core says it supports the 2.1.0 API. Is that actually correct? I suspect that if you try to use the log4j 2.1 API jar with the log4j 2.8.1 core jar there will be problems. Doesn’t Log4j core require a Log4j API jar that is at least at

Performance page for next release.

Remko, Would it be possible for you to update the performance page for the next release? I am uncomfortable with some of the results because I know they have changed since 2.6. Ralph - To unsubscribe, e-mail:

Re: [ANNOUNCEMENT] Apache Log4j 2.8.1 released

sn't that what they use at GitHub?" :P > > On 3 March 2017 at 01:58, Remko Popma <remko.po...@gmail.com > <mailto:remko.po...@gmail.com>> wrote: > >> Blogged: https://blogs.apache.org/logging/entry/log4j-2-8-1-released >> >> >> On Fr

[ANNOUNCEMENT] Apache Log4j 2.8.1 released

The Apache Log4j 2 team is pleased to announce the Log4j 2.8.1 release! Apache Log4j is a well known framework for logging application behavior. Log4j 2 is an upgrade to Log4j that provides significant improvements over its predecessor, Log4j 1.x, and provides many other modern features such as

[jira] [Commented] (LOG4J2-1832) Programmatical Configuration of Log4j2 with RollingFileAppender does not honor logging classnames

[ https://issues.apache.org/jira/browse/LOG4J2-1832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15892691#comment-15892691 ] Ralph Goers commented on LOG4J2-1832: - You appear to be adding to an existing configuration

[VOTE][RESULT] Log4j 2.8.1 rc1

The release vote has passed with binding +1 votes from Gary Gregory, Matt Sicker, Remko Popma, and Ralph Goers. Thanks to all who voted. I will continue on with the release process. Ralph - To unsubscribe, e-mail: log4j-dev

Re: [VOTE] Release Log4j 2.8.1-rc1

Here is my +1 Ralph > On Mar 1, 2017, at 8:47 AM, Remko Popma <remko.po...@gmail.com> wrote: > > +1 > > Sent from my iPhone > > On Feb 27, 2017, at 3:09, Ralph Goers <ralph.go...@dslextreme.com > <mailto:ralph.go...@dslextreme.com>> wrote: > >

Re: Roadmap for 2.8.1

t;> about the whole splitting up the release. >> >> Perhaps a diagram would help clarify my understanding. (I think there's >> already a JIRA or an epic for the above. Adding some diagrams there would be >> very useful.) >> >> Remko >> >> On Tue, Feb 2

[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=1500#comment-1500 ] Ralph Goers commented on LOG4J2-1828: - Look at FileManager.write(). You will see it acquire the file

[jira] [Closed] (LOG4J2-1827) Separate integration tests out of core to speed up build

[ https://issues.apache.org/jira/browse/LOG4J2-1827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers closed LOG4J2-1827. --- Resolution: Fixed > Separate integration tests out of core to speed up bu

[jira] [Created] (LOG4J2-1827) Separate integration tests out of core to speed up build

Ralph Goers created LOG4J2-1827: --- Summary: Separate integration tests out of core to speed up build Key: LOG4J2-1827 URL: https://issues.apache.org/jira/browse/LOG4J2-1827 Project: Log4j 2

[jira] [Commented] (LOG4J2-174) Multiple instances of same application server cause 2 problems - want to know if they are solved in log4j 2

[ https://issues.apache.org/jira/browse/LOG4J2-174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15887239#comment-15887239 ] Ralph Goers commented on LOG4J2-174: Rather than reopen this issue, if you would care to create a new

[jira] [Commented] (LOG4J2-174) Multiple instances of same application server cause 2 problems - want to know if they are solved in log4j 2

[ https://issues.apache.org/jira/browse/LOG4J2-174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15887227#comment-15887227 ] Ralph Goers commented on LOG4J2-174: Log4j 2.8 now supports omitting the file name

Re: Roadmap for 2.8.1

om the log4j-scala repo when two of the three artifacts will > already exist. > > On 27 February 2017 at 12:14, Ralph Goers <ralph.go...@dslextreme.com > <mailto:ralph.go...@dslextreme.com>> wrote: > Why is the release of log4j-scala delayed? > > Ralph > >&g

Re: Roadmap for 2.8.1

Why is the release of log4j-scala delayed? Ralph > On Feb 27, 2017, at 10:23 AM, Mikael Ståldal > wrote: > > I would really like LOG4J2-1661 and LOG4J2-1690 out in the next release. > > I implemented LOG4J2-1690 only in the new log4j-scala repo since I thought >

Re: Experimenting with NIO

I’m not sure what these numbers mean as I don’t know what you’ve changed and how they compare to what was there previously. Ralph > On Feb 26, 2017, at 9:44 PM, Matt Sicker wrote: > > Anyways, I managed to implement MemoryMappedFileAppender in the playground by > basically

[VOTE] Release Log4j 2.8.1-rc1

This is a vote to release Log4j 2.8.1 the next version of the Log4j 2 project. Please download, test, and cast your votes on the log4j developers list. [] +1, release the artifacts [] -1, don't release because... The vote will remain open for 72 hours (or more if required). All votes are

Re: Release Notes

gt; > > See how it formats it? Then you can copy/paste from that page into an email > or blog post. > > On 26 February 2017 at 17:42, Ralph Goers <ralph.go...@dslextreme.com > <mailto:ralph.go...@dslextreme.com>> wrote: > I don’t understand. What does the RELEASE

Re: Release Notes

Matt Sicker is doing some work on this can you contact him he can explain > better them me, thank's >> On Feb 26, 2017, at 3:42 PM, Ralph Goers <ralph.go...@dslextreme.com >> <mailto:ralph.go...@dslextreme.com>> wrote: >> >> I don’t understand. What do

Re: Release Notes

Afonso, Your emails don’t make any sense. My emails weren’t directed to you so I don’t know why you are replying to them. Ralph > On Feb 26, 2017, at 4:30 PM, Afonso Murakami wrote: > > ok thank you I knew you can figure it out and I didn’t change anything like I >

Re: Release Notes

I don’t understand. What does the RELEASE-NOTES.txt file have to do with Jira? What generated HTML? The text file is the result of running the Maven command and is what I past into the email. Ralph > On Feb 26, 2017, at 4:27 PM, Matt Sicker wrote: > > I renamed it to .md

[jira] [Resolved] (LOG4J2-1826) InterruptedException on RollingFileManager#rollover()

[ https://issues.apache.org/jira/browse/LOG4J2-1826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-1826. - Resolution: Duplicate > InterruptedException on RollingFileManager#rollo

[jira] [Commented] (LOG4J2-1798) InterruptedException on RollingFileManager#rollover()

[ https://issues.apache.org/jira/browse/LOG4J2-1798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15884570#comment-15884570 ] Ralph Goers commented on LOG4J2-1798: - Can you please try this with 2.8. Some changes were made

[jira] [Commented] (LOG4J2-1423) org.apache.logging.log4j.flume.appender.FlumeAppenderTest.testIncompleteBatch hangs

[ https://issues.apache.org/jira/browse/LOG4J2-1423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15884567#comment-15884567 ] Ralph Goers commented on LOG4J2-1423: - Is this still happening

[jira] [Assigned] (LOG4J2-1584) RFC5424 layout needs better delimiter specification between message and throwable

[ https://issues.apache.org/jira/browse/LOG4J2-1584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers reassigned LOG4J2-1584: --- Assignee: Ralph Goers > RFC5424 layout needs better delimiter specification between mess

[jira] [Commented] (LOG4J2-1455) CompositeConfiguration Logger level not overridable

[ https://issues.apache.org/jira/browse/LOG4J2-1455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15884566#comment-15884566 ] Ralph Goers commented on LOG4J2-1455: - So is this still a problem or can it be closed

[jira] [Commented] (LOG4J2-1376) RFC5424 Enterprise Number should be an OID fragment.

[ https://issues.apache.org/jira/browse/LOG4J2-1376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15884565#comment-15884565 ] Ralph Goers commented on LOG4J2-1376: - Any update on this? > RFC5424 Enterprise Number sho

[jira] [Commented] (LOG4J2-1768) MDC.clear() is broken in Log4j-1_2-api = 2.4

[ https://issues.apache.org/jira/browse/LOG4J2-1768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15884562#comment-15884562 ] Ralph Goers commented on LOG4J2-1768: - Any update? We will have to close this issue if we can't get

[jira] [Resolved] (LOG4J2-1821) (not only) default rollover strategy is *broken*

[ https://issues.apache.org/jira/browse/LOG4J2-1821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-1821. - Resolution: Fixed > (not only) default rollover strategy is *bro

[jira] [Closed] (LOG4J2-546) Commons logging integration does not work in WildFly 8.0

[ https://issues.apache.org/jira/browse/LOG4J2-546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers closed LOG4J2-546. -- > Commons logging integration does not work in WildFly

[jira] [Resolved] (LOG4J2-546) Commons logging integration does not work in WildFly 8.0

[ https://issues.apache.org/jira/browse/LOG4J2-546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-546. Resolution: Won't Fix I am closing this as "won't fix" because based on Matt's research

[jira] [Commented] (LOG4J2-1784) Large values for max in DefaultRolloverStrategy blocks application

[ https://issues.apache.org/jira/browse/LOG4J2-1784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15884556#comment-15884556 ] Ralph Goers commented on LOG4J2-1784: - Any update on this? > Large values for

[jira] [Commented] (LOG4J2-1086) SizeBasedTriggeringPolicy is not working properly

[ https://issues.apache.org/jira/browse/LOG4J2-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15884555#comment-15884555 ] Ralph Goers commented on LOG4J2-1086: - Is there any update on this? > SizeBasedTriggeringPol

[jira] [Resolved] (LOG4J2-1804) Rolling file %i based rolling broken in 2.8

[ https://issues.apache.org/jira/browse/LOG4J2-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-1804. - Resolution: Fixed Fix Version/s: 2.8.1 A modified version of the patch and test were

[jira] [Resolved] (LOG4J2-1822) Upgrade SLF4J to version 1.7.24

[ https://issues.apache.org/jira/browse/LOG4J2-1822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-1822. - Resolution: Fixed > Upgrade SLF4J to version 1.7

[jira] [Closed] (LOG4J2-1822) Upgrade SLF4J to version 1.7.24

[ https://issues.apache.org/jira/browse/LOG4J2-1822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers closed LOG4J2-1822. --- > Upgrade SLF4J to version 1.7.24 > --- > > Key:

[jira] [Created] (LOG4J2-1822) Upgrade SLF4J to version 1.7.24

Ralph Goers created LOG4J2-1822: --- Summary: Upgrade SLF4J to version 1.7.24 Key: LOG4J2-1822 URL: https://issues.apache.org/jira/browse/LOG4J2-1822 Project: Log4j 2 Issue Type: Improvement

[jira] [Assigned] (LOG4J2-1804) Rolling file %i based rolling broken in 2.8

[ https://issues.apache.org/jira/browse/LOG4J2-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers reassigned LOG4J2-1804: --- Assignee: Ralph Goers > Rolling file %i based rolling broken in

[jira] [Resolved] (LOG4J2-1815) An exception occurred processing Appender RollingFileMain java.lang.NullPointerException

[ https://issues.apache.org/jira/browse/LOG4J2-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-1815. - Resolution: Fixed Fix Version/s: 2.8.1 > An exception occurred processing Appen

[jira] [Commented] (LOG4J2-1630) Unit of Work Logging

[ https://issues.apache.org/jira/browse/LOG4J2-1630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15872588#comment-15872588 ] Ralph Goers commented on LOG4J2-1630: - I'm doing all that in the services we have created. We just

[jira] [Commented] (LOG4J2-1817) Can AbstractManager close managers after it has let go of the lock?

[ https://issues.apache.org/jira/browse/LOG4J2-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868135#comment-15868135 ] Ralph Goers commented on LOG4J2-1817: - Can't you just override the stop method to do: {code} public

[jira] [Commented] (LOG4J2-1691) Setup build process for new Git repo logging-log4j-scala, including site

[ https://issues.apache.org/jira/browse/LOG4J2-1691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15866117#comment-15866117 ] Ralph Goers commented on LOG4J2-1691: - I know how to do it but work constantly seems to be sucking up

[jira] [Commented] (LOG4J2-1811) Log4j 2 configuration/usage ergonomics

[ https://issues.apache.org/jira/browse/LOG4J2-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15862680#comment-15862680 ] Ralph Goers commented on LOG4J2-1811: - I have my doubts about how possible that is. Most of the blogs

[jira] [Commented] (LOG4J2-1812) Improve error message when log4j 2 configuration file not found

[ https://issues.apache.org/jira/browse/LOG4J2-1812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15862677#comment-15862677 ] Ralph Goers commented on LOG4J2-1812: - I had always intended to have the capability to dump the ring

[jira] [Commented] (LOG4J2-1813) Provide shorter and more intuitive way to switch on Log4j internal debug logging

[ https://issues.apache.org/jira/browse/LOG4J2-1813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15862675#comment-15862675 ] Ralph Goers commented on LOG4J2-1813: - If I am not mistaken, the change Matt just implemented should

[jira] [Commented] (LOG4J2-1811) Log4j 2 configuration/usage ergonomics

[ https://issues.apache.org/jira/browse/LOG4J2-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15862655#comment-15862655 ] Ralph Goers commented on LOG4J2-1811: - I'm all for documentation, but I have to note that I just went

[jira] [Commented] (LOG4J2-1259) Log4j threads are leaking on Tomcat shutdown

[ https://issues.apache.org/jira/browse/LOG4J2-1259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15860840#comment-15860840 ] Ralph Goers commented on LOG4J2-1259: - I believe this is most likely fixed in 2.8. Can someone please

[jira] [Reopened] (LOG4J2-1810) Upgrade Logback to version 1.1.10

[ https://issues.apache.org/jira/browse/LOG4J2-1810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers reopened LOG4J2-1810: - Update to Logback 1.2 > Upgrade Logback to version 1.1

[jira] [Updated] (LOG4J2-1810) Upgrade Logback to version 1.2

[ https://issues.apache.org/jira/browse/LOG4J2-1810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-1810: Summary: Upgrade Logback to version 1.2 (was: Upgrade Logback to version 1.1.10) > Upgr

[jira] [Resolved] (LOG4J2-1810) Upgrade Logback to version 1.1.10

[ https://issues.apache.org/jira/browse/LOG4J2-1810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-1810. - Resolution: Fixed > Upgrade Logback to version 1.1

[jira] [Closed] (LOG4J2-1810) Upgrade Logback to version 1.1.10

[ https://issues.apache.org/jira/browse/LOG4J2-1810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers closed LOG4J2-1810. --- > Upgrade Logback to version 1.1.10 > - > >

[jira] [Created] (LOG4J2-1810) Upgrade Logback to version 1.1.10

Ralph Goers created LOG4J2-1810: --- Summary: Upgrade Logback to version 1.1.10 Key: LOG4J2-1810 URL: https://issues.apache.org/jira/browse/LOG4J2-1810 Project: Log4j 2 Issue Type: Bug

[jira] [Commented] (LOG4J2-1809) Add global configuration environment SPI

[ https://issues.apache.org/jira/browse/LOG4J2-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15853346#comment-15853346 ] Ralph Goers commented on LOG4J2-1809: - I see no need to make core dependent on any commons components

Re: FileAppenderBenchmark

Yes. Ralph > On Jan 28, 2017, at 11:59 PM, Remko Popma wrote: > > Ralph, are your benchmark results with 4 threads (-t 4)? > >> On Sun, Jan 29, 2017 at 5:51 PM, Apache wrote: >> While I couldn’t get it to work with Log4j 2.8 the results I

Re: [VOTE] Release Log4j 2.8-rc1

Is anyone going to vote on the rc? Ralph > On Jan 21, 2017, at 11:08 PM, Ralph Goers <ralph.go...@dslextreme.com> wrote: > > This is a vote to release Log4j 2.8 the next version of the Log4j 2 project. > > Please download, test, and cast your votes on the log4j dev

[VOTE] Release Log4j 2.8-rc1

This is a vote to release Log4j 2.8 the next version of the Log4j 2 project. Please download, test, and cast your votes on the log4j developers list. [] +1, release the artifacts [] -1, don't release because... The vote will remain open for 72 hours (or more if required). All votes are welcome

[jira] [Commented] (LOG4J2-1768) MDC.clear() is broken in Log4j-1_2-api = 2.4

[ https://issues.apache.org/jira/browse/LOG4J2-1768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15833134#comment-15833134 ] Ralph Goers commented on LOG4J2-1768: - Can you provide a test that fails for this? I don't see

[jira] [Commented] (LOG4J2-1795) LogEvent serialization deserialization

[ https://issues.apache.org/jira/browse/LOG4J2-1795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15832174#comment-15832174 ] Ralph Goers commented on LOG4J2-1795: - I suspect that Jira issue would be closed as "won'

Re: github

So I can't accept the PR unless I have made at least one comment? Ralph > On Jan 18, 2017, at 9:08 AM, Matt Sicker wrote: > > The commit count statistics have always been a silly function of GitHub. See > for example . > > As for

[jira] [Commented] (LOG4J2-587) log4j-1.2-api emulation jar missing classes

[ https://issues.apache.org/jira/browse/LOG4J2-587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15826507#comment-15826507 ] Ralph Goers commented on LOG4J2-587: Can you provide the stack trace for the error you get

[jira] [Updated] (LOG4J2-1790) RollingFile deletes daily file

[ https://issues.apache.org/jira/browse/LOG4J2-1790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-1790: Description: When configured to save one file per day, the log file from a previous date

[jira] [Commented] (LOG4J2-1788) Create Apache Logging parent pom

[ https://issues.apache.org/jira/browse/LOG4J2-1788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15825497#comment-15825497 ] Ralph Goers commented on LOG4J2-1788: - Note that a release of this pom will be required before any

[jira] [Commented] (LOG4J2-1243) Faulty placeholder substitution in config xml

[ https://issues.apache.org/jira/browse/LOG4J2-1243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15825493#comment-15825493 ] Ralph Goers commented on LOG4J2-1243: - OK. I modified XmlLoggerPropsTest and verified the problem you

[jira] [Comment Edited] (LOG4J2-1784) Large values for max in DefaultRolloverStrategy blocks application

[ https://issues.apache.org/jira/browse/LOG4J2-1784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15824618#comment-15824618 ] Ralph Goers edited comment on LOG4J2-1784 at 1/16/17 9:39 PM: -- I thought I

[jira] [Commented] (LOG4J2-1784) Large values for max in DefaultRolloverStrategy blocks application

[ https://issues.apache.org/jira/browse/LOG4J2-1784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15824618#comment-15824618 ] Ralph Goers commented on LOG4J2-1784: - I thought I updated this but I don't see the changes. I

[jira] [Resolved] (LOG4J2-1589) Value nesting during property substitution

[ https://issues.apache.org/jira/browse/LOG4J2-1589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-1589. - Resolution: Fixed Fix Version/s: 2.8 This should be addressed by the fix for LOG4J2-1243

[jira] [Resolved] (LOG4J2-1243) Faulty placeholder substitution in config xml

[ https://issues.apache.org/jira/browse/LOG4J2-1243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-1243. - Resolution: Fixed Fix Version/s: 2.8 A fix has been committed to master. Please verify

[jira] [Resolved] (LOG4J2-1032) Rollover startegy failing on high load

[ https://issues.apache.org/jira/browse/LOG4J2-1032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-1032. - Resolution: Fixed Fix Version/s: 2.8 The fix for this is now in master. It consists of 2

[jira] [Commented] (LOG4J2-1101) Date based file appender

[ https://issues.apache.org/jira/browse/LOG4J2-1101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15823521#comment-15823521 ] Ralph Goers commented on LOG4J2-1101: - Yes, it should, although I didn't test it. I am also just

[jira] [Resolved] (LOG4J2-907) Log4j2 rolling policy

[ https://issues.apache.org/jira/browse/LOG4J2-907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-907. Resolution: Fixed Fix Version/s: 2.8 This has been implemented in master. Please verify

[jira] [Resolved] (LOG4J2-1185) Ability to change the fileName dynamically in RollingFileAppender

[ https://issues.apache.org/jira/browse/LOG4J2-1185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-1185. - Resolution: Fixed Fix Version/s: 2.8 This has been implemented in master. Please verify

[jira] [Resolved] (LOG4J2-1101) Date based file appender

[ https://issues.apache.org/jira/browse/LOG4J2-1101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-1101. - Resolution: Fixed Fix Version/s: 2.8 The fix for this has been committed in master

[jira] [Comment Edited] (LOG4J2-1784) Large values for max in DefaultRolloverStrategy blocks application

[ https://issues.apache.org/jira/browse/LOG4J2-1784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15823016#comment-15823016 ] Ralph Goers edited comment on LOG4J2-1784 at 1/15/17 3:25 AM: -- Actually

[jira] [Assigned] (LOG4J2-1784) Large values for max in DefaultRolloverStrategy blocks application

[ https://issues.apache.org/jira/browse/LOG4J2-1784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers reassigned LOG4J2-1784: --- Assignee: Ralph Goers > Large values for max in DefaultRolloverStrategy blocks applicat

[jira] [Updated] (LOG4J2-1784) Large values for max in DefaultRolloverStrategy blocks application

[ https://issues.apache.org/jira/browse/LOG4J2-1784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-1784: Issue Type: Improvement (was: Bug) > Large values for max in DefaultRolloverStrategy blo

[jira] [Commented] (LOG4J2-1748) RollingFile appender prevents a stand alone application to terminate for as long as 60 sec

[ https://issues.apache.org/jira/browse/LOG4J2-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15820023#comment-15820023 ] Ralph Goers commented on LOG4J2-1748: - I have no problem using the ThreadFactory to create the thread

[jira] [Commented] (LOG4J2-1780) LoggerContext does not shut down old executor services when creating new ones during reconfiguration

[ https://issues.apache.org/jira/browse/LOG4J2-1780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15819347#comment-15819347 ] Ralph Goers commented on LOG4J2-1780: - I don't see the problem. It is owned by the Configuration so

[jira] [Commented] (LOG4J2-1748) RollingFile appender prevents a stand alone application to terminate for as long as 60 sec

[ https://issues.apache.org/jira/browse/LOG4J2-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15819341#comment-15819341 ] Ralph Goers commented on LOG4J2-1748: - We have an ExecutorService. It is called

[jira] [Commented] (LOG4J2-1780) LoggerContext does not shut down old executor services when creating new ones during reconfiguration

[ https://issues.apache.org/jira/browse/LOG4J2-1780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15819309#comment-15819309 ] Ralph Goers commented on LOG4J2-1780: - The LoggerContext should not have any ExecutorServices

[jira] [Commented] (LOG4J2-1748) RollingFile appender prevents a stand alone application to terminate for as long as 60 sec

[ https://issues.apache.org/jira/browse/LOG4J2-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15819275#comment-15819275 ] Ralph Goers commented on LOG4J2-1748: - Again, lets just get rid of these ExecutorService instances

[jira] [Commented] (LOG4J2-1748) RollingFile appender prevents a stand alone application to terminate for as long as 60 sec

[ https://issues.apache.org/jira/browse/LOG4J2-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15819273#comment-15819273 ] Ralph Goers commented on LOG4J2-1748: - I don't think that is a great recommendation. > RollingF

[jira] [Comment Edited] (LOG4J2-1748) RollingFile appender prevents a stand alone application to terminate for as long as 60 sec

[ https://issues.apache.org/jira/browse/LOG4J2-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15819273#comment-15819273 ] Ralph Goers edited comment on LOG4J2-1748 at 1/11/17 9:44 PM: -- I don't think

[jira] [Commented] (LOG4J2-1748) RollingFile appender prevents a stand alone application to terminate for as long as 60 sec

[ https://issues.apache.org/jira/browse/LOG4J2-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15819271#comment-15819271 ] Ralph Goers commented on LOG4J2-1748: - I don't know why those two ThreadPoolExecutors were added

[jira] [Commented] (LOG4J2-1640) RollingFileAppender with CronTriggeringPolicy broken?

[ https://issues.apache.org/jira/browse/LOG4J2-1640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15816297#comment-15816297 ] Ralph Goers commented on LOG4J2-1640: - Yes, you would need to re-clone and re-build. If you want

[jira] [Commented] (LOG4J2-1776) log4j-starter pom modules for dependency management

[ https://issues.apache.org/jira/browse/LOG4J2-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15813291#comment-15813291 ] Ralph Goers commented on LOG4J2-1776: - +1 for log4j-boot. > log4j-starter pom modules for depende

[jira] [Commented] (LOG4J2-1640) RollingFileAppender with CronTriggeringPolicy broken?

[ https://issues.apache.org/jira/browse/LOG4J2-1640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15812841#comment-15812841 ] Ralph Goers commented on LOG4J2-1640: - No. As I said, System.nanotime() is relative to the time

[jira] [Resolved] (LOG4J2-1640) RollingFileAppender with CronTriggeringPolicy broken?

[ https://issues.apache.org/jira/browse/LOG4J2-1640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-1640. - Resolution: Fixed Fix Version/s: 2.8 Please verify and close. > RollingFileAppen

[jira] [Commented] (LOG4J2-1640) RollingFileAppender with CronTriggeringPolicy broken?

[ https://issues.apache.org/jira/browse/LOG4J2-1640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15812045#comment-15812045 ] Ralph Goers commented on LOG4J2-1640: - So it turns out that the ScheduledExecutorServices in Java use

[jira] [Commented] (LOG4J2-1748) RollingFile appender prevents a stand alone application to terminate for as long as 60 sec

[ https://issues.apache.org/jira/browse/LOG4J2-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15810287#comment-15810287 ] Ralph Goers commented on LOG4J2-1748: - Has this been tested with the latest code in master? I have

[jira] [Commented] (LOG4J2-1640) RollingFileAppender with CronTriggeringPolicy broken?

[ https://issues.apache.org/jira/browse/LOG4J2-1640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15810046#comment-15810046 ] Ralph Goers commented on LOG4J2-1640: - I finally got it to happen again. The cron event is firing

<    1   2   3   4   5   6   7   8   9   10   >