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

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

Re: log4j2 evangelism

greg...@gmail.com > <mailto:garydgreg...@gmail.com>> wrote: > On Mon, Jun 13, 2016 at 10:03 AM, Ralph Goers <ralph.go...@dslextreme.com > <mailto:ralph.go...@dslextreme.com>> wrote: > The biggest complaints we seem to be getting are about the effort in > trans

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

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

[ https://issues.apache.org/jira/browse/LOG4J2-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15327739#comment-15327739 ] Ralph Goers commented on LOG4J2-1395: - http://www.ibm.com/developerworks/java/jdk/. To be fair, 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=15327432#comment-15327432 ] Ralph Goers commented on LOG4J2-1395: - And that is what I meant - if that isn't documented already

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

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

[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=15327171#comment-15327171 ] Ralph Goers edited comment on LOG4J2-1395 at 6/13/16 11:14 AM: --- You should

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

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

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

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

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

st that failed but our old friend xz. >> >>> On Sun, Jun 12, 2016 at 10:07 PM, Ralph Goers <ralph.go...@dslextreme.com> >>> wrote: >>> Crap. I had hoped the change I made might have fixed it. There might be >>> some more information in the test ou

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

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 <ralph.go...@dslextreme.com> wrote: > > Both files write a header, 100 events and a footer. Neither

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

> zero length, then won't the test fail? > > On Sun, Jun 12, 2016 at 2:45 PM, Ralph Goers <ralph.go...@dslextreme.com > <mailto:ralph.go...@dslextreme.com>> wrote: > Looked at the test again. It had some bugs in it. > > Ralph > >> On Jun 11, 2

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 <ralph.go...@dslextreme.com> 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

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

[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=15326166#comment-15326166 ] Ralph Goers commented on LOG4J2-823: Is this still a problem or has it been resolved in later releases

[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 implementati

[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=15326164#comment-15326164 ] Ralph Goers commented on LOG4J2-696: Assigning to me since it doesn't appear Gary plans on fixing

[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=15326160#comment-15326160 ] Ralph Goers commented on LOG4J2-653: This is marked as "In progress" but hasn't been up

[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

[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=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=15325171#comment-15325171 ] Ralph Goers commented on LOG4J2-1420: - Actually, the logic worked the way it did previously because

[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=15324810#comment-15324810 ] Ralph Goers commented on LOG4J2-1414: - I have a fix for the git checkout info to point to the actual

[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=15324810#comment-15324810 ] Ralph Goers edited comment on LOG4J2-1414 at 6/10/16 5:00 PM: -- Rats. I

[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 <ralph.go...@dslextreme.com> 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, re

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.

Re: No Git tag for 2.6!

11:15 AM, Ralph Goers <ralph.go...@dslextreme.com> 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

Re: No Git tag for 2.6!

a RC does NOT lead to a release, then how can you tell that > from one that did? > > Gary > > On Tue, Jun 7, 2016 at 10:05 PM, Ralph Goers <ralph.go...@dslextreme.com > <mailto:ralph.go...@dslextreme.com>> wrote: > Yes. To be honest I haven’t tagged any of th

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

[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

e to copy/paste the > link. Not sure how that happened. > > On 6 June 2016 at 08:09, Remko Popma <remko.po...@gmail.com > <mailto:remko.po...@gmail.com>> wrote: > +1 > Remko > > On Mon, Jun 6, 2016 at 10:55 AM, Ralph Goers <ralph.go...@dslextreme.com > <

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:

Re: 2.6.1 web site

Never mind. I found your account Gary. Ralph > On Jun 5, 2016, at 8:30 PM, Ralph Goers <ralph.go...@dslextreme.com> 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

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 <ralph.go...@dslextreme.com> wrote: > > > I a

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 <ralph.go...@dslextreme.com> wrote: > > Oh - the repo is at https://github.com/rgoers/rgoers.github.io. > > Ralph > >> On Jun 5, 2016, at

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 <ralph.go...@dslextreme.com> wrote: > > It seems I forgot to update changes.xml and put in the date before running > the release. This should manually be correct

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

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

Re: Log4j 2.6.1

The release is in progress. Ralph > On Jun 5, 2016, at 10:09 AM, Ralph Goers <ralph.go...@dslextreme.com> 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 Greg

Re: Log4j 2.6.1

a previously logged Exception) > 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 <ralph.go...@dslextreme.com> >> wrote: >> Actually, nevermind. I know how to do it. >

[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=15315687#comment-15315687 ] Ralph Goers commented on LOG4J2-1405: - It is as I feared. The footer does get written twice. >

[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=15315630#comment-15315630 ] Ralph Goers commented on LOG4J2-1405: - Whenever the output stream is closed the footer is written. I

[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=15315565#comment-15315565 ] Ralph Goers commented on LOG4J2-1405: - Yes, that is definitely the problem. If the file exists

Re: Log4j 2.6.1

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

Re: Log4j 2.6.1

A png. Ralph > On Jun 3, 2016, at 12:11 PM, Gary Gregory <garydgreg...@gmail.com> wrote: > > On Fri, Jun 3, 2016 at 11:50 AM, Ralph Goers <ralph.go...@dslextreme.com > <mailto:ralph.go...@dslextreme.com>> wrote: > Do we have one of the standard logo? I can d

Re: Log4j 2.6.1

gt;> wrote: > On Fri, Jun 3, 2016 at 10:21 AM, Ralph Goers <ralph.go...@dslextreme.com > <mailto:ralph.go...@dslextreme.com>> wrote: > Gary, can you modify another logo for 2.6.1. Just pick the one in the chart > preceding the one for 2.6. > > Sure. > >

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 <ralph.go...@dslextreme.com> wrote: > > Thanks Remko. Just remember that “tonight” or “tomorrow morning” translates > into

Re: Log4j 2.6.1

from 2.3. However it'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 <garydgreg...@gmail.com > <mailto:garydgreg...@gmail.com>> wrote

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 <ralph.go...@dslextreme.com> wrote: > > I just fixed LOGJ2-1402. I would also like to modify RenameAction to use

[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 patch

[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=15313722#comment-15313722 ] Ralph Goers commented on LOG4J2-997: I am finally reviewing the patch. I'm not OK with it. I do

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

[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=15313337#comment-15313337 ] Ralph Goers commented on LOG4J2-1032: - The RenameAction was modified to use java.nio so it can better

[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=15313186#comment-15313186 ] Ralph Goers commented on LOG4J2-1407: - So what was the fix? Saying "In Git master" doesn

[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=15313123#comment-15313123 ] Ralph Goers commented on LOG4J2-1407: - What is misleading about the warning message? > Mislead

[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=15312991#comment-15312991 ] Ralph Goers commented on LOG4J2-1406: - Thanks for the patch! This looks like a pretty simple fix

[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=15312633#comment-15312633 ] Ralph Goers commented on LOG4J2-1402: - My mistake. The build does mvn clean install

[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=15312478#comment-15312478 ] Ralph Goers commented on LOG4J2-1402: - Did you deploy it? Our Jenkins build doesn't deploy

Log4j 2.6.1

I just fixed LOGJ2-1402. I would also like to modify RenameAction to use java.nio.file to rename and delete so that we can get better logging out of them. Ultimately, I want to address LOG4J2-1180 to have the rolling file appender write directly into the “rollover files” as this is apparently

[jira] [Assigned] (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 reassigned LOG4J2-1250: --- Assignee: Ralph Goers > [2.5] CronTriggeringPolicy renaming behavior when midni

[jira] [Resolved] (LOG4J2-1402) org.apache.logging.log4j.core.config.ConfigurationException: No name attribute provided for Logger org

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

[jira] [Assigned] (LOG4J2-1402) org.apache.logging.log4j.core.config.ConfigurationException: No name attribute provided for Logger org

[ https://issues.apache.org/jira/browse/LOG4J2-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers reassigned LOG4J2-1402: --- Assignee: Ralph Goers > org.apache.logging.log4j.core.config.ConfigurationExcept

[jira] [Commented] (LOG4J2-1402) org.apache.logging.log4j.core.config.ConfigurationException: No name attribute provided for Logger org

[ https://issues.apache.org/jira/browse/LOG4J2-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15310982#comment-15310982 ] Ralph Goers commented on LOG4J2-1402: - Yes, that is what I would do

[jira] [Comment Edited] (LOG4J2-1402) org.apache.logging.log4j.core.config.ConfigurationException: No name attribute provided for Logger org

[ https://issues.apache.org/jira/browse/LOG4J2-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15310845#comment-15310845 ] Ralph Goers edited comment on LOG4J2-1402 at 6/1/16 6:43 PM: - Our properties

[jira] [Commented] (LOG4J2-1402) org.apache.logging.log4j.core.config.ConfigurationException: No name attribute provided for Logger org

[ https://issues.apache.org/jira/browse/LOG4J2-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15310845#comment-15310845 ] Ralph Goers commented on LOG4J2-1402: - Our properties file support had no relationship to 1.x

[jira] [Commented] (LOG4J2-1402) org.apache.logging.log4j.core.config.ConfigurationException: No name attribute provided for Logger org

[ https://issues.apache.org/jira/browse/LOG4J2-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15310715#comment-15310715 ] Ralph Goers commented on LOG4J2-1402: - Based on what you saw (presumably while debugging) I am

[jira] [Comment Edited] (LOG4J2-1402) org.apache.logging.log4j.core.config.ConfigurationException: No name attribute provided for Logger org

[ https://issues.apache.org/jira/browse/LOG4J2-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15310681#comment-15310681 ] Ralph Goers edited comment on LOG4J2-1402 at 6/1/16 5:18 PM: - I'm a bit

[jira] [Commented] (LOG4J2-1402) org.apache.logging.log4j.core.config.ConfigurationException: No name attribute provided for Logger org

[ https://issues.apache.org/jira/browse/LOG4J2-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15310681#comment-15310681 ] Ralph Goers commented on LOG4J2-1402: - I'm a bit confused. The error means that it found something

[jira] [Commented] (LOG4J2-1402) org.apache.logging.log4j.core.config.ConfigurationException: No name attribute provided for Logger org

[ https://issues.apache.org/jira/browse/LOG4J2-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15310644#comment-15310644 ] Ralph Goers commented on LOG4J2-1402: - We do have a special case. We have a createLogger method

[jira] [Comment Edited] (LOG4J2-1180) Logger cache does not account for message factory

[ https://issues.apache.org/jira/browse/LOG4J2-1180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15310615#comment-15310615 ] Ralph Goers edited comment on LOG4J2-1180 at 6/1/16 4:55 PM: - I don't know

[jira] [Commented] (LOG4J2-1180) Logger cache does not account for message factory

[ https://issues.apache.org/jira/browse/LOG4J2-1180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15310615#comment-15310615 ] Ralph Goers commented on LOG4J2-1180: - I don't know if this has anything to do with the problem

[jira] [Commented] (LOG4J2-1401) Support changing the log level for all messages related to some domain object

[ https://issues.apache.org/jira/browse/LOG4J2-1401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15307922#comment-15307922 ] Ralph Goers commented on LOG4J2-1401: - I don't remember if I created a Jira, but I had planned

[jira] [Commented] (LOG4J2-1400) RollingRandomAccessFile is not able to rotate log files

[ https://issues.apache.org/jira/browse/LOG4J2-1400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15306531#comment-15306531 ] Ralph Goers commented on LOG4J2-1400: - The list of files you are showing looks correct. max=&q

[jira] [Resolved] (LOG4J2-1400) RollingRandomAccessFile is not able to rotate log files

[ https://issues.apache.org/jira/browse/LOG4J2-1400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-1400. - Resolution: Not A Problem > RollingRandomAccessFile is not able to rotate log fi

[jira] [Updated] (LOG4J2-1400) RollingRandomAccessFile is not able to rotate log files

[ https://issues.apache.org/jira/browse/LOG4J2-1400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-1400: Description: In configuration like this: {code

Re: 2.6 is not source compatible with 2.5

I added the same information to the main site page. Ralph > On May 29, 2016, at 2:08 PM, Gary Gregory <garydgreg...@gmail.com> wrote: > > On Sun, May 29, 2016 at 1:41 PM, Ralph Goers <ralph.go...@dslextreme.com > <mailto:ralph.go...@dslextreme.com>> wrote: >

[ANNOUNCEMENT] Log4j 2.6 released

tion in last week of year. Thanks to Nikolai. o LOG4J2-1248: Fixed broken nanotime in pattern layout. o LOG4J2-908: JSONLayout doesn't add a comma between log events. Thanks to Konstantinos Liakos, Patrick Flaherty, Robin Coe, Gary Gregory. o LOG4J2-1230: Don't concatenate SYSLOG Messages. T

Re: 2.6 is not source compatible with 2.5

, at 11:14 AM, Matt Sicker <boa...@gmail.com> wrote:Yet another reason to hate null! ;)On 29 May 2016 at 13:13, Ralph Goers <ralph.go...@dslextreme.com> wrote:When you pass null as the first argument it doesn't know which is betterSent from my iPhoneOn May 29, 2016, at 11:07 AM, Matt

Re: 2.6 is not source compatible with 2.5

r? > >> On 29 May 2016 at 13:02, Ralph Goers <ralph.go...@dslextreme.com> wrote: >> Only if the compatibility issue can be fixed. I don't think it can. We will >> just update the site and announcement. >> >> Sent from my iPhone >> >>> On May

Re: 2.6 is not source compatible with 2.5

On 29 May 2016 at 12:29, Ralph Goers <ralph.go...@dslextreme.com> wrote: >> Can’t do that. That would require a re-release. >> >> Speaking of which, the archives directory only lists a couple of releases. I >> thought they were all supposed to be there. >>

Re: 2.6 is not source compatible with 2.5

LEASE-NOTES.txt in the dist area needs to be updated as well. > > Gary > > On Sun, May 29, 2016 at 10:15 AM, Ralph Goers <ralph.go...@dslextreme.com > <mailto:ralph.go...@dslextreme.com>> wrote: > I will add something to the announcement text when I send out the emails. &

Re: 2.6 is not source compatible with 2.5

I will add something to the announcement text when I send out the emails. Those will go out in a few hours. Ralph > On May 29, 2016, at 9:53 AM, Gary Gregory wrote: > > We are going to need to update the release notes and/or site for 2.6 to note > that the 2.6 is not

Re: 2.6 is not source compatible with 2.5

I suspect most people would have coded logger.error(message, t) though so hopefully it won’t be too bad. Ralph > On May 29, 2016, at 9:53 AM, Gary Gregory wrote: > > We are going to need to update the release notes and/or site for 2.6 to note > that the 2.6 is not

Re: 2.6 is not source compatible with 2.5

Darn. I wish you had caught that before the vote. That is not good. Ralph > On May 29, 2016, at 10:02 AM, Gary Gregory wrote: > > On Sun, May 29, 2016 at 9:57 AM, Gary Gregory > wrote: > And to make it more

Re: Logo themes

r2.6.png;hb=HEAD> > > Gary > > On Fri, May 27, 2016 at 3:44 PM, Ralph Goers <ralph.go...@dslextreme.com > <mailto:ralph.go...@dslextreme.com>> wrote: > Yes, the last slide. OTOH, if we don’t have each release have its own logo we > could add them all and add some

Re: [VOTE][RESULT] Log4j 2.6 rc1

The artifacts have been released. I will update the web site in the morning. Ralph > On May 28, 2016, at 11:10 PM, Ralph Goers <ralph.go...@dslextreme.com> wrote: > > The vote has passed with binding +1 votes from Remko Popma, Ralph Goers, Gary > Gregory and Matt Sicker. M

[VOTE][RESULT] Log4j 2.6 rc1

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

Re: Logo themes

y > > On Fri, May 27, 2016 at 3:44 PM, Ralph Goers <ralph.go...@dslextreme.com > <mailto:ralph.go...@dslextreme.com>> wrote: > Yes, the last slide. OTOH, if we don’t have each release have its own logo we > could add them all and add some javascript to pick one at r

Re: Logo themes

gt;> >> On Thu, May 26, 2016 at 11:58 PM, Gary Gregory <garydgreg...@gmail.com >> <mailto:garydgreg...@gmail.com>> wrote: >> I added a bunch more, just for fun. >> >> Gary >> >> On Thu, May 26, 2016 at 11:18 PM, Ralph Goers <ralp

Re: Logo themes

y Gregory <garydgreg...@gmail.com > <mailto:garydgreg...@gmail.com>> wrote: > I added a bunch more, just for fun. > > Gary > > On Thu, May 26, 2016 at 11:18 PM, Ralph Goers <ralph.go...@dslextreme.com > <mailto:ralph.go...@dslextreme.com>> wrote: > Y

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