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 probl

[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&focusedCommentId=15341720#comment-15341720 ] Ralph Goers commented on LOG4J2-1427: - Is this on Windows? Can you try with 2

[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&focusedCommentId=15339936#comment-15339936 ] Ralph Goers commented on LOG4J2-1440: - OK, so setting the minSize to 0 should c

[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&focusedCommentId=15339038#comment-15339038 ] Ralph Goers commented on LOG4J2-1332: - >From what I can tell the the BNF

[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&focusedCommentId=15338653#comment-15338653 ] Ralph Goers commented on LOG4J2-1250: - Yes, this sounds reasonable. &g

[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 > > org.apache.logging.log4j.core.appender.rolling.RandomRollingAppenderOnStartupTest.org.apache.logging

Re: 2.6.2?

te: > Any other issues that we want to fix for 2.6.2? > > > On Sunday, 19 June 2016, Ralph Goers <mailto:ralph.go...@dslextreme.com>> wrote: > I’d rather do another point release. I am targeting a few bugs that need to > be fixed. I’d rather 2.7 contain more new stuff

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 return type change is key, th

Re: 2.6.2?

gt; >> >> On Sat, Jun 18, 2016 at 9:51 PM, Matt Sicker > <mailto:boa...@gmail.com>> wrote: >> Are there any more issues you guys want to finish for 2.6.2 at this time, or >> can we release this soon? >> >> On 12 June 2016 at 23:07, Ralph Goers >

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. > > On 18 June 2016 a

[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&focusedCommentId=15337572#comment-15337572 ] Ralph Goers commented on LOG4J2-1430: - Honestly, there are so many numbers here

[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&focusedCommentId=15337571#comment-15337571 ] Ralph Goers commented on LOG4J2-1434: - This seems like it is getting more and

[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&focusedCommentId=15334864#comment-15334864 ] Ralph Goers edited comment on LOG4J2-1434 at 6/16/16 10:4

[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&focusedCommentId=15334864#comment-15334864 ] Ralph Goers edited comment on LOG4J2-1434 at 6/16/16 10:4

[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&focusedCommentId=15334864#comment-15334864 ] Ralph Goers commented on LOG4J2-1434: - I think Remko may have misread

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

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

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: > > https://builds.apache.org/job/Log4j%202.x/2034/org.apache.logging.log4j$log4j

[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&focusedCommentId=15333085#comment-15333085 ] Ralph Goers commented on LOG4J2-1430: - Matt, despite while I can agree with

[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&focusedCommentId=15333074#comment-15333074 ] Ralph Goers commented on LOG4J2-1431: - I agree. But what system property are

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: > RollingAppenderSizeTest.testAppender:141->delet

[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&focusedCommentId=15332171#comment-15332171 ] Ralph Goers commented on LOG4J2-1430: - I would prefer an implementation wher

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 found: > > ArrayBl

[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&focusedCommentId=15330970#comment-15330970 ] Ralph Goers edited comment on LOG4J2-1429 at 6/15/16 1:1

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

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

[jira] [Commented] (LOG4J2-1395) Faster Console appender

[ https://issues.apache.org/jira/browse/LOG4J2-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15328033#comment-15328033 ] Ralph Goers commented on LOG4J2-1395: - That seems like you have covered the b

Re: log4j2 evangelism

m>> wrote: > On Mon, Jun 13, 2016 at 10:03 AM, Ralph Goers <mailto:ralph.go...@dslextreme.com>> wrote: > The biggest complaints we seem to be getting are about the effort in > transitioning from Log4j 1.x to 2. To be fair, they would have the same > amount of effort

Re: log4j2 evangelism

The biggest complaints we seem to be getting are about the effort in transitioning from Log4j 1.x to 2. To be fair, they would have the same amount of effort to transition to anything. I believe someone created a tool to help convert Log4j 1.x configuration to Log4j 2 format. At the very leas

[jira] [Commented] (LOG4J2-1395) Faster Console appender

[ https://issues.apache.org/jira/browse/LOG4J2-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15327739#comment-15327739 ] Ralph Goers commented on LOG4J2-1395: - http://www.ibm.com/developerworks/java

[jira] [Commented] (LOG4J2-1395) Faster Console appender

[ https://issues.apache.org/jira/browse/LOG4J2-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15327432#comment-15327432 ] Ralph Goers commented on LOG4J2-1395: - And that is what I meant - if that i

[jira] [Commented] (LOG4J2-1395) Faster Console appender

[ https://issues.apache.org/jira/browse/LOG4J2-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15327426#comment-15327426 ] Ralph Goers commented on LOG4J2-1395: - I am concerned because, as I noted previo

[jira] [Comment Edited] (LOG4J2-1395) Faster Console appender

[ https://issues.apache.org/jira/browse/LOG4J2-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15327171#comment-15327171 ] Ralph Goers edited comment on LOG4J2-1395 at 6/13/16 11:1

[jira] [Commented] (LOG4J2-1395) Faster Console appender

[ https://issues.apache.org/jira/browse/LOG4J2-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15327171#comment-15327171 ] Ralph Goers commented on LOG4J2-1395: - You should note that this only applies to

Re: 2.6.2?

I think another point release rather “soonish” is warranted. I’d really like to get a handle on these periodic Jenkins test failures. They may either be something wrong with the test or an actual problem with file rollover. Ralph > On Jun 12, 2016, at 7:09 PM, Gary Gregory wrote: > > We have

Re: Build failed in Jenkins: Log4j 2.x #2026

It had just started. Notice that this isn’t an out of heap space. In my experience "Unable to create native thread” usually means the server has exceeded the max number of processes. Ralph > On Jun 12, 2016, at 1:13 PM, Matt Sicker wrote: > > Huh, that's a new one. Out of memory! > > I bui

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

t;> On Sun, Jun 12, 2016 at 10:07 PM, Ralph Goers >>> wrote: >>> Crap. I had hoped the change I made might have fixed it. There might be >>> some more information in the test output though. >>> >>> Sent from my iPad >>> >>>>

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

Crap. I had hoped the change I made might have fixed it. There might be some more information in the test output though. Sent from my iPad > On Jun 12, 2016, at 3:42 AM, Remko Popma wrote: > > back to the old XZ failure... > >> On Sun, Jun 12, 2016 at 6:11 PM, Apache Jenkins Server >> wrot

Re: Jenkins build is unstable: Log4j 2.x #2019

Oh, but yes, if the first file is non-zero and the second file is zero then it should fail - and that would be a correct failure. Ralph > On Jun 12, 2016, at 12:38 AM, Ralph Goers wrote: > > Both files write a header, 100 events and a footer. Neither should be zero > and both s

Re: Jenkins build is unstable: Log4j 2.x #2019

7;t the test fail? > > On Sun, Jun 12, 2016 at 2:45 PM, Ralph Goers <mailto:ralph.go...@dslextreme.com>> wrote: > Looked at the test again. It had some bugs in it. > > Ralph > >> On Jun 11, 2016, at 10:22 PM, Ralph Goers > <mailto:ralph.go...@dslextreme.com&g

Re: Jenkins build is unstable: Log4j 2.x #2019

Looked at the test again. It had some bugs in it. Ralph > On Jun 11, 2016, at 10:22 PM, Ralph Goers wrote: > > Yes. It creates the file and writes to it. The test should then end and run > again. On the second run the file should roll over. The files should both > have the

Re: Jenkins build is unstable: Log4j 2.x #2019

Yes. It creates the file and writes to it. The test should then end and run again. On the second run the file should roll over. The files should both have the header, footer, and same number of lines so they should be the same size. Ralph > On Jun 11, 2016, at 10:08 PM, Remko Popma wrote: > >

[jira] [Assigned] (LOG4J2-548) Log4j 2.0 with JBoss EAP 6.2

[ https://issues.apache.org/jira/browse/LOG4J2-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers reassigned LOG4J2-548: -- Assignee: Ralph Goers > Log4j 2.0 with JBoss EAP

[jira] [Commented] (LOG4J2-823) Changing AsyncLogger level programmatically not working properly

[ https://issues.apache.org/jira/browse/LOG4J2-823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15326166#comment-15326166 ] Ralph Goers commented on LOG4J2-823: Is this still a problem or has it been reso

[jira] [Closed] (LOG4J2-800) All life cycle implementations should be serializable

[ https://issues.apache.org/jira/browse/LOG4J2-800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers closed LOG4J2-800. -- Resolution: Not A Problem Doesn't seem to be an issue any more. > All life cycle impleme

[jira] [Commented] (LOG4J2-696) RegexFilter does not match multiline log messages

[ https://issues.apache.org/jira/browse/LOG4J2-696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15326164#comment-15326164 ] Ralph Goers commented on LOG4J2-696: Assigning to me since it doesn't ap

[jira] [Assigned] (LOG4J2-696) RegexFilter does not match multiline log messages

[ https://issues.apache.org/jira/browse/LOG4J2-696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers reassigned LOG4J2-696: -- Assignee: Ralph Goers > RegexFilter does not match multiline log messa

[jira] [Closed] (LOG4J2-159) log4j.xml loading from classpath not working correct in osgi environment

[ https://issues.apache.org/jira/browse/LOG4J2-159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers closed LOG4J2-159. -- Resolution: Incomplete Closing this issue due to lack of feedback. > log4j.xml loading from classp

[jira] [Commented] (LOG4J2-653) Add plugin builder classes as alternative to factory methods.

[ https://issues.apache.org/jira/browse/LOG4J2-653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15326160#comment-15326160 ] Ralph Goers commented on LOG4J2-653: This is marked as "In progress" b

[jira] [Resolved] (LOG4J2-1420) 2.6.1 - NPE due to OnStartupTriggeringPolicy changes

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

[jira] [Commented] (LOG4J2-1420) 2.6.1 - NPE due to OnStartupTriggeringPolicy changes

[ https://issues.apache.org/jira/browse/LOG4J2-1420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15325822#comment-15325822 ] Ralph Goers commented on LOG4J2-1420: - That is my plan > 2.6.1 - NPE

[jira] [Assigned] (LOG4J2-1420) 2.6.1 - NPE due to OnStartupTriggeringPolicy changes

[ https://issues.apache.org/jira/browse/LOG4J2-1420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers reassigned LOG4J2-1420: --- Assignee: Ralph Goers > 2.6.1 - NPE due to OnStartupTriggeringPolicy chan

[jira] [Commented] (LOG4J2-1420) 2.6.1 - NPE due to OnStartupTriggeringPolicy changes

[ https://issues.apache.org/jira/browse/LOG4J2-1420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15325171#comment-15325171 ] Ralph Goers commented on LOG4J2-1420: - Actually, the logic worked the way it

[jira] [Commented] (LOG4J2-1414) Minor issues with the 2.6.1 web site

[ https://issues.apache.org/jira/browse/LOG4J2-1414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15324810#comment-15324810 ] Ralph Goers commented on LOG4J2-1414: - I have a fix for the git checkout inf

[jira] [Comment Edited] (LOG4J2-1414) Minor issues with the 2.6.1 web site

[ https://issues.apache.org/jira/browse/LOG4J2-1414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15324810#comment-15324810 ] Ralph Goers edited comment on LOG4J2-1414 at 6/10/16 5:0

[ANNOUNCEMENT] Log4j 2.6.1 released

The Apache Log4j 2 team is pleased to announce the Log4j 2.6.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

[VOTE][RESULT] Log4j 2.6.1 rc1

The vote has passed with binding +1 votes from Remko Popma, Matt Sicker, Gary Gregory and Ralph Goers. Leon Finker also cast a +1 vote. Thanks to all who voted. I will continue on with the release process. Ralph

Re: [VOTE] Log4j 2.6.1 rc1

My +1 Ralph > On Jun 5, 2016, at 6:55 PM, Ralph Goers wrote: > > This is a vote to release Log4j 2.6.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 > [] -

AsyncAppenderQueueFullPolicyTest hung

I just tried to do a full build and got this test to hang. Gary reported the same thing last week on Windows. The stack trace indicates that it isn’t properly shutting down. Somehow it seems the BlockingAppender must not be having its shutdown flag set. This test was only added a month ago. I’m

Re: No Git tag for 2.6!

11:15 AM, Ralph Goers wrote: > > Note that even if you add the tag the web site is still going to point to the > rc tag unless the page is manually modified. Maven creates the source > repository page automatically and uses the tag that was checked out. We would > have to inv

Re: No Git tag for 2.6!

ther with the guess work? > > I'll create a tag for 2.6... ;-) > > Gary > > > On 8 June 2016 at 00:28, Gary Gregory <mailto:garydgreg...@gmail.com>> wrote: > We should. If a RC does NOT lead to a release, then how can you tell that > fr

Re: No Git tag for 2.6!

Yes. To be honest I haven’t tagged any of the releases since I started tagging them as release candidates. The rc1 tag is what was voted on and released. Ralph > On Jun 7, 2016, at 7:43 PM, Gary Gregory wrote: > > I was trying to compare sources while investigating a Clirr issue and I see >

[jira] [Resolved] (LOG4J2-1228) Multiple footers written to file on system restart

[ https://issues.apache.org/jira/browse/LOG4J2-1228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-1228. - Resolution: Duplicate Yes, from the description this exactly matches what was fixed. > Multi

Re: [VOTE] Log4j 2.6.1 rc1

Not sure how that happened. > > On 6 June 2016 at 08:09, Remko Popma <mailto:remko.po...@gmail.com>> wrote: > +1 > Remko > > On Mon, Jun 6, 2016 at 10:55 AM, Ralph Goers <mailto:ralph.go...@dslextreme.com>> wrote: > This is a vote to release Log4

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

Failed due to an Unbox test. Ralph > On Jun 6, 2016, at 5:07 AM, Apache Jenkins Server > wrote: > > See > > > - > To unsubscribe, e-mail: log4j-dev-unsubscr...@logging

Re: 2.6.1 web site

Never mind. I found your account Gary. Ralph > On Jun 5, 2016, at 8:30 PM, Ralph Goers wrote: > > > I added Gary and Matt as collaborators. Gary, I don’t know your github id. > > Ralph > >> On Jun 5, 2016, at 8:26 PM, Ralph Goers wrote: >> >> Oh - t

Re: 2.6.1 web site

Also note that this repo is just temporary. The real fixes need to be committed to the real git repo. I will completely delete the site in git when I do the next release. Ralph > On Jun 5, 2016, at 8:30 PM, Ralph Goers wrote: > > > I added Gary and Matt as collaborators. Gary,

Re: 2.6.1 web site

I added Gary and Matt as collaborators. Gary, I don’t know your github id. Ralph > On Jun 5, 2016, at 8:26 PM, Ralph Goers wrote: > > Oh - the repo is at https://github.com/rgoers/rgoers.github.io. > > Ralph > >> On Jun 5, 2016, at 8:15 PM, Ralph Goers wrote: >

Re: 2.6.1 web site

Oh - the repo is at https://github.com/rgoers/rgoers.github.io. Ralph > On Jun 5, 2016, at 8:15 PM, Ralph Goers wrote: > > It seems I forgot to update changes.xml and put in the date before running > the release. This should manually be corrected on the web site. If you guy

2.6.1 web site

It seems I forgot to update changes.xml and put in the date before running the release. This should manually be corrected on the web site. If you guys want to update the site before it is released I think you should be able to clone my repo and do pull requests. Ralph

[VOTE] Log4j 2.6.1 rc1

This is a vote to release Log4j 2.6.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 welcom

Re: MessageFactory2 missing @since tag

Didn’t make 2.6.1 Ralph > On Jun 5, 2016, at 5:43 PM, Gary Gregory wrote: > > Thanks, fixed. > > Gary > > On Sun, Jun 5, 2016 at 5:31 PM, Remko Popma > wrote: > 2.6 > > Sent from my iPhone > > On 2016/06/06, at 8:57, Gary Gregory

Re: Log4j 2.6.1

The release is in progress. Ralph > On Jun 5, 2016, at 10:09 AM, Ralph Goers wrote: > > Actually, my fix broke a different unit test. Fixing that one. > > Sent from my iPhone > > On Jun 5, 2016, at 8:53 AM, Gary Gregory <mailto:garydgreg...@gmail.com>> wrote:

Re: Log4j 2.6.1

Actually, my fix broke a different unit test. Fixing that one. Sent from my iPhone > On Jun 5, 2016, at 8:53 AM, Gary Gregory wrote: > > +1 to release 2.6.1 ASAP to pick up the message factory fixes. > > Gary > >> On Jun 5, 2016 7:47 AM, "Ralph Goers" wrot

Re: Log4j 2.6.1

ption) > are critical bugs and I'd like to release the fix for these as soon as > possible... > > > >> On Sat, Jun 4, 2016 at 5:54 AM, Ralph Goers >> wrote: >> Actually, nevermind. I know how to do it. >> >> Ralph >> >>> On Jun

[jira] [Commented] (LOG4J2-1405) 2.6 html format - "" inserted in the middle of when restart tomcat

[ https://issues.apache.org/jira/browse/LOG4J2-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15315687#comment-15315687 ] Ralph Goers commented on LOG4J2-1405: - It is as I feared. The footer does

[jira] [Commented] (LOG4J2-1405) 2.6 html format - "" inserted in the middle of when restart tomcat

[ https://issues.apache.org/jira/browse/LOG4J2-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15315630#comment-15315630 ] Ralph Goers commented on LOG4J2-1405: - Whenever the output stream is closed

[jira] [Commented] (LOG4J2-1405) 2.6 html format - "" inserted in the middle of when restart tomcat

[ https://issues.apache.org/jira/browse/LOG4J2-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15315565#comment-15315565 ] Ralph Goers commented on LOG4J2-1405: - Yes, that is definitely the problem. If

Re: Log4j 2.6.1

Actually, nevermind. I know how to do it. Ralph > On Jun 3, 2016, at 1:32 PM, Gary Gregory wrote: > > I can make on from the jpeg tonight or tomorrow. AFK. > > Gary > > On Jun 3, 2016 1:26 PM, "Ralph Goers" <mailto:ralph.go...@dslextreme.com>> w

Re: Log4j 2.6.1

A png. Ralph > On Jun 3, 2016, at 12:11 PM, Gary Gregory wrote: > > On Fri, Jun 3, 2016 at 11:50 AM, Ralph Goers <mailto:ralph.go...@dslextreme.com>> wrote: > Do we have one of the standard logo? I can do that before I generate the site. > > I'm sorry one o

Re: Log4j 2.6.1

Do we have one of the standard logo? I can do that before I generate the site. Ralph > On Jun 3, 2016, at 11:11 AM, Gary Gregory wrote: > > On Fri, Jun 3, 2016 at 10:51 AM, Gary Gregory <mailto:garydgreg...@gmail.com>> wrote: > On Fri, Jun 3, 2016 at 10:21 AM, Ralph Go

Re: Log4j 2.6.1

Gary, can you modify another logo for 2.6.1. Just pick the one in the chart preceding the one for 2.6. Ralph > On Jun 3, 2016, at 10:16 AM, Ralph Goers wrote: > > Thanks Remko. Just remember that “tonight” or “tomorrow morning” translates > into 12-24 hrs from now. So if you h

Re: Log4j 2.6.1

#x27;s 2 am > here and I'm done for day. > > I'm good with releasing 2.6.1 with the current batch of fixes. > > -Remko > > > On Sat, Jun 4, 2016 at 1:50 AM, Gary Gregory <mailto:garydgreg...@gmail.com>> wrote: > On Fri, Jun 3, 2016 at 8:57 AM, Ralph Goers

Re: Log4j 2.6.1

Are there any other fixes that have to go in? I am thinking I will start the release tonight or tomorrow morning. Ralph > On Jun 1, 2016, at 2:57 PM, Ralph Goers wrote: > > I just fixed LOGJ2-1402. I would also like to modify RenameAction to use > java.nio.file to rename and de

[jira] [Resolved] (LOG4J2-997) removeFilter() in AbstractFilterable does not remove filter

[ https://issues.apache.org/jira/browse/LOG4J2-997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-997. Resolution: Fixed Fix Version/s: 2.6.1 Fixed in master. Although I didn't use the pat

[jira] [Commented] (LOG4J2-997) removeFilter() in AbstractFilterable does not remove filter

[ https://issues.apache.org/jira/browse/LOG4J2-997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15313722#comment-15313722 ] Ralph Goers commented on LOG4J2-997: I am finally reviewing the patch. I'

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

We really need to debug this. I wish it happened somewhere besides just the Jenkins build. Ralph > On Jun 2, 2016, at 9:07 PM, Matt Sicker wrote: > > Our old friend bz2. > > On 2 June 2016 at 20:13, Apache Jenkins Server > wrote: > See

[jira] [Assigned] (LOG4J2-997) removeFilter() in AbstractFilterable does not remove filter

[ https://issues.apache.org/jira/browse/LOG4J2-997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers reassigned LOG4J2-997: -- Assignee: Ralph Goers > removeFilter() in AbstractFilterable does not remove fil

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

[ https://issues.apache.org/jira/browse/LOG4J2-1032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15313337#comment-15313337 ] Ralph Goers commented on LOG4J2-1032: - The RenameAction was modified to use java

[jira] [Assigned] (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 reassigned LOG4J2-1032: --- Assignee: Ralph Goers > Rollover startegy failing on high l

[jira] [Assigned] (LOG4J2-1228) Multiple footers written to file on system restart

[ https://issues.apache.org/jira/browse/LOG4J2-1228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers reassigned LOG4J2-1228: --- Assignee: Ralph Goers > Multiple footers written to file on system rest

[jira] [Commented] (LOG4J2-1407) Misleading WARN log events from Log4j about message factories and unexpected formatting

[ https://issues.apache.org/jira/browse/LOG4J2-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15313186#comment-15313186 ] Ralph Goers commented on LOG4J2-1407: - So what was the fix? Saying "In G

[jira] [Commented] (LOG4J2-1407) Misleading WARN log events from Log4j about message factories and unexpected formatting

[ https://issues.apache.org/jira/browse/LOG4J2-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15313123#comment-15313123 ] Ralph Goers commented on LOG4J2-1407: - What is misleading about the warning mes

[jira] [Commented] (LOG4J2-1406) 2.6 is re-logging prior throwable instead of logging the throwable that is currently passed in by application code

[ https://issues.apache.org/jira/browse/LOG4J2-1406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15312991#comment-15312991 ] Ralph Goers commented on LOG4J2-1406: - Thanks for the patch! This looks li

[jira] [Commented] (LOG4J2-1402) Exception when using log4j2.properties and logger with dash

[ https://issues.apache.org/jira/browse/LOG4J2-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15312633#comment-15312633 ] Ralph Goers commented on LOG4J2-1402: - My mistake. The build does mvn clean ins

[jira] [Commented] (LOG4J2-1402) Exception when using log4j2.properties and logger with dash

[ https://issues.apache.org/jira/browse/LOG4J2-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15312478#comment-15312478 ] Ralph Goers commented on LOG4J2-1402: - Did you deploy it? Our Jenkins build doe

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