[jira] [Commented] (LOG4J2-1226) Message instances are simply serialized. They mustn't.

[ https://issues.apache.org/jira/browse/LOG4J2-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15370656#comment-15370656 ] Ralph Goers commented on LOG4J2-1226: - 1. I understand the arguments you are making (and pretty much

[jira] [Commented] (LOG4J2-1279) NullPointerException in FastDateParser$TimeZoneStrategy

[ https://issues.apache.org/jira/browse/LOG4J2-1279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15370233#comment-15370233 ] Ralph Goers commented on LOG4J2-1279: - I'm sure I could do that by the time 2.7 is released unless

[jira] [Commented] (LOG4J2-1226) Message instances are simply serialized. They mustn't.

[ https://issues.apache.org/jira/browse/LOG4J2-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15370227#comment-15370227 ] Ralph Goers commented on LOG4J2-1226: - Joern, is there any possibility of using some other

Re: [ANNOUNCEMENT] Log

> On Mon, Jul 11, 2016 at 4:31 AM, Ralph Goers <ralph.go...@dslextreme.com > <mailto:ralph.go...@dslextreme.com>> wrote: > The Apache Log4j 2 team is pleased to announce the Log4j 2.6.2 release! > > Apache Log4j is a well known framework for logging application behavior.

Re: [ANNOUNCEMENT] Log

gs.apache.org/logging/entry/log4j_2_6_2_released > <https://blogs.apache.org/logging/entry/log4j_2_6_2_released> > > On Mon, Jul 11, 2016 at 4:31 AM, Ralph Goers <ralph.go...@dslextreme.com > <mailto:ralph.go...@dslextreme.com>> wrote: > The Apache Log4j 2 team

[ANNOUNCEMENT] Log

2-1414: Fixed minor issues with the 2.6.1 web site. Thanks to Ralph Goers. o LOG4J2-1434: Ensure that the thread-local StringBuilders used by Layouts to format log events to text will not retain excessive memory after a large message was logged. Thanks to Luke Butters. o LOG4J2-1418: Pro

Logging web site

I have removed Log4j 1 from the main logging site and changed the title to just Log4j. The Log4j site has a link to Log4j 1. Log4j extras is still on the main site but should probably also be moved to the Legacy area of the Log4j site. Also, the Log4j site continues to say Log4j 2

[VOTE][RESULT] Log4j 2.6.2 rc1

The vote has passed with binding +1 votes from Mikael Ståldal, Matt Sicker, Gary Gregory, Remko Popma, and Ralph Goers. Leon Finker also voted +1. There were no other votes. Thanks to all who voted. I will be continuing the release process today. Ralph

[jira] [Commented] (LOG4J2-1447) Garbage-free data structure for LogEvent's context map data

[ https://issues.apache.org/jira/browse/LOG4J2-1447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15369128#comment-15369128 ] Ralph Goers commented on LOG4J2-1447: - Yes, that looks fine. > Garbage-free data struct

Re: Start configuration snippet for log4j2.properties?

Remko and I try to answer questions on stackoverflow as quickly as possible. I just responded to yours. But to be honest, you probably could have gotten this from the manual online. All I really did was take the example from the manual and tailor it a little bit for use in a Maven build.

Re: [VOTE] Log4j 2.6.2 rc1

The web site is corrected. It had the 4 items but with an odd icon. I’ve updated changes.xml and RELEASE_NOTES.txt. While they won’t be in the release distribution RELEASE_NOTES.txt is used for the announcement email. Ralph > On Jul 6, 2016, at 8:23 AM, Ralph Goers <ralph.go...@dslextre

[jira] [Commented] (LOG4J2-1457) Class loader deadlock when using async logging

[ https://issues.apache.org/jira/browse/LOG4J2-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15364978#comment-15364978 ] Ralph Goers commented on LOG4J2-1457: - That is a very good observation. Do you think you could make

[jira] [Comment Edited] (LOG4J2-1457) Class loader deadlock when using async logging

[ https://issues.apache.org/jira/browse/LOG4J2-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15364804#comment-15364804 ] Ralph Goers edited comment on LOG4J2-1457 at 7/6/16 6:23 PM: - I found https

[jira] [Commented] (LOG4J2-1457) Class loader deadlock when using async logging

[ https://issues.apache.org/jira/browse/LOG4J2-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15364804#comment-15364804 ] Ralph Goers commented on LOG4J2-1457: - I found https://bugs.openjdk.java.net/browse/JDK-8072592

Re: [jira] [Updated] (LOG4J2-1457) Class loader deadlock when using async logging

Do you know what the exception is and where it originated from? Does it correlate in any way to the other threads that are marked as runnable? Ralph > On Jul 6, 2016, at 8:14 AM, Leon Finker wrote: > > Although I'm still not clear why it deadlocks. I can confirm the thread

[jira] [Commented] (LOG4J2-1457) Class loader deadlock when using async logging

[ https://issues.apache.org/jira/browse/LOG4J2-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15364522#comment-15364522 ] Ralph Goers commented on LOG4J2-1457: - The workaround for this would be to modify your pattern layout

Re: [VOTE] Log4j 2.6.2 rc1

<mikael.stal...@magine.com >> <mailto:mikael.stal...@magine.com>> wrote: >> What about https://issues.apache.org/jira/browse/LOG4J2-1452 >> <https://issues.apache.org/jira/browse/LOG4J2-1452> >> >> On Wed, Jul 6, 2016 at 7:53 AM, Ralph Goers <ralph.

Re: [VOTE] Log4j 2.6.2 rc1

t; >> >> Fix bug in OnStartupTriggeringPolicy that allowed it to roll over on every >> reconfiguration. Added >> minSize attribute. >> >> >> On Wed, Jul 6, 2016 at 9:50 AM, Mikael Ståldal <mikael.stal...@magine.com >> <mailto:mikael

[VOTE] Log4j 2.6.2 rc1

utility's ringbuffer of StringBuilders is now configurable. Fixed Bugs: o LOG4J2-1414: Fixed minor issues with the 2.6.1 web site. Thanks to Ralph Goers. o LOG4J2-1434: Ensure that the thread-local StringBuilders used by Layouts to format log events to text will not retain excessive me

Re: Jenkins build became unstable: Log4j 2.x #2089

Yeah, guess I need to change the test logic. Ralph > On Jul 5, 2016, at 8:25 PM, Matt Sicker wrote: > > What a great start to 2.6.3-SNAPSHOT ;) > > On 5 July 2016 at 22:10, Apache Jenkins Server > wrote: > See

Re: 2.6.2?

OK. Then I think the changes for the site are done. I will start the release when I get home this afternoon. Ralph > On Jul 5, 2016, at 7:01 AM, Remko Popma <remko.po...@gmail.com> wrote: > > > > On Tue, Jul 5, 2016 at 3:28 PM, Ralph Goers <ralph.go...@dslextreme

Re: 2.6.2?

ee http://glyphicons.com/ <http://glyphicons.com/> > > Not sure yet how it works exactly. > > > On Tue, Jul 5, 2016 at 3:28 PM, Ralph Goers <ralph.go...@dslextreme.com > <mailto:ralph.go...@dslextreme.com>> wrote: > I added the “Legacy” links to the home page b

Re: 2.6.2?

can help with these two issues I would appreciate it. Ralph > On Jul 4, 2016, at 9:18 PM, Matt Sicker <boa...@gmail.com> wrote: > > Have fun! > > On 4 July 2016 at 18:50, Ralph Goers <ralph.go...@dslextreme.com > <mailto:ralph.go...@dslextreme.com>> wrote:

Re: My upcoming availability

Hopefully it will go as easily for you as it did for me. Ralph > On Jul 4, 2016, at 10:10 PM, Matt Sicker wrote: > > I've been trying to avoid it all my life, but this Thursday, July 7, I'm > getting my wisdom teeth removed. I may be gone for a few days while I recover. >

[jira] [Commented] (LOG4J2-904) RollingFile appender doesn't zip and create new files

[ https://issues.apache.org/jira/browse/LOG4J2-904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15362034#comment-15362034 ] Ralph Goers commented on LOG4J2-904: I don't understand why you keep asking about use cases involving

[jira] [Comment Edited] (LOG4J2-904) RollingFile appender doesn't zip and create new files

[ https://issues.apache.org/jira/browse/LOG4J2-904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15361842#comment-15361842 ] Ralph Goers edited comment on LOG4J2-904 at 7/4/16 11:52 PM: - No different

Re: 2.6.2?

Gary, Can you create a logo for 2.6.2? Just use the next one in line. Ralph > On Jul 4, 2016, at 11:03 AM, Ralph Goers <ralph.go...@dslextreme.com> wrote: > > Yes - I am also cleaning the BBQ. I have about 5 hours before people show up > at my house. We are just going

[jira] [Resolved] (LOG4J2-904) RollingFile appender doesn't zip and create new files

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

Re: Jenkins build became unstable: Log4j 2.x #2085

Yup. I just added some more logging to help identify the problem. Ralph > On Jul 4, 2016, at 12:15 PM, Matt Sicker wrote: > > New test failure: RollingAppenderCronTest. > > On 4 July 2016 at 14:03, Apache Jenkins Server

Re: 2.6.2?

; On Mon, Jul 4, 2016 at 10:45 AM, Ralph Goers <ralph.go...@dslextreme.com > <mailto:ralph.go...@dslextreme.com>> wrote: > I haven’t started it yet. I just committed a fix for LOG4J2-1250 and am about > to commit the patch for LOG4J2-950 that was just provided. I also plan to

Re: 2.6.2?

it to himself :-) >> >> Gary >> >> On Wed, Jun 29, 2016 at 3:26 PM, Gary Gregory <garydgreg...@gmail.com >> <mailto:garydgreg...@gmail.com>> wrote: >> On Mon, Jun 27, 2016 at 8:18 AM, Ralph Goers <ralph.go...@dslextreme.com >> <mailto:r

Re: Jenkins build became unstable: Log4j 2.x #2082

all our threads? That would be an easy way to > shutdown threads. > > Thoughts? > > Happy 4th to US folks! > > Gary > > On Jul 4, 2016 6:41 AM, "Ralph Goers" <ralph.go...@dslextreme.com > <mailto:ralph.go...@dslextreme.com>> wrote: > This is a bug i

Re: Jenkins build became unstable: Log4j 2.x #2082

threads. > > Thoughts? > > Happy 4th to US folks! > > Gary > >> On Jul 4, 2016 6:41 AM, "Ralph Goers" <ralph.go...@dslextreme.com> wrote: >> This is a bug in CleanFolders. If it encounters an error deleting files it >> retries deleting

[jira] [Resolved] (LOG4J2-1250) [2.5] CronTriggeringPolicy renaming behavior when midnight.

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

[jira] [Commented] (LOG4J2-1250) [2.5] CronTriggeringPolicy renaming behavior when midnight.

[ https://issues.apache.org/jira/browse/LOG4J2-1250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15361342#comment-15361342 ] Ralph Goers commented on LOG4J2-1250: - I have modified the ConfigurationScheduler to provide access

Re: Jenkins build became unstable: Log4j 2.x #2082

This is a bug in CleanFolders. If it encounters an error deleting files it retries deleting the directory up to 9 more times. However, it still fails because it failed the first time even if the delete subsequently worked. I have a fix for this. I have a suspicion that the bzip test is

[jira] [Commented] (LOG4J2-1250) [2.5] CronTriggeringPolicy renaming behavior when midnight.

[ https://issues.apache.org/jira/browse/LOG4J2-1250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15360631#comment-15360631 ] Ralph Goers commented on LOG4J2-1250: - OK - If only the SizeBasedTriggeringPolicy is configured

[jira] [Updated] (LOG4J2-1395) Add "direct" option to ConsoleAppender for increased performance

[ https://issues.apache.org/jira/browse/LOG4J2-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-1395: Attachment: app.zip See the attached project for the test. > Add "direct

[jira] [Reopened] (LOG4J2-1395) Add "direct" option to ConsoleAppender for increased performance

[ https://issues.apache.org/jira/browse/LOG4J2-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers reopened LOG4J2-1395: - Based on a StackOverflow post I created a test and expected to see some difference between

[jira] [Comment Edited] (LOG4J2-1250) [2.5] CronTriggeringPolicy renaming behavior when midnight.

[ https://issues.apache.org/jira/browse/LOG4J2-1250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15338653#comment-15338653 ] Ralph Goers edited comment on LOG4J2-1250 at 7/2/16 8:55 PM: - Actually

[jira] [Resolved] (LOG4J2-1332) Null/empty messages are not handled properly in RFC5424Layout

[ https://issues.apache.org/jira/browse/LOG4J2-1332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-1332. - Resolution: Not A Problem Actually, I misread the document the overall grammar of a syslog

[jira] [Resolved] (LOG4J2-1440) OnStartupTriggeringPolicy rolls over on every reconfiguration

[ https://issues.apache.org/jira/browse/LOG4J2-1440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-1440. - Resolution: Fixed The change has been made to pass true to the rename action. Please verify

Re: log4j2 evangelism

Personally, I don’t think talks do all that much. Articles are great, but IMO the best route is in trying to get other open source projects to use Log4j. Then people who start to use those other projects are forced to learn about Log4j. Ralph > On Jul 2, 2016, at 12:15 PM, Matt Sicker

Re: Thoughts on Log4J 3.0 branding

I have no idea when we would need or want to do 3.0 Sent from my iPad > On Jun 30, 2016, at 1:32 AM, Mikael Ståldal <mikael.stal...@magine.com> wrote: > > Are we planning to release Log4j 3.0 soon? > >> On Thu, Jun 30, 2016 at 12:59 AM, Ralph Goers <ralph.go..

[jira] [Comment Edited] (LOG4J2-1451) Java Log4j2 Syslog Appender

[ https://issues.apache.org/jira/browse/LOG4J2-1451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15356609#comment-15356609 ] Ralph Goers edited comment on LOG4J2-1451 at 6/30/16 6:38 AM: -- I created

[jira] [Resolved] (LOG4J2-1451) Java Log4j2 Syslog Appender

[ https://issues.apache.org/jira/browse/LOG4J2-1451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-1451. - Resolution: Cannot Reproduce > Java Log4j2 Syslog Appen

[jira] [Updated] (LOG4J2-1451) Java Log4j2 Syslog Appender

[ https://issues.apache.org/jira/browse/LOG4J2-1451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-1451: Attachment: logtest.zip I created the following project based on yours and it works fine for me

[jira] [Reopened] (LOG4J2-1451) Java Log4j2 Syslog Appender

[ https://issues.apache.org/jira/browse/LOG4J2-1451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers reopened LOG4J2-1451: - I just checked and SyslogAppenderTest does cover this so it should be working. Still, I'd like

[jira] [Assigned] (LOG4J2-1451) Java Log4j2 Syslog Appender

[ https://issues.apache.org/jira/browse/LOG4J2-1451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers reassigned LOG4J2-1451: --- Assignee: Ralph Goers > Java Log4j2 Syslog Appen

[jira] [Commented] (LOG4J2-1451) Java Log4j2 Syslog Appender

[ https://issues.apache.org/jira/browse/LOG4J2-1451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15356527#comment-15356527 ] Ralph Goers commented on LOG4J2-1451: - Gary, shouldn't we at least verify that this isn't a bug

[jira] [Commented] (LOG4J2-1450) SMTPAppender support for runtime lookup

[ https://issues.apache.org/jira/browse/LOG4J2-1450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15356526#comment-15356526 ] Ralph Goers commented on LOG4J2-1450: - I can't really imagine why you would want to change

Re: I can see! (colors)

A 3.0 version would imply that we plan to make changes the break compatibility in some way. I am not aware yet of anything that might require that, although it is possible that could happen if the Java 9 support requires it. Ralph > On Jun 29, 2016, at 2:00 PM, Paul Benedict

Re: AbstractManager.release() -> AutoCloseable

I have nothing against it. But since it isn’t a public API it wouldn’t be a priority for me. There are other far more interesting problems to solve (many of which are in the 300 some open Jira issues we have). Ralph > On Jun 28, 2016, at 3:52 PM, Gary Gregory wrote: >

Re: [Feature Request] Setting Log Level at Runtime?

Actually, it appears the question got down voted. I have no idea why as it seems a reasonable question to me. Ralph > On Jun 27, 2016, at 5:45 PM, Ralph Goers <ralph.go...@dslextreme.com> wrote: > > So upvote it… > > Ralph > >> On Jun 27, 2016, at 5:36 PM,

Re: [Feature Request] Setting Log Level at Runtime?

So upvote it… Ralph > On Jun 27, 2016, at 5:36 PM, Matt Sicker <boa...@gmail.com> wrote: > > And immediately got downvoted for some reason. > > On 27 June 2016 at 19:06, Ralph Goers <ralph.go...@dslextreme.com > <mailto:ralph.go...@dslextreme.com>>

Re: [Feature Request] Setting Log Level at Runtime?

I also provided an answer that provides more information on why Gary’s answer is correct and why it is so different. Ralph > On Jun 27, 2016, at 4:26 PM, Gary Gregory wrote: > > On Mon, Jun 27, 2016 at 3:56 PM, Ole Ersoy

[jira] [Commented] (LOG4J2-1181) Scala wrapper for Log4j 2 API

[ https://issues.apache.org/jira/browse/LOG4J2-1181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15351215#comment-15351215 ] Ralph Goers commented on LOG4J2-1181: - I wouldn't do it as part of 2.6.2, but it would make sense

Re: 2.6.2?

el.stal...@magine.com <mailto:mikael.stal...@magine.com> >>>>>> wrote: >>>>> >>>>>> I think that the MessageFactory2 fix was designed to not affect existing >>>>>> users. >>>>>> >>>>>> On Sun, Jun 19,

[jira] [Commented] (LOG4J2-1449) Injectable location info

[ https://issues.apache.org/jira/browse/LOG4J2-1449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15350250#comment-15350250 ] Ralph Goers commented on LOG4J2-1449: - Actually, I may not hate you. I currently have a test branch

Re: I can see! (colors)

<mailto:garydgreg...@gmail.com>> wrote: >> >> Since an HTML layout and a Console JAnsi layout need different >> interpretation of the message string, why not allow each appender to do its >> own rendering? Also, you want no rendering for other appenders like file, >>

[jira] [Comment Edited] (LOG4J2-1349) Garbage-free ThreadContext map

[ https://issues.apache.org/jira/browse/LOG4J2-1349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15349702#comment-15349702 ] Ralph Goers edited comment on LOG4J2-1349 at 6/25/16 4:25 PM: -- I am

[jira] [Commented] (LOG4J2-1447) Garbage-free data structure for LogEvent's context map data

[ https://issues.apache.org/jira/browse/LOG4J2-1447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15349703#comment-15349703 ] Ralph Goers commented on LOG4J2-1447: - See my comments in LOG4J2-1349 > Garbage-free data struct

[jira] [Commented] (LOG4J2-1349) Garbage-free ThreadContext map

[ https://issues.apache.org/jira/browse/LOG4J2-1349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15349702#comment-15349702 ] Ralph Goers commented on LOG4J2-1349: - I am wondering if we are taking this too far. While reducing

Re: I can see! (colors)

; Gary > > On Jun 24, 2016 11:07 AM, "Ralph Goers" <ralph.go...@dslextreme.com > <mailto:ralph.go...@dslextreme.com>> wrote: > Yes. Of course the converter would need to be aware what the target is, which > I am not sure is currently available. In this case

Re: I can see! (colors)

vent a new kind of %m converter that parses the > message and does the coloring. I could have an ANSI kind of %m, an HTML %m, > and so on. > > Gary > > On Jun 24, 2016 10:00 AM, "Ralph Goers" <ralph.go...@dslextreme.com > <mailto:ralph.go...@dslextreme.com>> w

Re: I can see! (colors)

I am not sure I get this idea at all. First, I would expect that “styles” would be plugins much as converters are for the PatternLayout. But it isn’t clear to me at all why I would want or require a StyledMessage to do that. If you want to support “styles” then implement the support in the

[jira] [Commented] (LOG4J2-1010) Injectable context properties

[ https://issues.apache.org/jira/browse/LOG4J2-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15347633#comment-15347633 ] Ralph Goers commented on LOG4J2-1010: - OK - I've read this whole thing: 1. I never really like

[jira] [Commented] (LOG4J2-1010) Injectable context properties

[ https://issues.apache.org/jira/browse/LOG4J2-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15346789#comment-15346789 ] Ralph Goers commented on LOG4J2-1010: - I just saw my name mentioned here. I definitely will want

Re: log4j2 evangelism

Please let me know if http://wiki.apache.org/logging/ManagingTheWebSite doesn’t have the answers you are looking for. Ralph > On Jun 22, 2016, at 8:15 AM, Gary Gregory wrote: > > On Wed, Jun 22, 2016 at 7:34 AM,

Re: More failing tests

ner.java:382) > at > org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192) > > Gary > > On Tue, Jun 21, 2016 at 1:22 PM, Ralph Goers <ralph.go...@dslextreme.com > <mailto:ralph.go...@dslextreme.com>> wrote: > I’d need the

Re: More failing tests

I’d need the rest of the error message on OnStartupTriggeringPolicyTest, but the line it is failing on is to delete the log file if it exists after the test has completed. We need to determine why Windows thinks the file is in use on the RollingAppenderSizeTest. I suspect this is the same

[jira] [Commented] (LOG4J2-1427) zipping files not working when file is created from appender used in root logger.

[ https://issues.apache.org/jira/browse/LOG4J2-1427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15341720#comment-15341720 ] Ralph Goers commented on LOG4J2-1427: - Is this on Windows? Can you try with 2.6.1? Some code

[jira] [Reopened] (LOG4J2-1440) OnStartupTriggeringPolicy rolls over on every reconfiguration

[ https://issues.apache.org/jira/browse/LOG4J2-1440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers reopened LOG4J2-1440: - > OnStartupTriggeringPolicy rolls over on every reconfigurat

[jira] [Commented] (LOG4J2-1440) OnStartupTriggeringPolicy rolls over on every reconfiguration

[ https://issues.apache.org/jira/browse/LOG4J2-1440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15339936#comment-15339936 ] Ralph Goers commented on LOG4J2-1440: - OK, so setting the minSize to 0 should cause

[jira] [Commented] (LOG4J2-1332) Null/empty messages are not handled properly in RFC5424Layout

[ https://issues.apache.org/jira/browse/LOG4J2-1332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15339038#comment-15339038 ] Ralph Goers commented on LOG4J2-1332: - >From what I can tell the the BNF grammar does not al

[jira] [Closed] (LOG4J2-1440) OnStartupTriggeringPolicy rolls over on every reconfiguration

[ https://issues.apache.org/jira/browse/LOG4J2-1440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers closed LOG4J2-1440. --- > OnStartupTriggeringPolicy rolls over on every reconfigurat

[jira] [Resolved] (LOG4J2-1440) OnStartupTriggeringPolicy rolls over on every reconfiguration

[ https://issues.apache.org/jira/browse/LOG4J2-1440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-1440. - Resolution: Fixed Fix has been committed. > OnStartupTriggeringPolicy rolls over on ev

[jira] [Created] (LOG4J2-1440) OnStartupTriggeringPolicy rolls over on every reconfiguration

Ralph Goers created LOG4J2-1440: --- Summary: OnStartupTriggeringPolicy rolls over on every reconfiguration Key: LOG4J2-1440 URL: https://issues.apache.org/jira/browse/LOG4J2-1440 Project: Log4j 2

[jira] [Assigned] (LOG4J2-1426) Log Rotation or rollover on every server shutdown in log4j2

[ https://issues.apache.org/jira/browse/LOG4J2-1426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers reassigned LOG4J2-1426: --- Assignee: Ralph Goers > Log Rotation or rollover on every server shutdown in log

[jira] [Commented] (LOG4J2-1250) [2.5] CronTriggeringPolicy renaming behavior when midnight.

[ https://issues.apache.org/jira/browse/LOG4J2-1250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15338653#comment-15338653 ] Ralph Goers commented on LOG4J2-1250: - Yes, this sounds reasonable. > [2.5] CronTriggeringPol

[jira] [Resolved] (LOG4J2-1425) monitorInterval doesn't work when using PropertiesConfiguration

[ https://issues.apache.org/jira/browse/LOG4J2-1425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-1425. - Resolution: Duplicate Fix Version/s: 2.6 This is a duplicate of LOG4J2-1425

Re: Jenkins build is still unstable: Log4j 2.x #2046

I haven’t figured out what the problem is yet. I need to see the contents of the files Ralph > On Jun 18, 2016, at 10:06 PM, Remko Popma wrote: > > Ouch, what was this again... > > Failed > >

Re: 2.6.2?

l.com > <mailto:remko.po...@gmail.com>> wrote: > Any other issues that we want to fix for 2.6.2? > > > On Sunday, 19 June 2016, Ralph Goers <ralph.go...@dslextreme.com > <mailto:ralph.go...@dslextreme.com>> wrote: > I’d rather do another point release. I

Re: Semver 2.6.2 vs 2.7

+1 Ralph > On Jun 18, 2016, at 3:57 PM, Remko Popma wrote: > > I would also like to do a release soon, but what we have so far "feels" more > like a bugfix release. I don't think we have enough new functionality yet to > call it 2.7... > > If the MessageFactory2

Re: 2.6.2?

g/jira/browse/LOG4J2-1434 >> <https://issues.apache.org/jira/browse/LOG4J2-1434> >> >> On Sat, Jun 18, 2016 at 9:51 PM, Matt Sicker <boa...@gmail.com >> <mailto:boa...@gmail.com>> wrote: >> Are there any more issues you guys want to finish for 2.

Re: Semver 2.6.2 vs 2.7

Personally, I wouldn’t want to release 2.7 with only that amount of stuff in it. It seems too minor to me. I would keep it at 2.6.2. Ralph > On Jun 18, 2016, at 2:11 PM, Matt Sicker wrote: > > Oh, in that case, yeah, I'd agree that this is semantically 2.7 at this point. >

[jira] [Commented] (LOG4J2-1430) Add optional support for Conversant DisruptorBlockingQueue in AsyncAppender

[ https://issues.apache.org/jira/browse/LOG4J2-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15337572#comment-15337572 ] Ralph Goers commented on LOG4J2-1430: - Honestly, there are so many numbers here that I can't really

[jira] [Commented] (LOG4J2-1434) StringBuffer in ThreadLocal can cause excessive memory usage after large log messages

[ https://issues.apache.org/jira/browse/LOG4J2-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15337571#comment-15337571 ] Ralph Goers commented on LOG4J2-1434: - This seems like it is getting more and more complicated

[jira] [Comment Edited] (LOG4J2-1434) StringBuffer in ThreadLocal can cause excisive memory usage after large log messages

[ https://issues.apache.org/jira/browse/LOG4J2-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15334864#comment-15334864 ] Ralph Goers edited comment on LOG4J2-1434 at 6/16/16 10:48 PM: --- I think

[jira] [Comment Edited] (LOG4J2-1434) StringBuffer in ThreadLocal can cause excisive memory usage after large log messages

[ https://issues.apache.org/jira/browse/LOG4J2-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15334864#comment-15334864 ] Ralph Goers edited comment on LOG4J2-1434 at 6/16/16 10:46 PM: --- I think

[jira] [Commented] (LOG4J2-1434) StringBuffer in ThreadLocal can cause excisive memory usage after large log messages

[ https://issues.apache.org/jira/browse/LOG4J2-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15334864#comment-15334864 ] Ralph Goers commented on LOG4J2-1434: - I think Remko may have misread this. Typically, the "m

[jira] [Commented] (LOG4J2-1429) Configuration File Include

[ https://issues.apache.org/jira/browse/LOG4J2-1429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15334329#comment-15334329 ] Ralph Goers commented on LOG4J2-1429: - I'm not sure what Maven would have to do with this. I am

Re: Different failures in RollingAppenderSizeTest on Windows and Jenkins

Good. There is actually a message in the log that can be investigated. Ralph > On Jun 15, 2016, at 8:14 PM, Gary Gregory wrote: > > [Sorry for the lack of subject before] > > It's failing differently in Jenkins: > >

[jira] [Commented] (LOG4J2-1430) Add optional support for Conversant DisruptorBlockingQueue in AsyncAppender

[ https://issues.apache.org/jira/browse/LOG4J2-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15333085#comment-15333085 ] Ralph Goers commented on LOG4J2-1430: - Matt, despite while I can agree with Gary that making

[jira] [Commented] (LOG4J2-1431) Simplify log4j system property naming scheme

[ https://issues.apache.org/jira/browse/LOG4J2-1431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15333074#comment-15333074 ] Ralph Goers commented on LOG4J2-1431: - I agree. But what system property are you planning on adding

Re:

Not yet, but it shows that the code I put in to add diagnostics is working. Ralph > On Jun 15, 2016, at 6:33 PM, Gary Gregory wrote: > > I'm just saw the following building (mvn clean test) master on Windows 7 and > Java 8: > > Failed tests: >

[jira] [Commented] (LOG4J2-1430) Add support for custom BlockingQueue implementations in AsyncAppender

[ https://issues.apache.org/jira/browse/LOG4J2-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15332171#comment-15332171 ] Ralph Goers commented on LOG4J2-1430: - I would prefer an implementation where no configuration

Re: Would it be worth it to make the BlockingQueue implementation configurable in AsyncAppender?

This is still a pretty good option. I would modify the code to use that option if the library is present, otherwise fall back to ArrayBlockingQueue. Ralph > On Jun 15, 2016, at 9:24 AM, Matt Sicker wrote: > > Using the 4 threads versions of the benchmarks, here's what I've

[jira] [Comment Edited] (LOG4J2-1429) Configuration File Include

[ https://issues.apache.org/jira/browse/LOG4J2-1429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15330970#comment-15330970 ] Ralph Goers edited comment on LOG4J2-1429 at 6/15/16 1:14 AM: -- You can use

[jira] [Commented] (LOG4J2-1429) Configuration File Include

[ https://issues.apache.org/jira/browse/LOG4J2-1429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15330970#comment-15330970 ] Ralph Goers commented on LOG4J2-1429: - You can use {code} LoggerContext initialize(final String name

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