from:"Ralph Goers"


[ 
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 with that.

> Faster Console appender
> ---
>
> Key: LOG4J2-1395
> URL: https://issues.apache.org/jira/browse/LOG4J2-1395
> Project: Log4j 2
>  Issue Type: Improvement
>  Components: Appenders
>Affects Versions: 2.5, 2.6, 2.6.1
>Reporter: Mikael Ståldal
> Attachments: ggregory-hardware.txt
>
>
> The ConsoleAppender is much slower than the FileAppender.
> It would be nice to improve the performance of the ConsoleAppender.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

Re: log4j2 evangelism

2016-06-13 Thread Ralph Goers

http://log4j-props2xml.appspot.com/ <http://log4j-props2xml.appspot.com/> 
https://github.com/jroyals/log4j-properties-converter/ 
<https://github.com/jroyals/log4j-properties-converter/>

https://github.com/mulesoft-labs/log4j2-migrator 
<https://github.com/mulesoft-labs/log4j2-migrator>

Ralph


> On Jun 13, 2016, at 10:37 AM, Matt Sicker <boa...@gmail.com> wrote:
> 
> What would be neat would be a tool like this one: 
> http://logback.qos.ch/translator/ <http://logback.qos.ch/translator/>
> 
> On 13 June 2016 at 12:08, Gary Gregory <garydgreg...@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 
> 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.  
> 
> Note that I started an effort to read Log4j 1 configuration files, please see 
> org.apache.log4j.config.Log4j1ConfigurationFactory. It is minimal but it is a 
> start. My longer term plan is to use that to help migrate my work app server 
> from Log4j 1 to 2 with less friction from our tools group and users.
> 
> Gary
>  
> At the very least we should link to that. If possible, we should consider 
> incorporating it into our web site.
> 
> What has been encouraging to me is the activity on Stack Overflow.  As of 
> right now I get 3,162 Log4j 2 questions vs 12,425 SLF4J questions and 6,581 
> Logback questions.  Both SLF4J and Logback have been around far longer.  I 
> think our participation there has really helped.
> 
> OTOH, the discussion on the Commons Dev list was rather disappointing.  
> 
> Ralph
> 
> 
>> On Jun 13, 2016, at 7:52 AM, Remko Popma <remko.po...@gmail.com 
>> <mailto:remko.po...@gmail.com>> wrote:
>> 
>> In spite of the fact that Log4j 2 has a very compelling story in terms of 
>> feature set and performance, I get the impression that adoption is quite 
>> slow. I could be wrong, but how many open source projects use Log4j 2? Or 
>> even how many Apache projects?
>> 
>> I propose we try to generate some ideas about what we can do to increase our 
>> uptake. Some things I've been thinking about:
>> 
>> * Rewrite the Wikipedia page on Log4j <https://en.wikipedia.org/wiki/Log4j>. 
>> It's mostly about Log4j 1.2 and mentions Log4j 2 at the bottom in a 
>> footnote. That needs to be the other way around in my opinion. The Wikipedia 
>> Java logging framework 
>> <https://en.wikipedia.org/wiki/Java_logging_framework> page is even worse.
>> * The Apache Logging site <https://logging.apache.org/> has no explicit 
>> mention that Log4j 1 is EOL.
>> * Only the top page on the Log4j 1 site 
>> <https://logging.apache.org/log4j/1.2/> mentions that the project is EOL, 
>> but it does so in two modest sentences that don't visually stick out and are 
>> easily ignored. At the very least the download page needs a mention of the 
>> EOL and a link to the Log4j 2 project, but it may be good to have a 
>> notification on every page.  
>> * Can we get other people involved in evangelizing log4j 2? It would be 
>> great if we can make more people enthusiastic so they write blog posts or 
>> tutorials etc about Log4j 2.
>> * How can we incentivise people to convert their project to Log4j 2? Maybe 
>> start a page on Projects Using Log4j 2 and mention people who did the 
>> conversion by name? Or some other way?
>> 
>> Thoughts?
>> 
>> Remko
> 
> 
> 
> 
> -- 
> E-Mail: garydgreg...@gmail.com <mailto:garydgreg...@gmail.com> | 
> ggreg...@apache.org  <mailto:ggreg...@apache.org>
> Java Persistence with Hibernate, Second Edition 
> <http://www.manning.com/bauer3/>
> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
> Spring Batch in Action <http://www.manning.com/templier/>
> Blog: http://garygregory.wordpress.com <http://garygregory.wordpress.com/> 
> Home: http://garygregory.com/ <http://garygregory.com/>
> Tweet! http://twitter.com/GaryGregory <http://twitter.com/GaryGregory>
> 
> 
> -- 
> Matt Sicker <boa...@gmail.com <mailto:boa...@gmail.com>>

Re: log4j2 evangelism

2016-06-13 Thread Ralph Goers

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 least we should 
link to that. If possible, we should consider incorporating it into our web 
site.

What has been encouraging to me is the activity on Stack Overflow.  As of right 
now I get 3,162 Log4j 2 questions vs 12,425 SLF4J questions and 6,581 Logback 
questions.  Both SLF4J and Logback have been around far longer.  I think our 
participation there has really helped.

OTOH, the discussion on the Commons Dev list was rather disappointing.  

Ralph

> On Jun 13, 2016, at 7:52 AM, Remko Popma  wrote:
> 
> In spite of the fact that Log4j 2 has a very compelling story in terms of 
> feature set and performance, I get the impression that adoption is quite 
> slow. I could be wrong, but how many open source projects use Log4j 2? Or 
> even how many Apache projects?
> 
> I propose we try to generate some ideas about what we can do to increase our 
> uptake. Some things I've been thinking about:
> 
> * Rewrite the Wikipedia page on Log4j . 
> It's mostly about Log4j 1.2 and mentions Log4j 2 at the bottom in a footnote. 
> That needs to be the other way around in my opinion. The Wikipedia Java 
> logging framework  page 
> is even worse.
> * The Apache Logging site  has no explicit 
> mention that Log4j 1 is EOL.
> * Only the top page on the Log4j 1 site 
>  mentions that the project is EOL, but 
> it does so in two modest sentences that don't visually stick out and are 
> easily ignored. At the very least the download page needs a mention of the 
> EOL and a link to the Log4j 2 project, but it may be good to have a 
> notification on every page.  
> * Can we get other people involved in evangelizing log4j 2? It would be great 
> if we can make more people enthusiastic so they write blog posts or tutorials 
> etc about Log4j 2.
> * How can we incentivise people to convert their project to Log4j 2? Maybe 
> start a page on Projects Using Log4j 2 and mention people who did the 
> conversion by name? Or some other way?
> 
> Thoughts?
> 
> Remko

[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 think it would be 
enough for the documentation to just express where it has been tested.

> Faster Console appender
> ---
>
> Key: LOG4J2-1395
> URL: https://issues.apache.org/jira/browse/LOG4J2-1395
> Project: Log4j 2
>  Issue Type: Improvement
>  Components: Appenders
>Affects Versions: 2.5, 2.6, 2.6.1
>Reporter: Mikael Ståldal
> Attachments: ggregory-hardware.txt
>
>
> The ConsoleAppender is much slower than the FileAppender.
> It would be nice to improve the performance of the ConsoleAppender.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[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 it needs to be.

> Faster Console appender
> ---
>
> Key: LOG4J2-1395
> URL: https://issues.apache.org/jira/browse/LOG4J2-1395
> Project: Log4j 2
>  Issue Type: Improvement
>  Components: Appenders
>Affects Versions: 2.5, 2.6, 2.6.1
>Reporter: Mikael Ståldal
> Attachments: ggregory-hardware.txt
>
>
> The ConsoleAppender is much slower than the FileAppender.
> It would be nice to improve the performance of the ConsoleAppender.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[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 and the Java spec 
don't actually describe how FileDescriptor.out/err should behave in relation to 
System.out/err.

> Faster Console appender
> ---
>
> Key: LOG4J2-1395
> URL: https://issues.apache.org/jira/browse/LOG4J2-1395
> Project: Log4j 2
>  Issue Type: Improvement
>  Components: Appenders
>Affects Versions: 2.5, 2.6, 2.6.1
>Reporter: Mikael Ståldal
> Attachments: ggregory-hardware.txt
>
>
> The ConsoleAppender is much slower than the FileAppender.
> It would be nice to improve the performance of the ConsoleAppender.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[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 also note that this only applies to the Oracle JVM as it is 
currently implemented. The behavior in other JVMs cannot be guaranteed.

I am also concerned that if the calling app redirects STDOUT that this 
enhancement may not be aware of it.


was (Author: ralph.go...@dslextreme.com):
You should note that this only applies to the Oraclr JVM as it is currently 
implemented. The behavior in other JVMs cannot be guaranteed.

I am also concerned that if the calling app redirects STDOUT that this 
enhancement may not be aware of it.

> Faster Console appender
> ---
>
> Key: LOG4J2-1395
> URL: https://issues.apache.org/jira/browse/LOG4J2-1395
> Project: Log4j 2
>  Issue Type: Improvement
>  Components: Appenders
>Affects Versions: 2.5, 2.6, 2.6.1
>Reporter: Mikael Ståldal
> Attachments: ggregory-hardware.txt
>
>
> The ConsoleAppender is much slower than the FileAppender.
> It would be nice to improve the performance of the ConsoleAppender.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[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 as it is currently 
implemented. The behavior in other JVMs cannot be guaranteed.

I am also concerned that if the calling app redirects STDOUT that this 
enhancement may not be aware of it.

> Faster Console appender
> ---
>
> Key: LOG4J2-1395
> URL: https://issues.apache.org/jira/browse/LOG4J2-1395
> Project: Log4j 2
>  Issue Type: Improvement
>  Components: Appenders
>Affects Versions: 2.5, 2.6, 2.6.1
>Reporter: Mikael Ståldal
> Attachments: ggregory-hardware.txt
>
>
> The ConsoleAppender is much slower than the FileAppender.
> It would be nice to improve the performance of the ConsoleAppender.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

Re: 2.6.2?

2016-06-12 Thread Ralph Goers

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 quite a bit of activity... :-) Do we plan on releasing a 2.6.2 
> soonish or waiting for a larger pile to materialize?
> 
> Gary
> 
> -- 
> E-Mail: garydgreg...@gmail.com  | 
> ggreg...@apache.org  
> Java Persistence with Hibernate, Second Edition 
> 
> JUnit in Action, Second Edition 
> Spring Batch in Action 
> Blog: http://garygregory.wordpress.com  
> Home: http://garygregory.com/ 
> Tweet! http://twitter.com/GaryGregory

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

2016-06-12 Thread Ralph Goers

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 built this locally and it worked fine.
> 
> On 12 June 2016 at 13:46, Apache Jenkins Server  > wrote:
> See  >
> 
> Changes:
> 
> [boards] Suppress pointless warning messages
> 
> --
> Started by an SCM change
> [EnvInject] - Loading node environment variables.
> Building remotely on ubuntu-1 (docker Ubuntu ubuntu yahoo-not-h2 ubuntu1) in 
> workspace  >
>  > git rev-parse --is-inside-work-tree # timeout=10
> Fetching changes from the remote Git repository
>  > git config remote.origin.url 
> https://git-wip-us.apache.org/repos/asf/logging-log4j2.git 
>  # timeout=10
> Fetching upstream changes from 
> https://git-wip-us.apache.org/repos/asf/logging-log4j2.git 
> 
>  > git --version # timeout=10
>  > git -c core.askpass=true fetch --tags --progress 
> https://git-wip-us.apache.org/repos/asf/logging-log4j2.git 
>  
> +refs/heads/*:refs/remotes/origin/*
>  > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
>  > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
> Checking out Revision 021da77c9b1615b63f9b3d2b89ab7f78e705a9df 
> (refs/remotes/origin/master)
>  > git config core.sparsecheckout # timeout=10
>  > git checkout -f 021da77c9b1615b63f9b3d2b89ab7f78e705a9df
>  > git rev-list 33162b9c292f119a944e8ca42f6698996c3b670b # timeout=10
> [EnvInject] - Executing scripts and injecting environment variables after the 
> SCM step.
> [EnvInject] - Injecting as environment variables the properties content
> LANG=en_US.UTF-8
> 
> [EnvInject] - Variables injected successfully.
> Parsing POMs
> Modules changed, recalculating dependency graph
> Established TCP socket on 49503
> maven32-agent.jar already up to date
> maven32-interceptor.jar already up to date
> maven3-interceptor-commons.jar already up to date
> [Log4j 2.x] $ 
> /home/jenkins/jenkins-slave/tools/hudson.model.JDK/jdk-1.7u51/bin/java -Xmx2g 
> -Xms256m -XX:MaxPermSize=512m -cp 
> /home/jenkins/jenkins-slave/maven32-agent.jar:/home/jenkins/jenkins-slave/tools/hudson.tasks.Maven_MavenInstallation/maven-3.2.1/boot/plexus-classworlds-2.5.1.jar:/home/jenkins/jenkins-slave/tools/hudson.tasks.Maven_MavenInstallation/maven-3.2.1/conf/logging
>  jenkins.maven3.agent.Maven32Main 
> /home/jenkins/jenkins-slave/tools/hudson.tasks.Maven_MavenInstallation/maven-3.2.1
>  /home/jenkins/jenkins-slave/slave.jar 
> /home/jenkins/jenkins-slave/maven32-interceptor.jar 
> /home/jenkins/jenkins-slave/maven3-interceptor-commons.jar 49503
> ERROR: Failed to parse POMs
> java.io.IOException: Remote call on ubuntu-1 failed
> at hudson.remoting.Channel.call(Channel.java:789)
> at hudson.Launcher$RemoteLauncher.launch(Launcher.java:928)
> at hudson.Launcher$ProcStarter.start(Launcher.java:381)
> at 
> hudson.maven.AbstractMavenProcessFactory.newProcess(AbstractMavenProcessFactory.java:281)
> at hudson.maven.ProcessCache.get(ProcessCache.java:236)
> at 
> hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:778)
> at 
> hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534)
> at hudson.model.Run.execute(Run.java:1738)
> at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531)
> at hudson.model.ResourceController.execute(ResourceController.java:98)
> at hudson.model.Executor.run(Executor.java:410)
> Caused by: java.lang.OutOfMemoryError: unable to create new native thread
> at java.lang.Thread.start0(Native Method)
> at java.lang.Thread.start(Thread.java:714)
> at hudson.Proc$LocalProc.(Proc.java:252)
> at hudson.Proc$LocalProc.(Proc.java:216)
> at hudson.Launcher$LocalLauncher.launch(Launcher.java:815)
> at hudson.Launcher$ProcStarter.start(Launcher.java:381)
> at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1148)
> at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1113)
> at hudson.remoting.UserRequest.perform(UserRequest.java:120)
> at hudson.remoting.UserRequest.perform(UserRequest.java:48)
> at hudson.remoting.Request$2.run(Request.java:326)
> at 
>

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

2016-06-12 Thread Ralph Goers

Same test though

Sent from my iPad

> On Jun 12, 2016, at 11:02 AM, Matt Sicker <boa...@gmail.com> wrote:
> 
> xz is the new friend, bz2 was the old friend. ;)
> 
>> On 12 June 2016 at 08:11, Remko Popma <remko.po...@gmail.com> wrote:
>> This was not your test 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 output though.
>>> 
>>> Sent from my iPad
>>> 
>>>> On Jun 12, 2016, at 3:42 AM, Remko Popma <remko.po...@gmail.com> wrote:
>>>> 
>>>> back to the old XZ failure...
>>>> 
>>>>> On Sun, Jun 12, 2016 at 6:11 PM, Apache Jenkins Server 
>>>>> <jenk...@builds.apache.org> wrote:
>>>>> See <https://builds.apache.org/job/Log4j%202.x/changes>
>>>>> 
>>>>> 
>>>>> -
>>>>> To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
>>>>> For additional commands, e-mail: log4j-dev-h...@logging.apache.org
>>>>> 
>>>> 
>> 
> 
> 
> 
> -- 
> Matt Sicker <boa...@gmail.com>

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

2016-06-12 Thread Ralph Goers

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 
>>  wrote:
>> See 
>> 
>> 
>> -
>> To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
>> For additional commands, e-mail: log4j-dev-h...@logging.apache.org
>

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

2016-06-12 Thread Ralph Goers

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 should be zero 
> and both should be the same length.
> 
> Ralph
> 
>> On Jun 11, 2016, at 11:44 PM, Remko Popma <remko.po...@gmail.com 
>> <mailto:remko.po...@gmail.com>> wrote:
>> 
>> If the first file on the stream is non-zero length, and the second file is 
>> 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, 2016, at 10:22 PM, Ralph Goers <ralph.go...@dslextreme.com 
>>> <mailto: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 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 <remko.po...@gmail.com 
>>> <mailto:remko.po...@gmail.com>> wrote:
>>> 
>>>> Hm... this is the second time I see this test fail:
>>>> Stacktrace
>>>> 
>>>> java.lang.AssertionError
>>>>at 
>>>> org.apache.logging.log4j.core.appender.rolling.RollingAppenderOnStartupTest.afterClass(RollingAppenderOnStartupTest.java:85)
>>>> 
>>>> What does this test do? It looks like it remembers the size of the first 
>>>> non-empty file in the directory, and then asserts that all other files are 
>>>> the same size, is that correct? 
>>>> 
>>>> @AfterClass
>>>> public static void afterClass() throws Exception {
>>>> long size = 0;
>>>> try (DirectoryStream directoryStream = 
>>>> Files.newDirectoryStream(Paths.get("target/onStartup"))) {
>>>> for (Path path : directoryStream) {
>>>> if (size == 0) {
>>>> size = Files.size(path);
>>>> } else {
>>>> assertTrue(size == Files.size(path)); // <- line 85 
>>>> }
>>>> Files.delete(path);
>>>> }
>>>> Files.delete(Paths.get("target/onStartup"));
>>>> }
>>>> }
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> On Sun, Jun 12, 2016 at 1:17 PM, Apache Jenkins Server 
>>>> <jenk...@builds.apache.org <mailto:jenk...@builds.apache.org>> wrote:
>>>> See <https://builds.apache.org/job/Log4j%202.x/2019/changes 
>>>> <https://builds.apache.org/job/Log4j%202.x/2019/changes>>
>>>> 
>>>> 
>>>> -
>>>> To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org 
>>>> <mailto:log4j-dev-unsubscr...@logging.apache.org>
>>>> For additional commands, e-mail: log4j-dev-h...@logging.apache.org 
>>>> <mailto:log4j-dev-h...@logging.apache.org>
>>>> 
>>>> 
>> 
>> 
>

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

2016-06-12 Thread Ralph Goers

Both files write a header, 100 events and a footer. Neither should be zero and 
both should be the same length.

Ralph

> On Jun 11, 2016, at 11:44 PM, Remko Popma <remko.po...@gmail.com> wrote:
> 
> If the first file on the stream is non-zero length, and the second file is 
> 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, 2016, at 10:22 PM, Ralph Goers <ralph.go...@dslextreme.com 
>> <mailto: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 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 <remko.po...@gmail.com 
>> <mailto:remko.po...@gmail.com>> wrote:
>> 
>>> Hm... this is the second time I see this test fail:
>>> Stacktrace
>>> 
>>> java.lang.AssertionError
>>> at 
>>> org.apache.logging.log4j.core.appender.rolling.RollingAppenderOnStartupTest.afterClass(RollingAppenderOnStartupTest.java:85)
>>> 
>>> What does this test do? It looks like it remembers the size of the first 
>>> non-empty file in the directory, and then asserts that all other files are 
>>> the same size, is that correct? 
>>> 
>>> @AfterClass
>>> public static void afterClass() throws Exception {
>>> long size = 0;
>>> try (DirectoryStream directoryStream = 
>>> Files.newDirectoryStream(Paths.get("target/onStartup"))) {
>>> for (Path path : directoryStream) {
>>> if (size == 0) {
>>> size = Files.size(path);
>>> } else {
>>> assertTrue(size == Files.size(path)); // <- line 85 
>>> }
>>> Files.delete(path);
>>> }
>>> Files.delete(Paths.get("target/onStartup"));
>>> }
>>> }
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> On Sun, Jun 12, 2016 at 1:17 PM, Apache Jenkins Server 
>>> <jenk...@builds.apache.org <mailto:jenk...@builds.apache.org>> wrote:
>>> See <https://builds.apache.org/job/Log4j%202.x/2019/changes 
>>> <https://builds.apache.org/job/Log4j%202.x/2019/changes>>
>>> 
>>> 
>>> -
>>> To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org 
>>> <mailto:log4j-dev-unsubscr...@logging.apache.org>
>>> For additional commands, e-mail: log4j-dev-h...@logging.apache.org 
>>> <mailto:log4j-dev-h...@logging.apache.org>
>>> 
>>> 
> 
>

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

2016-06-11 Thread Ralph Goers

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 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 <remko.po...@gmail.com 
> <mailto:remko.po...@gmail.com>> wrote:
> 
>> Hm... this is the second time I see this test fail:
>> Stacktrace
>> 
>> java.lang.AssertionError
>>  at 
>> org.apache.logging.log4j.core.appender.rolling.RollingAppenderOnStartupTest.afterClass(RollingAppenderOnStartupTest.java:85)
>> 
>> What does this test do? It looks like it remembers the size of the first 
>> non-empty file in the directory, and then asserts that all other files are 
>> the same size, is that correct? 
>> 
>> @AfterClass
>> public static void afterClass() throws Exception {
>> long size = 0;
>> try (DirectoryStream directoryStream = 
>> Files.newDirectoryStream(Paths.get("target/onStartup"))) {
>> for (Path path : directoryStream) {
>> if (size == 0) {
>> size = Files.size(path);
>> } else {
>> assertTrue(size == Files.size(path)); // <- line 85 
>> }
>> Files.delete(path);
>> }
>> Files.delete(Paths.get("target/onStartup"));
>> }
>> }
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> On Sun, Jun 12, 2016 at 1:17 PM, Apache Jenkins Server 
>> <jenk...@builds.apache.org <mailto:jenk...@builds.apache.org>> wrote:
>> See <https://builds.apache.org/job/Log4j%202.x/2019/changes 
>> <https://builds.apache.org/job/Log4j%202.x/2019/changes>>
>> 
>> 
>> -
>> To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org 
>> <mailto:log4j-dev-unsubscr...@logging.apache.org>
>> For additional commands, e-mail: log4j-dev-h...@logging.apache.org 
>> <mailto:log4j-dev-h...@logging.apache.org>
>> 
>>

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

2016-06-11 Thread Ralph Goers

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:
> 
> Hm... this is the second time I see this test fail:
> Stacktrace
> 
> java.lang.AssertionError
>   at 
> org.apache.logging.log4j.core.appender.rolling.RollingAppenderOnStartupTest.afterClass(RollingAppenderOnStartupTest.java:85)
> 
> What does this test do? It looks like it remembers the size of the first 
> non-empty file in the directory, and then asserts that all other files are 
> the same size, is that correct? 
> 
> @AfterClass
> public static void afterClass() throws Exception {
> long size = 0;
> try (DirectoryStream directoryStream = 
> Files.newDirectoryStream(Paths.get("target/onStartup"))) {
> for (Path path : directoryStream) {
> if (size == 0) {
> size = Files.size(path);
> } else {
> assertTrue(size == Files.size(path)); // <- line 85 
> }
> Files.delete(path);
> }
> Files.delete(Paths.get("target/onStartup"));
> }
> }
> 
> 
> 
> 
> 
> 
> 
> 
> 
>> On Sun, Jun 12, 2016 at 1:17 PM, Apache Jenkins Server 
>>  wrote:
>> See 
>> 
>> 
>> -
>> To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
>> For additional commands, e-mail: log4j-dev-h...@logging.apache.org
>

[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 6.2
> -
>
> Key: LOG4J2-548
> URL: https://issues.apache.org/jira/browse/LOG4J2-548
> Project: Log4j 2
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 2.0-rc1, 2.1
> Environment: EJB 3.1 , JBoss EAP 6.2 , Windows 7 , Eclipse Kepler 
>Reporter: Shehata
>Assignee: Ralph Goers
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> When trying to use log4j 2.0-rc1 with EJB3.1 i got Error Message:
> "ERROR StatusLogger Could not search jar file 
> 'jboss-eap-6.2\standalone\deployments\Log4J2Ear.ear\lib\log4j-core-2.0-rc1.jar\org\apache\logging\log4j\core'
>  for classes matching criteria: annotated with @Plugin file not found"
> after debugging the application found that the problem is located in :
> org.apache.logging.log4j.core.config.plugins.ResolverUtil
> method: findInPackage --> line number 247
> the protocol used in the jar is vfs not vfszip



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

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

> Changing AsyncLogger level programmatically not working properly
> 
>
> Key: LOG4J2-823
> URL: https://issues.apache.org/jira/browse/LOG4J2-823
> Project: Log4j 2
>  Issue Type: Bug
>  Components: Appenders
>Affects Versions: 2.0-rc2
>Reporter: Pranav Pratap
>  Labels: AsyncLogger
>
> I am trying to programmatically change the log level of AsyncLogger. But 
> unable to do so. 
> Programmatically we can change AsyncRoot or Root Log level using below code:
> LoggerContext ctx = (LoggerContext) LogManager.getContext(false);
>   Configuration config = ctx.getConfiguration();
>   LoggerConfig loggerConfig = 
> config.getLoggerConfig(LogManager.ROOT_LOGGER_NAME);
>   loggerConfig.setLevel(level);
>   ctx.updateLoggers();
> How to achieve the same for AsyncLogger? Please suggest. I searched many 
> forums but all provide the way for Root Level or AsyncRoot Log Level Change. 
> But no once suggest the AsyncLogger logger level change mechanism.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[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 implementations should be serializable
> -
>
> Key: LOG4J2-800
> URL: https://issues.apache.org/jira/browse/LOG4J2-800
> Project: Log4j 2
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 2.0.2
> Environment: Apache Maven 3.2.3 
> (33f8c3e1027c3ddde99d3cdebad2656a31e8fdf4; 2014-08-11T16:58:10-04:00)
> Maven home: C:\Java\apache-maven-3.2.3
> Java version: 1.7.0_65, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.7.0_65\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
>Reporter: Gary Gregory
>Assignee: Gary Gregory
>
> All internal life cycle implementations should be serializable:
> {code:java}
> public class AbstractLifeCycle implements LifeCycle, Serializable
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[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 this.

> RegexFilter does not match multiline log messages
> -
>
> Key: LOG4J2-696
> URL: https://issues.apache.org/jira/browse/LOG4J2-696
> Project: Log4j 2
>  Issue Type: Bug
>  Components: Filters
>Affects Versions: 2.0-rc2
>Reporter: phil wray
>Assignee: Ralph Goers
> Attachments: RegexFilterTest.java
>
>
> RegexFilter is constructed with a pattern, but pattern does not support 
> multiline matches, so impossible for the filter to ever match a multiline msg.
> Should maybe provide a multline="x attribute whichi should default to true 
> and result in the patter being compiled as such:
> Pattern pattern = Pattern.compile(".*line.*", Pattern.DOTALL);
> See attached UnitTest illustrating failure



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[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 messages
> -
>
> Key: LOG4J2-696
> URL: https://issues.apache.org/jira/browse/LOG4J2-696
> Project: Log4j 2
>  Issue Type: Bug
>  Components: Filters
>Affects Versions: 2.0-rc2
>Reporter: phil wray
>Assignee: Ralph Goers
> Attachments: RegexFilterTest.java
>
>
> RegexFilter is constructed with a pattern, but pattern does not support 
> multiline matches, so impossible for the filter to ever match a multiline msg.
> Should maybe provide a multline="x attribute whichi should default to true 
> and result in the patter being compiled as such:
> Pattern pattern = Pattern.compile(".*line.*", Pattern.DOTALL);
> See attached UnitTest illustrating failure



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[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 classpath not working correct in osgi environment
> 
>
> Key: LOG4J2-159
> URL: https://issues.apache.org/jira/browse/LOG4J2-159
> Project: Log4j 2
>  Issue Type: Bug
>  Components: API, Core
>Affects Versions: 2.0-beta3, 2.0-rc1
> Environment: win7, eclipse 3.7 64bit
>Reporter: Jan Winter
>Assignee: Ralph Goers
>Priority: Trivial
> Fix For: 2.3
>
>
> I have problems while loading log4j.xml configuration file in osgi 
> environment. 
> I have the following started equinox container: 
> +
> | osgi> ss log4j 
> | 
> | Framework is launched. 
> | 
> | id  State Bundle 
> | 58  RESOLVED my.log4j.xml.fragment 
> | Master=136 
> | 136 RESOLVED org.apache.commons.log4j-api_2.0.0.beta3 
> | Fragments=58 
> | 137 RESOLVED org.apache.commons.log4j-core_2.0.0.beta3 
> +
> The log4j2 config file is packaged under my.log4j.xml.fragment.jar/log4j.xml. 
> If I have the upper bundle-configuration 
> - than the following output happens: 
> +
> | ERROR StatusLogger Unable to locate a logging implementation, using 
> SimpleLogger 
> | FATAL Log4j_2 log4j-2.0.x logging 
> | ERROR Log4j_2 log4j-2.0.x logging 
> +
> *QUICKFIX* If I update the 
> org.apache.commons.log4j-core_2.0.0.beta3.jar!/META-INF/MANIFEST.MF 
> - append: Fragment-Host: org.apache.commons.log4j-api 
> - than log4j2 configuration is loaded and work. 
> +
> | osgi> ss log4j 
> |
> | Framework is launched. 
> | 
> | id  State Bundle 
> | 58  RESOLVED my.log4j.xml.fragment 
> | Master=136 
> | 136 RESOLVED org.apache.commons.log4j-api_2.0.0.beta3 
> | Fragments=58, 137 
> | 137 RESOLVED org.apache.commons.log4j-core_2.0.0.beta3 
> | Master=136 
> +



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[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 updated in 2 years.

> Add plugin builder classes as alternative to factory methods.
> -
>
> Key: LOG4J2-653
> URL: https://issues.apache.org/jira/browse/LOG4J2-653
> Project: Log4j 2
>  Issue Type: Improvement
>  Components: Plugins
>Reporter: Matt Sicker
>Assignee: Matt Sicker
>  Labels: config
>
> It would be useful to have builder-style classes as an alternative to plugin 
> factory methods. This would be useful in two settings:
> # Easier to construct plugins in tests and in the code.
> # Can add annotations to fields for value injection in the PluginBuilder 
> class.
> This could replace the existing factory methods, or it could complement it. 
> This would also make it easier to support programmatic configuration.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[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 close.

> 2.6.1 - NPE due to OnStartupTriggeringPolicy changes
> 
>
> Key: LOG4J2-1420
> URL: https://issues.apache.org/jira/browse/LOG4J2-1420
> Project: Log4j 2
>  Issue Type: Bug
>Affects Versions: 2.6.1
>Reporter: Leon Finker
>    Assignee: Ralph Goers
> Fix For: 2.6.2
>
>
> Hi,
> Noticed an NPE with one of our configurations with 2.6.1 (doesn't happen on 
> previous versions). Looks like it's due to changes for LOG4J2-1405. Looks 
> like the file size in RollingFileManager constructor is set before the 
> randomAccessFile in RollingRandomAccessFileManager ctor. And the actual 
> policy triggering happens in RollingFileManager  before the randomAccessFile 
> is assigned:triggeringPolicy.initialize(this); I guess that's why there was 
> somewhat an elaborate logic in previous version of OnStartupTriggeringPolicy 
> and the actual rollover was decided in isTriggeringEvent.
> The NPE always happens with OnStartupTriggeringPolicy and if previous file is 
> not empty.
> {noformat}
> 2016-06-09 13:38:57,060 main ERROR Unable to invoke factory method in class 
> class org.apache.logging.log4j.core.appender.RollingRandomAccessFileAppender 
> for element RollingRandomAccessFile. 
> java.lang.reflect.InvocationTargetException
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.build(PluginBuilder.java:132)
>   at 
> org.apache.logging.log4j.core.config.AbstractConfiguration.createPluginObject(AbstractConfiguration.java:918)
>   at 
> org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:858)
>   at 
> org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:850)
>   at 
> org.apache.logging.log4j.core.config.AbstractConfiguration.doConfigure(AbstractConfiguration.java:479)
>   at 
> org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:219)
>   at 
> org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:231)
>   at 
> org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:491)
>   at 
> org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:561)
>   at 
> org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:577)
>   at 
> org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:212)
>   at 
> org.apache.logging.log4j.core.async.AsyncLoggerContext.start(AsyncLoggerContext.java:75)
>   at 
> org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:152)
>   at 
> org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:45)
>   at org.apache.logging.log4j.LogManager.getContext(LogManager.java:194)
>   at 
> org.apache.logging.log4j.spi.AbstractLoggerAdapter.getContext(AbstractLoggerAdapter.java:103)
>   at 
> org.apache.logging.slf4j.Log4jLoggerFactory.getContext(Log4jLoggerFactory.java:43)
>   at 
> org.apache.logging.log4j.spi.AbstractLoggerAdapter.getLogger(AbstractLoggerAdapter.java:42)
>   at 
> org.apache.logging.slf4j.Log4jLoggerFactory.getLogger(Log4jLoggerFactory.java:29)
>   at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:358)
>   at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:383)
>   at 
> com.tradingscreen.gemfire.server.CacheServer.(CacheServer.java:46)
> Caused by: java.lang.NullPointerException
>   at 
> org.apache.logging.log4j.core.appender.rolling.RollingRandomAccessFileManager.close(RollingRandomAccessFileManager.java:128)
>   at 
> org.apache.logging.log4j.core.appender.rolling.RollingFileManager.rollover(RollingFileManager.java:211)
>   at 
> org.apache.logging.log4j.core.appender.rolling.RollingFileManager.rollover(RollingFileManager.java:142)
>   at 
> org.apache.logging.log4j.core.appender.rolling.OnStartupTriggeringPolicy.ini

[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 due to OnStartupTriggeringPolicy changes
> 
>
> Key: LOG4J2-1420
> URL: https://issues.apache.org/jira/browse/LOG4J2-1420
> Project: Log4j 2
>  Issue Type: Bug
>Affects Versions: 2.6.1
>Reporter: Leon Finker
>
> Hi,
> Noticed an NPE with one of our configurations with 2.6.1 (doesn't happen on 
> previous versions). Looks like it's due to changes for LOG4J2-1405. Looks 
> like the file size in RollingFileManager constructor is set before the 
> randomAccessFile in RollingRandomAccessFileManager ctor. And the actual 
> policy triggering happens in RollingFileManager  before the randomAccessFile 
> is assigned:triggeringPolicy.initialize(this); I guess that's why there was 
> somewhat an elaborate logic in previous version of OnStartupTriggeringPolicy 
> and the actual rollover was decided in isTriggeringEvent.
> The NPE always happens with OnStartupTriggeringPolicy and if previous file is 
> not empty.
> {noformat}
> 2016-06-09 13:38:57,060 main ERROR Unable to invoke factory method in class 
> class org.apache.logging.log4j.core.appender.RollingRandomAccessFileAppender 
> for element RollingRandomAccessFile. 
> java.lang.reflect.InvocationTargetException
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.build(PluginBuilder.java:132)
>   at 
> org.apache.logging.log4j.core.config.AbstractConfiguration.createPluginObject(AbstractConfiguration.java:918)
>   at 
> org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:858)
>   at 
> org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:850)
>   at 
> org.apache.logging.log4j.core.config.AbstractConfiguration.doConfigure(AbstractConfiguration.java:479)
>   at 
> org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:219)
>   at 
> org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:231)
>   at 
> org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:491)
>   at 
> org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:561)
>   at 
> org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:577)
>   at 
> org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:212)
>   at 
> org.apache.logging.log4j.core.async.AsyncLoggerContext.start(AsyncLoggerContext.java:75)
>   at 
> org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:152)
>   at 
> org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:45)
>   at org.apache.logging.log4j.LogManager.getContext(LogManager.java:194)
>   at 
> org.apache.logging.log4j.spi.AbstractLoggerAdapter.getContext(AbstractLoggerAdapter.java:103)
>   at 
> org.apache.logging.slf4j.Log4jLoggerFactory.getContext(Log4jLoggerFactory.java:43)
>   at 
> org.apache.logging.log4j.spi.AbstractLoggerAdapter.getLogger(AbstractLoggerAdapter.java:42)
>   at 
> org.apache.logging.slf4j.Log4jLoggerFactory.getLogger(Log4jLoggerFactory.java:29)
>   at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:358)
>   at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:383)
>   at 
> com.tradingscreen.gemfire.server.CacheServer.(CacheServer.java:46)
> Caused by: java.lang.NullPointerException
>   at 
> org.apache.logging.log4j.core.appender.rolling.RollingRandomAccessFileManager.close(RollingRandomAccessFileManager.java:128)
>   at 
> org.apache.logging.log4j.core.appender.rolling.RollingFileManager.rollover(RollingFileManager.java:211)
>   at 
> org.apache.logging.log4j.core.appender.rolling.RollingFileManager.rollover(RollingFileManager.java:142)
>   at 
> org.apache.logging.log4j.core.appender.rolling.OnStartupTriggeringPolicy.initialize(OnStartupTriggeringPolicy.java:43)
>   at 
> org.apache.logging.log4j.core.appender.rolling.CompositeTriggeringP

[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 changes
> 
>
> Key: LOG4J2-1420
> URL: https://issues.apache.org/jira/browse/LOG4J2-1420
> Project: Log4j 2
>  Issue Type: Bug
>Affects Versions: 2.6.1
>Reporter: Leon Finker
>    Assignee: Ralph Goers
>
> Hi,
> Noticed an NPE with one of our configurations with 2.6.1 (doesn't happen on 
> previous versions). Looks like it's due to changes for LOG4J2-1405. Looks 
> like the file size in RollingFileManager constructor is set before the 
> randomAccessFile in RollingRandomAccessFileManager ctor. And the actual 
> policy triggering happens in RollingFileManager  before the randomAccessFile 
> is assigned:triggeringPolicy.initialize(this); I guess that's why there was 
> somewhat an elaborate logic in previous version of OnStartupTriggeringPolicy 
> and the actual rollover was decided in isTriggeringEvent.
> The NPE always happens with OnStartupTriggeringPolicy and if previous file is 
> not empty.
> {noformat}
> 2016-06-09 13:38:57,060 main ERROR Unable to invoke factory method in class 
> class org.apache.logging.log4j.core.appender.RollingRandomAccessFileAppender 
> for element RollingRandomAccessFile. 
> java.lang.reflect.InvocationTargetException
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.build(PluginBuilder.java:132)
>   at 
> org.apache.logging.log4j.core.config.AbstractConfiguration.createPluginObject(AbstractConfiguration.java:918)
>   at 
> org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:858)
>   at 
> org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:850)
>   at 
> org.apache.logging.log4j.core.config.AbstractConfiguration.doConfigure(AbstractConfiguration.java:479)
>   at 
> org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:219)
>   at 
> org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:231)
>   at 
> org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:491)
>   at 
> org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:561)
>   at 
> org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:577)
>   at 
> org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:212)
>   at 
> org.apache.logging.log4j.core.async.AsyncLoggerContext.start(AsyncLoggerContext.java:75)
>   at 
> org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:152)
>   at 
> org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:45)
>   at org.apache.logging.log4j.LogManager.getContext(LogManager.java:194)
>   at 
> org.apache.logging.log4j.spi.AbstractLoggerAdapter.getContext(AbstractLoggerAdapter.java:103)
>   at 
> org.apache.logging.slf4j.Log4jLoggerFactory.getContext(Log4jLoggerFactory.java:43)
>   at 
> org.apache.logging.log4j.spi.AbstractLoggerAdapter.getLogger(AbstractLoggerAdapter.java:42)
>   at 
> org.apache.logging.slf4j.Log4jLoggerFactory.getLogger(Log4jLoggerFactory.java:29)
>   at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:358)
>   at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:383)
>   at 
> com.tradingscreen.gemfire.server.CacheServer.(CacheServer.java:46)
> Caused by: java.lang.NullPointerException
>   at 
> org.apache.logging.log4j.core.appender.rolling.RollingRandomAccessFileManager.close(RollingRandomAccessFileManager.java:128)
>   at 
> org.apache.logging.log4j.core.appender.rolling.RollingFileManager.rollover(RollingFileManager.java:211)
>   at 
> org.apache.logging.log4j.core.appender.rolling.RollingFileManager.rollover(RollingFileManager.java:142)
>   at 
> org.apache.logging.log4j.core.appender.rolling.OnStartupTriggeringPolicy.initialize(OnStartupTriggeringPolicy.

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

2016-06-10 Thread Ralph Goers (JIRA)


[ 
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 FileManager didn't 
expose a rollover method. Now that it does it simplifies the logic of 
performing a rollover.

It looks to me that RollingRandomAccessFileManager needs a number of changes in 
addition to fixing the NPE as I believe it will still write headers and footers 
when it shouldn't.

> 2.6.1 - NPE due to OnStartupTriggeringPolicy changes
> 
>
> Key: LOG4J2-1420
> URL: https://issues.apache.org/jira/browse/LOG4J2-1420
> Project: Log4j 2
>  Issue Type: Bug
>Affects Versions: 2.6.1
>Reporter: Leon Finker
>
> Hi,
> Noticed an NPE with one of our configurations with 2.6.1 (doesn't happen on 
> previous versions). Looks like it's due to changes for LOG4J2-1405. Looks 
> like the file size in RollingFileManager constructor is set before the 
> randomAccessFile in RollingRandomAccessFileManager ctor. And the actual 
> policy triggering happens in RollingFileManager  before the randomAccessFile 
> is assigned:triggeringPolicy.initialize(this); I guess that's why there was 
> somewhat an elaborate logic in previous version of OnStartupTriggeringPolicy 
> and the actual rollover was decided in isTriggeringEvent.
> The NPE always happens with OnStartupTriggeringPolicy and if previous file is 
> not empty.
> {noformat}
> 2016-06-09 13:38:57,060 main ERROR Unable to invoke factory method in class 
> class org.apache.logging.log4j.core.appender.RollingRandomAccessFileAppender 
> for element RollingRandomAccessFile. 
> java.lang.reflect.InvocationTargetException
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.build(PluginBuilder.java:132)
>   at 
> org.apache.logging.log4j.core.config.AbstractConfiguration.createPluginObject(AbstractConfiguration.java:918)
>   at 
> org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:858)
>   at 
> org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:850)
>   at 
> org.apache.logging.log4j.core.config.AbstractConfiguration.doConfigure(AbstractConfiguration.java:479)
>   at 
> org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:219)
>   at 
> org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:231)
>   at 
> org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:491)
>   at 
> org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:561)
>   at 
> org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:577)
>   at 
> org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:212)
>   at 
> org.apache.logging.log4j.core.async.AsyncLoggerContext.start(AsyncLoggerContext.java:75)
>   at 
> org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:152)
>   at 
> org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:45)
>   at org.apache.logging.log4j.LogManager.getContext(LogManager.java:194)
>   at 
> org.apache.logging.log4j.spi.AbstractLoggerAdapter.getContext(AbstractLoggerAdapter.java:103)
>   at 
> org.apache.logging.slf4j.Log4jLoggerFactory.getContext(Log4jLoggerFactory.java:43)
>   at 
> org.apache.logging.log4j.spi.AbstractLoggerAdapter.getLogger(AbstractLoggerAdapter.java:42)
>   at 
> org.apache.logging.slf4j.Log4jLoggerFactory.getLogger(Log4jLoggerFactory.java:29)
>   at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:358)
>   at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:383)
>   at 
> com.tradingscreen.gemfire.server.CacheServer.(CacheServer.java:46)
> Caused by: java.lang.NullPointerException
>   at 
> org.apache.logging.log4j.core.appender.rolling.RollingRandomAccessFileManager.close(RollingRandomAccessFileManager.java:128)
>   at 
> org.apache.logging.log4j.core.appender.rolling.RollingFileManager.rollover(RollingFileManager.java:211)
>   a

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

2016-06-10 Thread Ralph Goers (JIRA)


[ 
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 release tag when 
the site is generated. I will be checking that in tonight.

There is no surefire report for the top level because there are no tests (or 
code for that matter). I have no idea why Maven generates the report anyway. 
The same is true for the dependencies page. We don't have a dependencies 
section in the parent pom. If we had one we might at least get an empty page.

> Minor issues with the 2.6.1 web site
> 
>
> Key: LOG4J2-1414
> URL: https://issues.apache.org/jira/browse/LOG4J2-1414
> Project: Log4j 2
>  Issue Type: Bug
>  Components: Documentation
>Affects Versions: 2.6.1
>Reporter: Remko Popma
>Priority: Minor
>
> 2.6
> (-) Project Information -> Dependencies, does not exist (I believe there's 
> already a bug report for this link)
> (-) Source Repository, git checkout info references a release candidate tag. 
> Will this be updated when an official release is tagged?
> (-) Surefire Report, does not exist
> (-) Manual page on 
> [Messages|http://logging.apache.org/log4j/2.x/manual/messages.html] is 
> missing the new ReusableXxxMessage types
> 2.6.1
> (/) [Changes Report|http://rgoers.github.io/log4j2-site/changes-report.html]  
> Release date is "Release 2.6.1 – 2016-MM-DD"
> (/) (Not an issue) Add German article on Log4j to the list: 
> https://jaxenter.de/apache-log4j-2-6-laeuft-nun-auch-ohne-muell-41098



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

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

2016-06-10 Thread Ralph Goers (JIRA)


[ 
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 forgot to update the changes.xml again!  I will update that tonight.

I have a fix for the git checkout info to point to the actual release tag when 
the site is generated. I will be checking that in tonight.

There is no surefire report for the top level because there are no tests (or 
code for that matter). I have no idea why Maven generates the report anyway. 
The same is true for the dependencies page. We don't have a dependencies 
section in the parent pom. If we had one we might at least get an empty page.


was (Author: ralph.go...@dslextreme.com):
I have a fix for the git checkout info to point to the actual release tag when 
the site is generated. I will be checking that in tonight.

There is no surefire report for the top level because there are no tests (or 
code for that matter). I have no idea why Maven generates the report anyway. 
The same is true for the dependencies page. We don't have a dependencies 
section in the parent pom. If we had one we might at least get an empty page.

> Minor issues with the 2.6.1 web site
> 
>
> Key: LOG4J2-1414
> URL: https://issues.apache.org/jira/browse/LOG4J2-1414
> Project: Log4j 2
>  Issue Type: Bug
>  Components: Documentation
>Affects Versions: 2.6.1
>Reporter: Remko Popma
>Priority: Minor
>
> 2.6
> (-) Project Information -> Dependencies, does not exist (I believe there's 
> already a bug report for this link)
> (-) Source Repository, git checkout info references a release candidate tag. 
> Will this be updated when an official release is tagged?
> (-) Surefire Report, does not exist
> (-) Manual page on 
> [Messages|http://logging.apache.org/log4j/2.x/manual/messages.html] is 
> missing the new ReusableXxxMessage types
> 2.6.1
> (/) [Changes Report|http://rgoers.github.io/log4j2-site/changes-report.html]  
> Release date is "Release 2.6.1 – 2016-MM-DD"
> (/) (Not an issue) Add German article on Log4j to the list: 
> https://jaxenter.de/apache-log4j-2-6-laeuft-nun-auch-ohne-muell-41098



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[ANNOUNCEMENT] Log4j 2.6.1 released

2016-06-09 Thread Ralph Goers

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 support for Markers, property substitution 
using Lookups, multiple patterns on
a PatternLayout and asynchronous Loggers. In addition, Log4j 2 will not lose 
events while reconfiguring.

This is the eleventh GA release. It is primarily a bugfix release. More details 
on the fixes are itemized below.

Note that subsequent to the 2.6 release a minor source incompatibility was 
found due to the addition of new methods to
the Logger interface. If you have code that does:

logger.error(null, “This is the log message”, throwable);

or similar with any log level you will get a compiler error saying the 
reference is ambiguous.  To correct this either do:

logger.error(“This is the log message”, throwable);

or

logger.error((Marker) null, “This is the log message”, throwable);

Log4j 2.6 maintains binary compatibility with previous releases.

GA Release 2.6.1

Changes in this version include:

New features:
o LOG4J2-1411:  Add documentation about plugin builders compared to factories. 

Fixed Bugs:
o LOG4J2-1405:  OnStartupTriggeringPolicy was forcing a rollover of empty files 
at startup and would append a
second footer that was added by the prior shutdown. 
o LOG4J2-1406:  Fixed bug in ReusableParameterizedMessage where Throwable was 
never updated so first error was logged over
and over again and subsequent errors were not logged. Thanks to Trask 
Stalnaker. 
o LOG4J2-1409:  Fixed ArrayIndexOutOfBoundsException that may occur in 
ReusableParameterizedMessage. Thanks to Shahan. 
o LOG4J2-997:  Add filter and remove filter were not working properly in 
AbstractFilterable. Thanks to Maytee Chinavanichkit. 
o LOG4J2-1032:  Change RenameAction to use java.nio to better report rename 
failures. 
o LOG4J2-1407:  Misleading WARN log events from Log4j about message factories 
and unexpected formatting. Thanks to Gary Gregory. 
o LOG4J2-1408:  The module log4j-liquibase is missing from BOM POM. Thanks to 
Gary Gregory. 
o LOG4J2-1180:  Logger cache does not account for message factory. Thanks to 
Gary Gregory. 
o LOG4J2-1402:  Fix regression in properties configuration to support arbitrary 
component ids. 

Changes:
o LOG4J2-1385:  (GC) CSV layouts should not create a new CSVPrinter for each 
log event. Requires Apache Commons CSV 1.4. 
o LOG4J2-1398:  Update liquibase-core from 3.4.2 to 3.5.1. 
o LOG4J2-1399:  Update Apache Commons CSV from 1.3 to 1.4. 


Apache Log4j 2.6.1 requires a minimum of Java 7 to build and run. Log4j 2.3 was 
the last release that
supported Java 6.

Basic compatibility with Log4j 1.x is provided through the log4j-1.2-api 
component, however it does not implement some of the
very implementation specific classes and methods. The package names and Maven 
groupId have been changed to
org.apache.logging.log4j to avoid any conflicts with log4j 1.x.

For complete information on Apache Log4j 2, including instructions on how to 
submit bug reports,
patches, or suggestions for improvement, see the Apache Apache Log4j 2 website:

http://logging.apache.org/log4j/2.x/

[VOTE][RESULT] Log4j 2.6.1 rc1

2016-06-08 Thread Ralph Goers

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

2016-06-08 Thread Ralph Goers

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, release the artifacts
> [] -1, don't release because...
> 
> The vote will remain open for 72 hours (or more if required). All votes are 
> welcome and we encourage everyone to test the release, but only Logging PMC 
> votes are “officially” counted. As always, at least 3 +1 votes and more 
> positive than negative votes are required.
> 
> Changes in this version include:
> 
> New features:
> o LOG4J2-1411:  Add documentation about plugin builders compared to factories.
> 
> Fixed Bugs:
> o LOG4J2-1405:  OnStartupTriggeringPolicy was forcing a rollover of empty 
> files at startup and would append a
> second footer that was added by the prior shutdown.
> o LOG4J2-1406:  Fixed bug in ReusableParameterizedMessage where Throwable was 
> never updated so first error was logged over
> and over again and subsequent errors were not logged. Thanks to Trask 
> Stalnaker.
> o LOG4J2-1409:  Fixed ArrayIndexOutOfBoundsException that may occur in 
> ReusableParameterizedMessage. Thanks to Shahan.
> o LOG4J2-997:  Add filter and remove filter were not working properly in 
> AbstractFilterable. Thanks to Maytee Chinavanichkit.
> o LOG4J2-1032:  Change RenameAction to use java.nio to better report rename 
> failures.
> o LOG4J2-1407:  Misleading WARN log events from Log4j about message factories 
> and unexpected formatting. Thanks to Gary Gregory.
> o LOG4J2-1408:  The module log4j-liquibase is missing from BOM POM. Thanks to 
> Gary Gregory.
> o LOG4J2-1180:  Logger cache does not account for message factory. Thanks to 
> Gary Gregory.
> o LOG4J2-1402:  Fix regression in properties configuration to support 
> arbitrary component ids.
> 
> Changes:
> o LOG4J2-1385:  (GC) CSV layouts should not create a new CSVPrinter for each 
> log event. Requires Apache Commons CSV 1.4.
> o LOG4J2-1398:  Update liquibase-core from 3.4.2 to 3.5.1.
> o LOG4J2-1399:  Update Apache Commons CSV from 1.3 to 1.4.
> 
> Tag: 
> 
> a)  for a new copy do "git clone 
> https://git-wip-us.apache.org/repos/asf/logging-log4j2.git 
> <https://git-wip-us.apache.org/repos/asf/logging-log4j2.git>" and then "git 
> checkout tags/log4j-2.6.1-rc1”
> b) for an existing working copy to “git pull” and then “git checkout 
> tags/log4j-2.6.1-rc1”
> Web Site:  
> <http://rgoers.github.io/log4j2-site/index.html>http://rgoers.github.io/log4j2-site/index.html
>  <http://rgoers.github.io/log4j2-site/index.html>
> 
> Artifacts: 
> https://repository.apache.org/content/repositories/orgapachelogging-1019 
> <https://repository.apache.org/content/repositories/orgapachelogging-1017>
> You may download all the artifacts by executing:
> 
> wget -e robots=off --cut-dirs=7 -nH -r -p -np --no-check-certificate 
> https://repository.apache.org/content/repositories/orgapachelogging-1019/org/apache/logging/log4j/
>  
> <https://repository.apache.org/content/repositories/orgapachelogging-1019/org/apache/logging/log4j/>
> Ralph
>

AsyncAppenderQueueFullPolicyTest hung

2016-06-08 Thread Ralph Goers

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 not 
really sure what this test is trying to do but it appears to have some flawed 
logic somewhere.

Ralph

Full thread dump Java HotSpot(TM) 64-Bit Server VM (24.80-b11 mixed mode):

"Attach Listener" daemon prio=5 tid=0x7fc93b81b000 nid=0x3d0b waiting on 
condition [0x]
   java.lang.Thread.State: RUNNABLE

"AsyncAppender-Async" daemon prio=5 tid=0x7fc93c16c000 nid=0x5603 
sleeping[0x715d5000]
   java.lang.Thread.State: TIMED_WAITING (sleeping)
at java.lang.Thread.sleep(Native Method)
at 
org.apache.logging.log4j.test.appender.BlockingAppender.append(BlockingAppender.java:44)
at 
org.apache.logging.log4j.core.config.AppenderControl.tryCallAppender(AppenderControl.java:155)
at 
org.apache.logging.log4j.core.config.AppenderControl.callAppender0(AppenderControl.java:128)
at 
org.apache.logging.log4j.core.config.AppenderControl.callAppenderPreventRecursion(AppenderControl.java:119)
at 
org.apache.logging.log4j.core.config.AppenderControl.callAppender(AppenderControl.java:84)
at 
org.apache.logging.log4j.core.appender.AsyncAppender$AsyncThread.callAppenders(AsyncAppender.java:338)
at 
org.apache.logging.log4j.core.appender.AsyncAppender$AsyncThread.run(AsyncAppender.java:291)

"surefire-forkedjvm-command-thread" daemon prio=5 tid=0x7fc93c845800 
nid=0x5403 runnable [0x714d2000]
   java.lang.Thread.State: RUNNABLE
at java.io.FileInputStream.readBytes(Native Method)
at java.io.FileInputStream.read(FileInputStream.java:272)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:235)
at java.io.BufferedInputStream.read(BufferedInputStream.java:254)
- locked <0x0007aaa9ab70> (a java.io.BufferedInputStream)
at java.io.DataInputStream.readInt(DataInputStream.java:387)
at 
org.apache.maven.surefire.booter.MasterProcessCommand.decode(MasterProcessCommand.java:117)
at 
org.apache.maven.surefire.booter.CommandReader$CommandRunnable.run(CommandReader.java:360)
at java.lang.Thread.run(Thread.java:745)

"last-ditch-daemon-shutdown-thread-30sec" daemon prio=5 tid=0x7fc93c873800 
nid=0x5203 waiting on condition [0x713cf000]
   java.lang.Thread.State: TIMED_WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for  <0x0007aad7d750> (a 
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
at 
java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:226)
at 
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2082)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1090)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:807)
at 
java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1068)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)

"Service Thread" daemon prio=5 tid=0x7fc93c014800 nid=0x4e03 runnable 
[0x]
   java.lang.Thread.State: RUNNABLE

"C2 CompilerThread1" daemon prio=5 tid=0x7fc93c82d800 nid=0x4c03 waiting on 
condition [0x]
   java.lang.Thread.State: RUNNABLE

"C2 CompilerThread0" daemon prio=5 tid=0x7fc93b051800 nid=0x4a03 waiting on 
condition [0x]
   java.lang.Thread.State: RUNNABLE

"Signal Dispatcher" daemon prio=5 tid=0x7fc93b04c000 nid=0x3e0f runnable 
[0x]
   java.lang.Thread.State: RUNNABLE

"Finalizer" daemon prio=5 tid=0x7fc93c80 nid=0x3803 in Object.wait() 
[0x70d3a000]
   java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0x0007aaa84858> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:135)
- locked <0x0007aaa84858> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:151)
at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:209)

"Reference Handler" daemon prio=5 tid=0x7fc93c00e000 nid=0x3603 in 
Object.wait() [0x70c37000]
   java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0x0007aaa84470> (a java.lang.ref.Reference$Lock)
at

Re: No Git tag for 2.6!

2016-06-08 Thread Ralph Goers

The project-info-reports:scm goal accepts scmTag as a parameter so we should be 
able to configure that as 

log4j-${log4jReleaseVersion}

I’ll have to try it though to see if that is actually the goal that generates 
that page and to see if it breaks anything else.

Ralph

> On Jun 8, 2016, at 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 out. We would 
> have to investigate to see if there is some way to override that.
> 
> Ralph
> 
>> On Jun 8, 2016, at 11:04 AM, Gary Gregory <garydgreg...@gmail.com 
>> <mailto:garydgreg...@gmail.com>> wrote:
>> 
>> On Wed, Jun 8, 2016 at 7:17 AM, Matt Sicker <boa...@gmail.com 
>> <mailto:boa...@gmail.com>> wrote:
>> Well, the highest number RC would normally be the release, and we haven't 
>> skipped any releases, right?
>> 
>> But why bother with the guess work?
>> 
>> I'll create a tag for 2.6... ;-)
>> 
>> Gary
>>  
>> 
>> On 8 June 2016 at 00:28, Gary Gregory <garydgreg...@gmail.com 
>> <mailto:garydgreg...@gmail.com>> wrote:
>> We should. If 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 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 <garydgreg...@gmail.com 
>>> <mailto:garydgreg...@gmail.com>> wrote:
>>> 
>>> I was trying to compare sources while investigating a Clirr issue and I see 
>>> that there is no Git tag for 2.6. I take it 2.6 is the same as RC1, right?
>>> 
>>> Gary
>>> 
>>> -- 
>>> E-Mail: garydgreg...@gmail.com <mailto:garydgreg...@gmail.com> | 
>>> ggreg...@apache.org  <mailto:ggreg...@apache.org>
>>> Java Persistence with Hibernate, Second Edition 
>>> <http://www.manning.com/bauer3/>
>>> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
>>> Spring Batch in Action <http://www.manning.com/templier/>
>>> Blog: http://garygregory.wordpress.com <http://garygregory.wordpress.com/> 
>>> Home: http://garygregory.com/ <http://garygregory.com/>
>>> Tweet! http://twitter.com/GaryGregory <http://twitter.com/GaryGregory>
>> 
>> 
>> 
>> -- 
>> E-Mail: garydgreg...@gmail.com <mailto:garydgreg...@gmail.com> | 
>> ggreg...@apache.org  <mailto:ggreg...@apache.org>
>> Java Persistence with Hibernate, Second Edition 
>> <http://www.manning.com/bauer3/>
>> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
>> Spring Batch in Action <http://www.manning.com/templier/>
>> Blog: http://garygregory.wordpress.com <http://garygregory.wordpress.com/> 
>> Home: http://garygregory.com/ <http://garygregory.com/>
>> Tweet! http://twitter.com/GaryGregory <http://twitter.com/GaryGregory>
>> 
>> 
>> -- 
>> Matt Sicker <boa...@gmail.com <mailto:boa...@gmail.com>>
>> 
>> 
>> 
>> -- 
>> E-Mail: garydgreg...@gmail.com <mailto:garydgreg...@gmail.com> | 
>> ggreg...@apache.org  <mailto:ggreg...@apache.org>
>> Java Persistence with Hibernate, Second Edition 
>> <http://www.manning.com/bauer3/>
>> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
>> Spring Batch in Action <http://www.manning.com/templier/>
>> Blog: http://garygregory.wordpress.com <http://garygregory.wordpress.com/> 
>> Home: http://garygregory.com/ <http://garygregory.com/>
>> Tweet! http://twitter.com/GaryGregory <http://twitter.com/GaryGregory>

Re: No Git tag for 2.6!

2016-06-08 Thread Ralph Goers

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 investigate to see if there is some way to override that.

Ralph

> On Jun 8, 2016, at 11:04 AM, Gary Gregory <garydgreg...@gmail.com> wrote:
> 
> On Wed, Jun 8, 2016 at 7:17 AM, Matt Sicker <boa...@gmail.com 
> <mailto:boa...@gmail.com>> wrote:
> Well, the highest number RC would normally be the release, and we haven't 
> skipped any releases, right?
> 
> But why bother with the guess work?
> 
> I'll create a tag for 2.6... ;-)
> 
> Gary
>  
> 
> On 8 June 2016 at 00:28, Gary Gregory <garydgreg...@gmail.com 
> <mailto:garydgreg...@gmail.com>> wrote:
> We should. If 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 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 <garydgreg...@gmail.com 
>> <mailto:garydgreg...@gmail.com>> wrote:
>> 
>> I was trying to compare sources while investigating a Clirr issue and I see 
>> that there is no Git tag for 2.6. I take it 2.6 is the same as RC1, right?
>> 
>> Gary
>> 
>> -- 
>> E-Mail: garydgreg...@gmail.com <mailto:garydgreg...@gmail.com> | 
>> ggreg...@apache.org  <mailto:ggreg...@apache.org>
>> Java Persistence with Hibernate, Second Edition 
>> <http://www.manning.com/bauer3/>
>> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
>> Spring Batch in Action <http://www.manning.com/templier/>
>> Blog: http://garygregory.wordpress.com <http://garygregory.wordpress.com/> 
>> Home: http://garygregory.com/ <http://garygregory.com/>
>> Tweet! http://twitter.com/GaryGregory <http://twitter.com/GaryGregory>
> 
> 
> 
> -- 
> E-Mail: garydgreg...@gmail.com <mailto:garydgreg...@gmail.com> | 
> ggreg...@apache.org  <mailto:ggreg...@apache.org>
> Java Persistence with Hibernate, Second Edition 
> <http://www.manning.com/bauer3/>
> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
> Spring Batch in Action <http://www.manning.com/templier/>
> Blog: http://garygregory.wordpress.com <http://garygregory.wordpress.com/> 
> Home: http://garygregory.com/ <http://garygregory.com/>
> Tweet! http://twitter.com/GaryGregory <http://twitter.com/GaryGregory>
> 
> 
> -- 
> Matt Sicker <boa...@gmail.com <mailto:boa...@gmail.com>>
> 
> 
> 
> -- 
> E-Mail: garydgreg...@gmail.com <mailto:garydgreg...@gmail.com> | 
> ggreg...@apache.org  <mailto:ggreg...@apache.org>
> Java Persistence with Hibernate, Second Edition 
> <http://www.manning.com/bauer3/>
> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
> Spring Batch in Action <http://www.manning.com/templier/>
> Blog: http://garygregory.wordpress.com <http://garygregory.wordpress.com/> 
> Home: http://garygregory.com/ <http://garygregory.com/>
> Tweet! http://twitter.com/GaryGregory <http://twitter.com/GaryGregory>

Re: No Git tag for 2.6!

2016-06-07 Thread Ralph Goers

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 
> that there is no Git tag for 2.6. I take it 2.6 is the same as RC1, right?
> 
> Gary
> 
> -- 
> E-Mail: garydgreg...@gmail.com  | 
> ggreg...@apache.org  
> Java Persistence with Hibernate, Second Edition 
> 
> JUnit in Action, Second Edition 
> Spring Batch in Action 
> Blog: http://garygregory.wordpress.com  
> Home: http://garygregory.com/ 
> Tweet! http://twitter.com/GaryGregory

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

2016-06-06 Thread Ralph Goers (JIRA)


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

> Multiple footers written to file on system restart
> --
>
> Key: LOG4J2-1228
> URL: https://issues.apache.org/jira/browse/LOG4J2-1228
> Project: Log4j 2
>  Issue Type: Bug
>  Components: Layouts
>Reporter: Steve Davids
>    Assignee: Ralph Goers
> Attachments: LOG4J2-1228-test.diff
>
>
> I created a custom layout that appends a header and footer to a rolling file 
> appender with a time based and startup trigger policies which works great 
> during normal circumstances except when it comes to system restarts. On 
> shutdown the file is closed with the footer being written to the file, then 
> on startup the startup trigger policy will open the file then immediately 
> roll thus printing the footer again on rollover (prior to v2.4 the header was 
> also written on startup LOG4J2-1030). I am attempting to produce well-formed 
> XML with this particular use-case but it is getting mangled at this 
> particular point. Ideally we can either have the footer either not print the 
> second time or just perform the rollover on shutdown.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

Re: [VOTE] Log4j 2.6.1 rc1

2016-06-06 Thread Ralph Goers

Sorry, I usually cut and paste the prior release email. That link was for the 
prior release. Just change the 17 to 19 in the browser.

Ralph

> On Jun 6, 2016, at 11:43 AM, Matt Sicker <boa...@gmail.com> wrote:
> 
> Just FYI, the artifacts link is hyperlinked wrong. You have 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 
> <mailto: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, release the artifacts
> [] -1, don't release because...
> 
> The vote will remain open for 72 hours (or more if required). All votes are 
> welcome and we encourage everyone to test the release, but only Logging PMC 
> votes are “officially” counted. As always, at least 3 +1 votes and more 
> positive than negative votes are required.
> 
> Changes in this version include:
> 
> New features:
> o LOG4J2-1411:  Add documentation about plugin builders compared to factories.
> 
> Fixed Bugs:
> o LOG4J2-1405:  OnStartupTriggeringPolicy was forcing a rollover of empty 
> files at startup and would append a
> second footer that was added by the prior shutdown.
> o LOG4J2-1406:  Fixed bug in ReusableParameterizedMessage where Throwable was 
> never updated so first error was logged over
> and over again and subsequent errors were not logged. Thanks to Trask 
> Stalnaker.
> o LOG4J2-1409:  Fixed ArrayIndexOutOfBoundsException that may occur in 
> ReusableParameterizedMessage. Thanks to Shahan.
> o LOG4J2-997:  Add filter and remove filter were not working properly in 
> AbstractFilterable. Thanks to Maytee Chinavanichkit.
> o LOG4J2-1032:  Change RenameAction to use java.nio to better report rename 
> failures.
> o LOG4J2-1407:  Misleading WARN log events from Log4j about message factories 
> and unexpected formatting. Thanks to Gary Gregory.
> o LOG4J2-1408:  The module log4j-liquibase is missing from BOM POM. Thanks to 
> Gary Gregory.
> o LOG4J2-1180:  Logger cache does not account for message factory. Thanks to 
> Gary Gregory.
> o LOG4J2-1402:  Fix regression in properties configuration to support 
> arbitrary component ids.
> 
> Changes:
> o LOG4J2-1385:  (GC) CSV layouts should not create a new CSVPrinter for each 
> log event. Requires Apache Commons CSV 1.4.
> o LOG4J2-1398:  Update liquibase-core from 3.4.2 to 3.5.1.
> o LOG4J2-1399:  Update Apache Commons CSV from 1.3 to 1.4.
> 
> Tag: 
> 
> a)  for a new copy do "git clone 
> https://git-wip-us.apache.org/repos/asf/logging-log4j2.git 
> <https://git-wip-us.apache.org/repos/asf/logging-log4j2.git>" and then "git 
> checkout tags/log4j-2.6.1-rc1”
> b) for an existing working copy to “git pull” and then “git checkout 
> tags/log4j-2.6.1-rc1”
> Web Site:  
> <http://rgoers.github.io/log4j2-site/index.html>http://rgoers.github.io/log4j2-site/index.html
>  <http://rgoers.github.io/log4j2-site/index.html>
> 
> Artifacts: 
> https://repository.apache.org/content/repositories/orgapachelogging-1019 
> <https://repository.apache.org/content/repositories/orgapachelogging-1017>
> You may download all the artifacts by executing:
> 
> wget -e robots=off --cut-dirs=7 -nH -r -p -np --no-check-certificate 
> https://repository.apache.org/content/repositories/orgapachelogging-1019/org/apache/logging/log4j/
>  
> <https://repository.apache.org/content/repositories/orgapachelogging-1019/org/apache/logging/log4j/>
> Ralph
> 
> 
> 
> 
> 
> -- 
> Matt Sicker <boa...@gmail.com <mailto:boa...@gmail.com>>

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

2016-06-06 Thread Ralph Goers

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.apache.org
> For additional commands, e-mail: log4j-dev-h...@logging.apache.org
> 
> 



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

Re: 2.6.1 web site

2016-06-05 Thread Ralph Goers

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 Goers <ralph.go...@dslextreme.com> wrote:
>> 
>> 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 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
>>> 
>>> -
>>> To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
>>> For additional commands, e-mail: log4j-dev-h...@logging.apache.org
>>> 
>>> 
>> 
> 
> 
> 
> -
> To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
> For additional commands, e-mail: log4j-dev-h...@logging.apache.org
> 
> 



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

Re: 2.6.1 web site

2016-06-05 Thread Ralph Goers

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 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 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 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
>>> 
>>> -
>>> To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
>>> For additional commands, e-mail: log4j-dev-h...@logging.apache.org
>>> 
>>> 
>> 
> 



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

Re: 2.6.1 web site

2016-06-05 Thread Ralph Goers


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 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 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
>> 
>> -
>> To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
>> For additional commands, e-mail: log4j-dev-h...@logging.apache.org
>> 
>> 
> 



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

Re: 2.6.1 web site

2016-06-05 Thread Ralph Goers

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 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
> 
> -
> To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
> For additional commands, e-mail: log4j-dev-h...@logging.apache.org
> 
> 



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

2.6.1 web site

2016-06-05 Thread Ralph Goers

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

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

[VOTE] Log4j 2.6.1 rc1

2016-06-05 Thread Ralph Goers

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
welcome and we encourage everyone to test the release, but only Logging PMC
votes are “officially” counted. As always, at least 3 +1 votes and more
positive than negative votes are required.

Changes in this version include:

New features:
o LOG4J2-1411: Add documentation about plugin builders compared to factories.

Fixed Bugs:
o LOG4J2-1405: OnStartupTriggeringPolicy was forcing a rollover of empty files
at startup and would append a
second footer that was added by the prior shutdown.
o LOG4J2-1406: Fixed bug in ReusableParameterizedMessage where Throwable was
never updated so first error was logged over
and over again and subsequent errors were not logged. Thanks to Trask
Stalnaker.
o LOG4J2-1409: Fixed ArrayIndexOutOfBoundsException that may occur in
ReusableParameterizedMessage. Thanks to Shahan.
o LOG4J2-997: Add filter and remove filter were not working properly in
AbstractFilterable. Thanks to Maytee Chinavanichkit.
o LOG4J2-1032: Change RenameAction to use java.nio to better report rename
failures.
o LOG4J2-1407: Misleading WARN log events from Log4j about message factories
and unexpected formatting. Thanks to Gary Gregory.
o LOG4J2-1408: The module log4j-liquibase is missing from BOM POM. Thanks to
Gary Gregory.
o LOG4J2-1180: Logger cache does not account for message factory. Thanks to
Gary Gregory.
o LOG4J2-1402: Fix regression in properties configuration to support arbitrary
component ids.

Changes:
o LOG4J2-1385: (GC) CSV layouts should not create a new CSVPrinter for each
log event. Requires Apache Commons CSV 1.4.
o LOG4J2-1398: Update liquibase-core from 3.4.2 to 3.5.1.
o LOG4J2-1399: Update Apache Commons CSV from 1.3 to 1.4.

Tag:

a) for a new copy do "git clone
https://git-wip-us.apache.org/repos/asf/logging-log4j2.git
" and then "git
checkout tags/log4j-2.6.1-rc1”
b) for an existing working copy to “git pull” and then “git checkout
tags/log4j-2.6.1-rc1”
Web Site:
http://rgoers.github.io/log4j2-site/index.html

Artifacts:
https://repository.apache.org/content/repositories/orgapachelogging-1019

You may download all the artifacts by executing:

wget -e robots=off --cut-dirs=7 -nH -r -p -np --no-check-certificate
https://repository.apache.org/content/repositories/orgapachelogging-1019/org/apache/logging/log4j/

Ralph

Re: MessageFactory2 missing @since tag

2016-06-05 Thread Ralph Goers

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  > wrote:
> 
>> The type MessageFactory2 is missing its @since tag. When was this added?
>> 
>> Gary
>> 
>> -- 
>> E-Mail: garydgreg...@gmail.com  | 
>> ggreg...@apache.org  
>> Java Persistence with Hibernate, Second Edition 
>> 
>> JUnit in Action, Second Edition 
>> Spring Batch in Action 
>> Blog: http://garygregory.wordpress.com  
>> Home: http://garygregory.com/ 
>> Tweet! http://twitter.com/GaryGregory 
> 
> 
> -- 
> E-Mail: garydgreg...@gmail.com  | 
> ggreg...@apache.org  
> Java Persistence with Hibernate, Second Edition 
> 
> JUnit in Action, Second Edition 
> Spring Batch in Action 
> Blog: http://garygregory.wordpress.com  
> Home: http://garygregory.com/ 
> Tweet! http://twitter.com/GaryGregory

Re: Log4j 2.6.1

2016-06-05 Thread Ralph Goers

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 Gregory <garydgreg...@gmail.com 
> <mailto:garydgreg...@gmail.com>> 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" <ralph.go...@dslextreme.com 
>> <mailto:ralph.go...@dslextreme.com>> wrote:
>> I created the fix and tested it. The test works when I run it standalone but 
>> fails when I run all tests. I am not sure why. One way or another I plan to 
>> create the release today.
>> 
>> Ralph
>> 
>> On Jun 5, 2016, at 4:23 AM, Remko Popma <remko.po...@gmail.com 
>> <mailto:remko.po...@gmail.com>> wrote:
>> 
>>> Is the footer being written twice in LOG4J2-1405 
>>> <https://issues.apache.org/jira/browse/LOG4J2-1405> a showstopper for 2.6.1?
>>> If this is an easy fix I'd say go for it, but otherwise perhaps it makes 
>>> sense to release what's in master now.
>>> 
>>> Especially LOG4J2-1409 <https://issues.apache.org/jira/browse/LOG4J2-1409> 
>>> (the ArrayIndexOutOfBoundsException) 
>>> and LOG4J2-1406 <https://issues.apache.org/jira/browse/LOG4J2-1406> 
>>> (getting stuck on 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 
>>> <mailto:ralph.go...@dslextreme.com>> wrote:
>>> Actually, nevermind.  I know how to do it.
>>> 
>>> Ralph
>>> 
>>>> On Jun 3, 2016, at 1:32 PM, Gary Gregory <garydgreg...@gmail.com 
>>>> <mailto: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.go...@dslextreme.com 
>>>> <mailto:ralph.go...@dslextreme.com>> wrote:
>>>> A png.
>>>> 
>>>> Ralph
>>>> 
>>>>> On Jun 3, 2016, at 12:11 PM, Gary Gregory <garydgreg...@gmail.com 
>>>>> <mailto: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 do that before I generate the 
>>>>> site.
>>>>> 
>>>>> I'm sorry one of what?
>>>>> 
>>>>> Gary
>>>>>  
>>>>> 
>>>>> Ralph
>>>>> 
>>>>>> On Jun 3, 2016, at 11:11 AM, Gary Gregory <garydgreg...@gmail.com 
>>>>>> <mailto:garydgreg...@gmail.com>> wrote:
>>>>>> 
>>>>>> On Fri, Jun 3, 2016 at 10:51 AM, Gary Gregory <garydgreg...@gmail.com 
>>>>>> <mailto:garydgreg...@gmail.com>> 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.
>>>>>> 
>>>>>> See /log4j-parent/src/site/resources/logo/logo-lightning-2.6.1.png
>>>>>> 
>>>>>> You should switch the site to use a png instead of a jpeg IMO.
>>>>>> 
>>>>>> Gary
>>>>>>  
>>>>>> 
>>>>>> G 
>>>>>> 
>>>>>> Ralph
>>>>>> 
>>>>>>> On Jun 3, 2016, at 10:16 AM, Ralph Goers <ralph.go...@dslextreme.com 
>>>>>>> <mailto:ralph.go...@dslextreme.com>> wrote:
>>>>>>> 
>>>>>>> Thanks Remko. Just remember that “tonight” or “tomorrow morning” 
>>>>>>> translates into 12-24 hrs from now.  So if you have more you want to do 
>>>>>>> when you get up you have some time.
>>>>>>> 
&g

Re: Log4j 2.6.1

2016-06-05 Thread Ralph Goers

I created the fix and tested it. The test works when I run it standalone but 
fails when I run all tests. I am not sure why. One way or another I plan to 
create the release today.

Ralph

> On Jun 5, 2016, at 4:23 AM, Remko Popma <remko.po...@gmail.com> wrote:
> 
> Is the footer being written twice in LOG4J2-1405 a showstopper for 2.6.1?
> If this is an easy fix I'd say go for it, but otherwise perhaps it makes 
> sense to release what's in master now.
> 
> Especially LOG4J2-1409 (the ArrayIndexOutOfBoundsException) 
> and LOG4J2-1406 (getting stuck on 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.
>> 
>> 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.go...@dslextreme.com> wrote:
>>>> 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> wrote:
>>>>>> Do we have one of the standard logo? I can do that before I generate the 
>>>>>> site.
>>>>> 
>>>>> I'm sorry one of what?
>>>>> 
>>>>> Gary
>>>>>  
>>>>>> 
>>>>>> Ralph
>>>>>> 
>>>>>>> On Jun 3, 2016, at 11:11 AM, Gary Gregory <garydgreg...@gmail.com> 
>>>>>>> wrote:
>>>>>>> 
>>>>>>>> On Fri, Jun 3, 2016 at 10:51 AM, Gary Gregory <garydgreg...@gmail.com> 
>>>>>>>> wrote:
>>>>>>>>> On Fri, Jun 3, 2016 at 10:21 AM, Ralph Goers 
>>>>>>>>> <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.
>>>>>>> 
>>>>>>> See /log4j-parent/src/site/resources/logo/logo-lightning-2.6.1.png
>>>>>>> 
>>>>>>> You should switch the site to use a png instead of a jpeg IMO.
>>>>>>> 
>>>>>>> Gary
>>>>>>>  
>>>>>>>> 
>>>>>>>> G 
>>>>>>>>> 
>>>>>>>>> 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 12-24 hrs from now.  So if you have more you want to 
>>>>>>>>>> do when you get up you have some time.
>>>>>>>>>> 
>>>>>>>>>> Ralph
>>>>>>>>>> 
>>>>>>>>>>> On Jun 3, 2016, at 10:03 AM, Remko Popma <remko.po...@gmail.com> 
>>>>>>>>>>> wrote:
>>>>>>>>>>> 
>>>>>>>>>>> I fixed two critical issues introduced by 2.6.
>>>>>>>>>>> It would be great if Matt can take a look at LOG4J2-1394 (I did a 
>>>>>>>>>>> bit but there's still quite a few remaining).
>>>>>>>>>>> 
>>>>>>>>>>> Not sure if LOG4J2-1405 was introduced by 2.6 since the user 
>>>>>>>>>>> upgraded 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
>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>

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

2016-06-04 Thread Ralph Goers (JIRA)


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

> 2.6 html format - "" inserted in the middle of  
> when restart tomcat
> -
>
> Key: LOG4J2-1405
> URL: https://issues.apache.org/jira/browse/LOG4J2-1405
> Project: Log4j 2
>  Issue Type: Bug
>Affects Versions: 2.6
>Reporter: yl
> Attachments: debug.html
>
>
> Hello,
> Updated 2.3 to 2.6. When reload tomcat7, the logfile (html format) not shown 
> correctly:
> {code}
> 
> 13942164
> http-bio-.
> INFO
> ActionClass
> ..
> 
> 
> 
> 
> 
> 13936096
> http-bio.50
> WARN
> .
>  
> 
> {code}
> "" is added in the middle, so html file cannot be 
> printed correctly.
> Can someone help how to fix this please?
> Here is log4j2.xml config:
> {code}
> fileName="@log4j.debug.html@"
>   filePattern="@log4j.debug.html@-%i.html">
> 
> 
>
> 
>  
>   
>  
>   
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

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

2016-06-04 Thread Ralph Goers (JIRA)


[ 
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 believe that when 
the Appender starts it opens the output stream - the writeHeader flag isn't 
true so no header is written, then the rollover occurs which will close the 
stream and write a footer (which we don't want). Then the new file is opened.

But I need to run a test and see if it actually works this way or if we roll 
before the file is even opened.

> 2.6 html format - "" inserted in the middle of  
> when restart tomcat
> -
>
> Key: LOG4J2-1405
> URL: https://issues.apache.org/jira/browse/LOG4J2-1405
> Project: Log4j 2
>  Issue Type: Bug
>Affects Versions: 2.6
>Reporter: yl
> Attachments: debug.html
>
>
> Hello,
> Updated 2.3 to 2.6. When reload tomcat7, the logfile (html format) not shown 
> correctly:
> {code}
> 
> 13942164
> http-bio-.
> INFO
> ActionClass
> ..
> 
> 
> 
> 
> 
> 13936096
> http-bio.50
> WARN
> .
>  
> 
> {code}
> "" is added in the middle, so html file cannot be 
> printed correctly.
> Can someone help how to fix this please?
> Here is log4j2.xml config:
> {code}
> fileName="@log4j.debug.html@"
>   filePattern="@log4j.debug.html@-%i.html">
> 
> 
>
> 
>  
>   
>  
>   
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

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

2016-06-04 Thread Ralph Goers (JIRA)


[ 
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 then RollingFileManager 
is created with the writeHeader flag set to false as a log file should never 
have more than one header. But since the file didn't roll over more log events 
are just going to be appended to the file.

However, we will need to check if the footer will be written again when 
OnStartupTriggeringPolicy runs.

> 2.6 html format - "" inserted in the middle of  
> when restart tomcat
> -
>
> Key: LOG4J2-1405
> URL: https://issues.apache.org/jira/browse/LOG4J2-1405
> Project: Log4j 2
>  Issue Type: Bug
>Affects Versions: 2.6
>Reporter: yl
> Attachments: debug.html
>
>
> Hello,
> Updated 2.3 to 2.6. When reload tomcat7, the logfile (html format) not shown 
> correctly:
> {code}
> 
> 13942164
> http-bio-.
> INFO
> ActionClass
> ..
> 
> 
> 
> 
> 
> 13936096
> http-bio.50
> WARN
> .
>  
> 
> {code}
> "" is added in the middle, so html file cannot be 
> printed correctly.
> Can someone help how to fix this please?
> Here is log4j2.xml config:
> {code}
> fileName="@log4j.debug.html@"
>   filePattern="@log4j.debug.html@-%i.html">
> 
> 
>
> 
>  
>   
>  
>   
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

Re: Log4j 2.6.1

2016-06-03 Thread Ralph Goers

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.go...@dslextreme.com 
> <mailto:ralph.go...@dslextreme.com>> wrote:
> A png.
> 
> Ralph
> 
>> On Jun 3, 2016, at 12:11 PM, Gary Gregory <garydgreg...@gmail.com 
>> <mailto: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 do that before I generate the 
>> site.
>> 
>> I'm sorry one of what?
>> 
>> Gary
>>  
>> 
>> Ralph
>> 
>>> On Jun 3, 2016, at 11:11 AM, Gary Gregory <garydgreg...@gmail.com 
>>> <mailto:garydgreg...@gmail.com>> wrote:
>>> 
>>> On Fri, Jun 3, 2016 at 10:51 AM, Gary Gregory <garydgreg...@gmail.com 
>>> <mailto:garydgreg...@gmail.com>> 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.
>>> 
>>> See /log4j-parent/src/site/resources/logo/logo-lightning-2.6.1.png
>>> 
>>> You should switch the site to use a png instead of a jpeg IMO.
>>> 
>>> Gary
>>>  
>>> 
>>> G 
>>> 
>>> Ralph
>>> 
>>>> On Jun 3, 2016, at 10:16 AM, Ralph Goers <ralph.go...@dslextreme.com 
>>>> <mailto:ralph.go...@dslextreme.com>> wrote:
>>>> 
>>>> Thanks Remko. Just remember that “tonight” or “tomorrow morning” 
>>>> translates into 12-24 hrs from now.  So if you have more you want to do 
>>>> when you get up you have some time.
>>>> 
>>>> Ralph
>>>> 
>>>>> On Jun 3, 2016, at 10:03 AM, Remko Popma <remko.po...@gmail.com 
>>>>> <mailto:remko.po...@gmail.com>> wrote:
>>>>> 
>>>>> I fixed two critical issues introduced by 2.6.
>>>>> It would be great if Matt can take a look at LOG4J2-1394 (I did a bit but 
>>>>> there's still quite a few remaining).
>>>>> 
>>>>> Not sure if LOG4J2-1405 
>>>>> <https://issues.apache.org/jira/browse/LOG4J2-1405> was introduced by 2.6 
>>>>> since the user upgraded 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:
>>>>> On Fri, Jun 3, 2016 at 8:57 AM, Ralph Goers <ralph.go...@dslextreme.com 
>>>>> <mailto:ralph.go...@dslextreme.com>> wrote:
>>>>> Are there any other fixes that have to go in?  I am thinking I will start 
>>>>> the release tonight or tomorrow morning.
>>>>> 
>>>>> Good to go from my POV.
>>>>> 
>>>>> Gary
>>>>>  
>>>>> 
>>>>> Ralph
>>>>> 
>>>>> > On Jun 1, 2016, at 2:57 PM, Ralph Goers <ralph.go...@dslextreme.com 
>>>>> > <mailto:ralph.go...@dslextreme.com>> wrote:
>>>>> >
>>>>> > 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 the only real fix for Windows.  However, I don’t 
>>>>> > want to do that in a point release.
>>>>> >
>>>>> > LOG4J2-1180 was updated today and it seems the support for having 
>>>>> > Loggers stored by their message factory is not working correctly. Gary 
>>>>> > apparently is also experiencing this problem.
>>>>> >
>>>>> > I woul

Re: Log4j 2.6.1

2016-06-03 Thread Ralph Goers

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 do that before I generate the site.
> 
> I'm sorry one of what?
> 
> Gary
>  
> 
> Ralph
> 
>> On Jun 3, 2016, at 11:11 AM, Gary Gregory <garydgreg...@gmail.com 
>> <mailto:garydgreg...@gmail.com>> wrote:
>> 
>> On Fri, Jun 3, 2016 at 10:51 AM, Gary Gregory <garydgreg...@gmail.com 
>> <mailto:garydgreg...@gmail.com>> 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.
>> 
>> See /log4j-parent/src/site/resources/logo/logo-lightning-2.6.1.png
>> 
>> You should switch the site to use a png instead of a jpeg IMO.
>> 
>> Gary
>>  
>> 
>> G 
>> 
>> Ralph
>> 
>>> On Jun 3, 2016, at 10:16 AM, Ralph Goers <ralph.go...@dslextreme.com 
>>> <mailto:ralph.go...@dslextreme.com>> wrote:
>>> 
>>> Thanks Remko. Just remember that “tonight” or “tomorrow morning” translates 
>>> into 12-24 hrs from now.  So if you have more you want to do when you get 
>>> up you have some time.
>>> 
>>> Ralph
>>> 
>>>> On Jun 3, 2016, at 10:03 AM, Remko Popma <remko.po...@gmail.com 
>>>> <mailto:remko.po...@gmail.com>> wrote:
>>>> 
>>>> I fixed two critical issues introduced by 2.6.
>>>> It would be great if Matt can take a look at LOG4J2-1394 (I did a bit but 
>>>> there's still quite a few remaining).
>>>> 
>>>> Not sure if LOG4J2-1405 
>>>> <https://issues.apache.org/jira/browse/LOG4J2-1405> was introduced by 2.6 
>>>> since the user upgraded 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:
>>>> On Fri, Jun 3, 2016 at 8:57 AM, Ralph Goers <ralph.go...@dslextreme.com 
>>>> <mailto:ralph.go...@dslextreme.com>> wrote:
>>>> Are there any other fixes that have to go in?  I am thinking I will start 
>>>> the release tonight or tomorrow morning.
>>>> 
>>>> Good to go from my POV.
>>>> 
>>>> Gary
>>>>  
>>>> 
>>>> Ralph
>>>> 
>>>> > On Jun 1, 2016, at 2:57 PM, Ralph Goers <ralph.go...@dslextreme.com 
>>>> > <mailto:ralph.go...@dslextreme.com>> wrote:
>>>> >
>>>> > 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 the only real fix for Windows.  However, I don’t want to 
>>>> > do that in a point release.
>>>> >
>>>> > LOG4J2-1180 was updated today and it seems the support for having 
>>>> > Loggers stored by their message factory is not working correctly. Gary 
>>>> > apparently is also experiencing this problem.
>>>> >
>>>> > I would like to see if we can fix these three items this week and do 
>>>> > another release this weekend.  If there are any other bugs that can be 
>>>> > addressed by then I’m ok with that.
>>>> >
>>>> > Thoughts?
>>>> >
>>>> > Ralph
>>>> >
>>>> > -
>>>> > To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org 
>>>> > <mailto:log4j-dev-unsubscr...@logging.apache.org>
>>>> > For additional commands, e-mail: log4j-dev-h...@logging.apache.org 
>>>> > <mailto:log4j-dev-h...@logging.apache.org>
>>>> >
>>>> >
>

Re: Log4j 2.6.1

2016-06-03 Thread Ralph Goers

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 <garydgreg...@gmail.com> wrote:
> 
> On Fri, Jun 3, 2016 at 10:51 AM, Gary Gregory <garydgreg...@gmail.com 
> <mailto:garydgreg...@gmail.com>> 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.
> 
> See /log4j-parent/src/site/resources/logo/logo-lightning-2.6.1.png
> 
> You should switch the site to use a png instead of a jpeg IMO.
> 
> Gary
>  
> 
> G 
> 
> Ralph
> 
>> On Jun 3, 2016, at 10:16 AM, Ralph Goers <ralph.go...@dslextreme.com 
>> <mailto:ralph.go...@dslextreme.com>> wrote:
>> 
>> Thanks Remko. Just remember that “tonight” or “tomorrow morning” translates 
>> into 12-24 hrs from now.  So if you have more you want to do when you get up 
>> you have some time.
>> 
>> Ralph
>> 
>>> On Jun 3, 2016, at 10:03 AM, Remko Popma <remko.po...@gmail.com 
>>> <mailto:remko.po...@gmail.com>> wrote:
>>> 
>>> I fixed two critical issues introduced by 2.6.
>>> It would be great if Matt can take a look at LOG4J2-1394 (I did a bit but 
>>> there's still quite a few remaining).
>>> 
>>> Not sure if LOG4J2-1405 <https://issues.apache.org/jira/browse/LOG4J2-1405> 
>>> was introduced by 2.6 since the user upgraded 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:
>>> On Fri, Jun 3, 2016 at 8:57 AM, Ralph Goers <ralph.go...@dslextreme.com 
>>> <mailto:ralph.go...@dslextreme.com>> wrote:
>>> Are there any other fixes that have to go in?  I am thinking I will start 
>>> the release tonight or tomorrow morning.
>>> 
>>> Good to go from my POV.
>>> 
>>> Gary
>>>  
>>> 
>>> Ralph
>>> 
>>> > On Jun 1, 2016, at 2:57 PM, Ralph Goers <ralph.go...@dslextreme.com 
>>> > <mailto:ralph.go...@dslextreme.com>> wrote:
>>> >
>>> > 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 the only real fix for Windows.  However, I don’t want to do 
>>> > that in a point release.
>>> >
>>> > LOG4J2-1180 was updated today and it seems the support for having Loggers 
>>> > stored by their message factory is not working correctly. Gary apparently 
>>> > is also experiencing this problem.
>>> >
>>> > I would like to see if we can fix these three items this week and do 
>>> > another release this weekend.  If there are any other bugs that can be 
>>> > addressed by then I’m ok with that.
>>> >
>>> > Thoughts?
>>> >
>>> > Ralph
>>> >
>>> > -
>>> > To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org 
>>> > <mailto:log4j-dev-unsubscr...@logging.apache.org>
>>> > For additional commands, e-mail: log4j-dev-h...@logging.apache.org 
>>> > <mailto:log4j-dev-h...@logging.apache.org>
>>> >
>>> >
>>> 
>>> 
>>> 
>>> -
>>> To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org 
>>> <mailto:log4j-dev-unsubscr...@logging.apache.org>
>>> For additional commands, e-mail: log4j-dev-h...@logging.apache.org 
>>> <mailto:log4j-dev-h...@logging.apache.org>
>>> 
>>> 
>>> 
>>> 
>>> -- 
>>> E-Mail: garydgreg...@gmail.com <mailto:garydgreg...@gmail.com> | 
>>> ggreg...@apache.org  <mailto:ggreg...@apache.org>
>>> Java Persistence with Hibernate, Second Edition 
>>> <http://www.manning.com/bauer3/>
&

Re: Log4j 2.6.1

2016-06-03 Thread Ralph Goers

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 12-24 hrs from now.  So if you have more you want to do when you get up 
> you have some time.
> 
> Ralph
> 
>> On Jun 3, 2016, at 10:03 AM, Remko Popma <remko.po...@gmail.com 
>> <mailto:remko.po...@gmail.com>> wrote:
>> 
>> I fixed two critical issues introduced by 2.6.
>> It would be great if Matt can take a look at LOG4J2-1394 (I did a bit but 
>> there's still quite a few remaining).
>> 
>> Not sure if LOG4J2-1405 <https://issues.apache.org/jira/browse/LOG4J2-1405> 
>> was introduced by 2.6 since the user upgraded 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:
>> On Fri, Jun 3, 2016 at 8:57 AM, Ralph Goers <ralph.go...@dslextreme.com 
>> <mailto:ralph.go...@dslextreme.com>> wrote:
>> Are there any other fixes that have to go in?  I am thinking I will start 
>> the release tonight or tomorrow morning.
>> 
>> Good to go from my POV.
>> 
>> Gary
>>  
>> 
>> Ralph
>> 
>> > On Jun 1, 2016, at 2:57 PM, Ralph Goers <ralph.go...@dslextreme.com 
>> > <mailto:ralph.go...@dslextreme.com>> wrote:
>> >
>> > 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 the only real fix for Windows.  However, I don’t want to do 
>> > that in a point release.
>> >
>> > LOG4J2-1180 was updated today and it seems the support for having Loggers 
>> > stored by their message factory is not working correctly. Gary apparently 
>> > is also experiencing this problem.
>> >
>> > I would like to see if we can fix these three items this week and do 
>> > another release this weekend.  If there are any other bugs that can be 
>> > addressed by then I’m ok with that.
>> >
>> > Thoughts?
>> >
>> > Ralph
>> >
>> > -
>> > To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org 
>> > <mailto:log4j-dev-unsubscr...@logging.apache.org>
>> > For additional commands, e-mail: log4j-dev-h...@logging.apache.org 
>> > <mailto:log4j-dev-h...@logging.apache.org>
>> >
>> >
>> 
>> 
>> 
>> -
>> To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org 
>> <mailto:log4j-dev-unsubscr...@logging.apache.org>
>> For additional commands, e-mail: log4j-dev-h...@logging.apache.org 
>> <mailto:log4j-dev-h...@logging.apache.org>
>> 
>> 
>> 
>> 
>> -- 
>> E-Mail: garydgreg...@gmail.com <mailto:garydgreg...@gmail.com> | 
>> ggreg...@apache.org  <mailto:ggreg...@apache.org>
>> Java Persistence with Hibernate, Second Edition 
>> <http://www.manning.com/bauer3/>
>> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
>> Spring Batch in Action <http://www.manning.com/templier/>
>> Blog: http://garygregory.wordpress.com <http://garygregory.wordpress.com/> 
>> Home: http://garygregory.com/ <http://garygregory.com/>
>> Tweet! http://twitter.com/GaryGregory <http://twitter.com/GaryGregory>
>

Re: Log4j 2.6.1

2016-06-03 Thread Ralph Goers

Thanks Remko. Just remember that “tonight” or “tomorrow morning” translates 
into 12-24 hrs from now.  So if you have more you want to do when you get up 
you have some time.

Ralph

> On Jun 3, 2016, at 10:03 AM, Remko Popma <remko.po...@gmail.com> wrote:
> 
> I fixed two critical issues introduced by 2.6.
> It would be great if Matt can take a look at LOG4J2-1394 (I did a bit but 
> there's still quite a few remaining).
> 
> Not sure if LOG4J2-1405 <https://issues.apache.org/jira/browse/LOG4J2-1405> 
> was introduced by 2.6 since the user upgraded 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:
> On Fri, Jun 3, 2016 at 8:57 AM, Ralph Goers <ralph.go...@dslextreme.com 
> <mailto:ralph.go...@dslextreme.com>> wrote:
> Are there any other fixes that have to go in?  I am thinking I will start the 
> release tonight or tomorrow morning.
> 
> Good to go from my POV.
> 
> Gary
>  
> 
> Ralph
> 
> > On Jun 1, 2016, at 2:57 PM, Ralph Goers <ralph.go...@dslextreme.com 
> > <mailto:ralph.go...@dslextreme.com>> wrote:
> >
> > 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 the 
> > only real fix for Windows.  However, I don’t want to do that in a point 
> > release.
> >
> > LOG4J2-1180 was updated today and it seems the support for having Loggers 
> > stored by their message factory is not working correctly. Gary apparently 
> > is also experiencing this problem.
> >
> > I would like to see if we can fix these three items this week and do 
> > another release this weekend.  If there are any other bugs that can be 
> > addressed by then I’m ok with that.
> >
> > Thoughts?
> >
> > Ralph
> >
> > -
> > To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org 
> > <mailto:log4j-dev-unsubscr...@logging.apache.org>
> > For additional commands, e-mail: log4j-dev-h...@logging.apache.org 
> > <mailto:log4j-dev-h...@logging.apache.org>
> >
> >
> 
> 
> 
> -
> To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org 
> <mailto:log4j-dev-unsubscr...@logging.apache.org>
> For additional commands, e-mail: log4j-dev-h...@logging.apache.org 
> <mailto:log4j-dev-h...@logging.apache.org>
> 
> 
> 
> 
> -- 
> E-Mail: garydgreg...@gmail.com <mailto:garydgreg...@gmail.com> | 
> ggreg...@apache.org  <mailto:ggreg...@apache.org>
> Java Persistence with Hibernate, Second Edition 
> <http://www.manning.com/bauer3/>
> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
> Spring Batch in Action <http://www.manning.com/templier/>
> Blog: http://garygregory.wordpress.com <http://garygregory.wordpress.com/> 
> Home: http://garygregory.com/ <http://garygregory.com/>
> Tweet! http://twitter.com/GaryGregory <http://twitter.com/GaryGregory>

Re: Log4j 2.6.1

2016-06-03 Thread Ralph Goers

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 
> 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 the 
> only real fix for Windows.  However, I don’t want to do that in a point 
> release.
> 
> LOG4J2-1180 was updated today and it seems the support for having Loggers 
> stored by their message factory is not working correctly. Gary apparently is 
> also experiencing this problem.
> 
> I would like to see if we can fix these three items this week and do another 
> release this weekend.  If there are any other bugs that can be addressed by 
> then I’m ok with that.
> 
> Thoughts?
> 
> Ralph
> 
> -
> To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
> For additional commands, e-mail: log4j-dev-h...@logging.apache.org
> 
> 



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

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

2016-06-03 Thread Ralph Goers (JIRA)


 [ 
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 to AbstractFilterable I did 
use the test class you created, after some modifications, so you are still 
getting credit for the fix.

Please verify and close.

> removeFilter() in AbstractFilterable does not remove filter
> ---
>
> Key: LOG4J2-997
> URL: https://issues.apache.org/jira/browse/LOG4J2-997
> Project: Log4j 2
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 2.2
>Reporter: Maytee Chinavanichkit
>Assignee: Ralph Goers
> Fix For: 2.6.1
>
>
> Add two filters to a class that implements AbstractFilterable. Try to remove 
> one of the two filters; nothing is removed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

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

2016-06-03 Thread Ralph Goers (JIRA)


[ 
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 not like 1) This 
patch goes way beyond what the problem statement is (not being able to remove a 
filter, 2) a Filterable always has a CompositeFilter, and 3) adding 2 composite 
filters actually results in 2 composite filters.

The way filtering is supposed to work is that you either have no filters, a 
filter, or a single composite filter containing multiple individual filters. 
While you can add a composite to a composite or two composites to 
AbstractFilterable programmatically, it is impossible to do from configuration. 

I will modify CompositeFilter so that if another CompositeFilter is being added 
all the individual filters will be added so there will still only be one 
CompositeFilter.

The basic root of the problem was that addFilter and removeFilter were testing 
the passed in filter to see if it is a CompositeFilter when it should have been 
checking this.filter.

> removeFilter() in AbstractFilterable does not remove filter
> ---
>
> Key: LOG4J2-997
> URL: https://issues.apache.org/jira/browse/LOG4J2-997
> Project: Log4j 2
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 2.2
>Reporter: Maytee Chinavanichkit
>Assignee: Ralph Goers
>
> Add two filters to a class that implements AbstractFilterable. Try to remove 
> one of the two filters; nothing is removed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

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

2016-06-02 Thread Ralph Goers

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  >
> 
> 
> -
> To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org 
> 
> For additional commands, e-mail: log4j-dev-h...@logging.apache.org 
> 
> 
> 
> 
> 
> -- 
> Matt Sicker >

[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 filter
> ---
>
> Key: LOG4J2-997
> URL: https://issues.apache.org/jira/browse/LOG4J2-997
> Project: Log4j 2
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 2.2
>Reporter: Maytee Chinavanichkit
>Assignee: Ralph Goers
>
> Add two filters to a class that implements AbstractFilterable. Try to remove 
> one of the two filters; nothing is removed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[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 report rename 
failures and their cause. This won't fix the issue. That will require an 
enhancement to the RollingFileAppender to write to the filePattern directly 
instead of renaming files.

> Rollover startegy failing on high load
> --
>
> Key: LOG4J2-1032
> URL: https://issues.apache.org/jira/browse/LOG4J2-1032
> Project: Log4j 2
>  Issue Type: Bug
>  Components: Appenders
>Affects Versions: 2.1
>Reporter: Binoy Varghese
>Assignee: Ralph Goers
>
> On windows virtual machines, the roll over strategy simply fails and the log 
> size becomes huge. This happens on high load on tomcat server.
> Log4j2 is loaded from our application using below configuration
> {code}
> 
> 
>   
>   
>  
> fileName="${sys:catalina.base}/logs/xvx/com.xvx.connector.log"
>   
> filePattern="${sys:catalina.base}/logs/xvx/com.xvx.connector-%d{dd-MM-}#%i.log">
>   
>   
>   
>   
>   
>   
>   
>  
> fileName="${sys:catalina.base}/logs/xvx/com.xvx.connector-request-response.log"
>   
> filePattern="${sys:catalina.base}/logs/xvx/com.xvx.connector-request-response-%d{dd-MM-}#%i.log">
>   
>   
>   
>   
>   
>   
>   
>  
> fileName="${sys:catalina.base}/logs/xvx/com.xvx.connector-time.log"
>   
> filePattern="${sys:catalina.base}/logs/xvx/com.xvx.connector-time-%d{dd-MM-}#%i.log">
>   
>   
>   
>   
>   
>   
>   
>   
>  
> fileName="${sys:catalina.base}/logs/xvx/org.springframework.log"
>   
> filePattern="${sys:catalina.base}/logs/xvx/org.springframework-%d{dd-MM-}#%i.log">
>   
>   
>   
>   
>   
>   
>   
>   
>  
> fileName="${sys:catalina.base}/logs/xvx/org.springframework.jdbc.log"
>   
> filePattern="${sys:catalina.base}/logs/xvx/org.springframework.jdbc-%d{dd-MM-}#%i.log">
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>level="DEBUG" additivity="false">
>   
>   
>additivity="false">
>   
>   
>additivity="false">
>   
>   
>additivity="false">
>   
>   
>   
>   
>   
>   
>   
> 
> {code}
> we are using slf4j 1.7.7



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[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 restart
> --
>
> Key: LOG4J2-1228
> URL: https://issues.apache.org/jira/browse/LOG4J2-1228
> Project: Log4j 2
>  Issue Type: Bug
>  Components: Layouts
>Reporter: Steve Davids
>    Assignee: Ralph Goers
> Attachments: LOG4J2-1228-test.diff
>
>
> I created a custom layout that appends a header and footer to a rolling file 
> appender with a time based and startup trigger policies which works great 
> during normal circumstances except when it comes to system restarts. On 
> shutdown the file is closed with the footer being written to the file, then 
> on startup the startup trigger policy will open the file then immediately 
> roll thus printing the footer again on rollover (prior to v2.4 the header was 
> also written on startup LOG4J2-1030). I am attempting to produce well-formed 
> XML with this particular use-case but it is getting mangled at this 
> particular point. Ideally we can either have the footer either not print the 
> second time or just perform the rollover on shutdown.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[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't tell me what was done 
about the reported problem.

> Misleading WARN log events from Log4j about message factories and unexpected 
> formatting
> ---
>
> Key: LOG4J2-1407
> URL: https://issues.apache.org/jira/browse/LOG4J2-1407
> Project: Log4j 2
>  Issue Type: Bug
>  Components: API
>Affects Versions: 2.6
>Reporter: Gary Gregory
>Assignee: Gary Gregory
> Fix For: 2.6.1
>
>
> We log misleading WARN log events from Log4j about message factories and 
> unexpected formatting.
> For example:
> {noformat}
> 2016-05-29 18:21:46,712 main WARN The Logger com.example.foo was created with 
> the message factory 
> org.apache.logging.log4j.spi.MessageFactory2Adapter@46bc9802 and is now 
> requested with the message factory org.apache.logging.log4j.m
> essage.StringFormatterMessageFactory@510e0dd2, which may create log events 
> with unexpected formatting.
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

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

> Misleading WARN log events from Log4j about message factories and unexpected 
> formatting
> ---
>
> Key: LOG4J2-1407
> URL: https://issues.apache.org/jira/browse/LOG4J2-1407
> Project: Log4j 2
>  Issue Type: Bug
>  Components: API
>Affects Versions: 2.6
>Reporter: Gary Gregory
>Assignee: Gary Gregory
> Fix For: 2.6.1
>
>
> We log misleading WARN log events from Log4j about message factories and 
> unexpected formatting.
> For example:
> {noformat}
> 2016-05-29 18:21:46,712 main WARN The Logger com.example.foo was created with 
> the message factory 
> org.apache.logging.log4j.spi.MessageFactory2Adapter@46bc9802 and is now 
> requested with the message factory org.apache.logging.log4j.m
> essage.StringFormatterMessageFactory@510e0dd2, which may create log events 
> with unexpected formatting.
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[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 and should be 
included in the 2.6.1 release planned for this weekend.

> 2.6 is re-logging prior throwable instead of logging the throwable that is 
> currently passed in by application code
> --
>
> Key: LOG4J2-1406
> URL: https://issues.apache.org/jira/browse/LOG4J2-1406
> Project: Log4j 2
>  Issue Type: Bug
>Affects Versions: 2.6
>Reporter: Trask Stalnaker
>Priority: Critical
>
> Hi,
> I just want to make sure you saw the issue I submitted PR for a couple days 
> ago.  It seems a very serious issue in 2.6:
> https://github.com/apache/logging-log4j2/pull/31
> Thanks,
> Trask



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[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 but there is a post build step to 
deploy to Nexus.

> Exception when using log4j2.properties and logger with dash
> ---
>
> Key: LOG4J2-1402
> URL: https://issues.apache.org/jira/browse/LOG4J2-1402
> Project: Log4j 2
>  Issue Type: Bug
>Affects Versions: 2.6
>Reporter: Pascal Schumacher
>    Assignee: Ralph Goers
> Fix For: 2.6.1
>
>
> After upgrading log4j2 from 2.5 to 2.6 I get the following exception:
> {quote}
> Exception in thread "main" 
> org.apache.logging.log4j.core.config.ConfigurationException: No name 
> attribute provided for Logger org
>   at 
> org.apache.logging.log4j.core.config.properties.PropertiesConfigurationBuilder.createLogger(PropertiesConfigurationBuilder.java:215)
>   at 
> org.apache.logging.log4j.core.config.properties.PropertiesConfigurationBuilder.build(PropertiesConfigurationBuilder.java:140)
>   at 
> org.apache.logging.log4j.core.config.properties.PropertiesConfigurationFactory.getConfiguration(PropertiesConfigurationFactory.java:52)
>   at 
> org.apache.logging.log4j.core.config.properties.PropertiesConfigurationFactory.getConfiguration(PropertiesConfigurationFactory.java:34)
>   at 
> org.apache.logging.log4j.core.config.ConfigurationFactory$Factory.getConfiguration(ConfigurationFactory.java:510)
>   at 
> org.apache.logging.log4j.core.config.ConfigurationFactory$Factory.getConfiguration(ConfigurationFactory.java:450)
>   at 
> org.apache.logging.log4j.core.config.ConfigurationFactory.getConfiguration(ConfigurationFactory.java:257)
>   at 
> org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:560)
>   at 
> org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:577)
>   at 
> org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:212)
>   at 
> org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:152)
>   at 
> org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:45)
>   at org.apache.logging.log4j.LogManager.getContext(LogManager.java:194)
>   at 
> org.apache.logging.log4j.spi.AbstractLoggerAdapter.getContext(AbstractLoggerAdapter.java:103)
>   at 
> org.apache.logging.log4j.jcl.LogAdapter.getContext(LogAdapter.java:39)
>   at 
> org.apache.logging.log4j.spi.AbstractLoggerAdapter.getLogger(AbstractLoggerAdapter.java:42)
>   at 
> org.apache.logging.log4j.jcl.LogFactoryImpl.getInstance(LogFactoryImpl.java:40)
>   at 
> org.apache.logging.log4j.jcl.LogFactoryImpl.getInstance(LogFactoryImpl.java:55)
>   at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:655)
>   at 
> org.springframework.context.support.AbstractApplicationContext.(AbstractApplicationContext.java:159)
>   at 
> org.springframework.context.support.AbstractApplicationContext.(AbstractApplicationContext.java:223)
>   at 
> org.springframework.context.support.AbstractRefreshableApplicationContext.(AbstractRefreshableApplicationContext.java:88)
>   at 
> org.springframework.context.support.AbstractRefreshableConfigApplicationContext.(AbstractRefreshableConfigApplicationContext.java:58)
>   at 
> org.springframework.context.support.AbstractXmlApplicationContext.(AbstractXmlApplicationContext.java:61)
>   at 
> org.springframework.context.support.ClassPathXmlApplicationContext.(ClassPathXmlApplicationContext.java:136)
>   at 
> org.springframework.context.support.ClassPathXmlApplicationContext.(ClassPathXmlApplicationContext.java:83)
> x.y.z.Start.main(Start.java:12)
> {quote}
> The parameter "key" has the value "org" and the parameter properties has the 
> value {code}{activiti.engine.impl.level=info, 
> activiti.engine.impl.name=org.activiti.engine.impl}{code}
> The log4j2.properties in use:
> {code}
> # Root logger option
> rootLogger.level = info
> rootLogger.appenderRefs = stdout
> rootLogger.appenderRef.stdout.ref = STDOUT
> # Redirect log messages to console
> appenders = stdout
> appender.stdout.type = Console
> appender.stdout.name = STDOUT
> appender.stdout.layout.type = PatternLayout
> appender.stdout.layout.pattern = %d %-5p [%t] %c - %m%n
> {code}
> Sadly I have not been able to reproduce the issue in a simple standalone 
> application.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[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 the SNAPSHOTs. It probably 
should.

> Exception when using log4j2.properties and logger with dash
> ---
>
> Key: LOG4J2-1402
> URL: https://issues.apache.org/jira/browse/LOG4J2-1402
> Project: Log4j 2
>  Issue Type: Bug
>Affects Versions: 2.6
>Reporter: Pascal Schumacher
>    Assignee: Ralph Goers
> Fix For: 2.6.1
>
>
> After upgrading log4j2 from 2.5 to 2.6 I get the following exception:
> {quote}
> Exception in thread "main" 
> org.apache.logging.log4j.core.config.ConfigurationException: No name 
> attribute provided for Logger org
>   at 
> org.apache.logging.log4j.core.config.properties.PropertiesConfigurationBuilder.createLogger(PropertiesConfigurationBuilder.java:215)
>   at 
> org.apache.logging.log4j.core.config.properties.PropertiesConfigurationBuilder.build(PropertiesConfigurationBuilder.java:140)
>   at 
> org.apache.logging.log4j.core.config.properties.PropertiesConfigurationFactory.getConfiguration(PropertiesConfigurationFactory.java:52)
>   at 
> org.apache.logging.log4j.core.config.properties.PropertiesConfigurationFactory.getConfiguration(PropertiesConfigurationFactory.java:34)
>   at 
> org.apache.logging.log4j.core.config.ConfigurationFactory$Factory.getConfiguration(ConfigurationFactory.java:510)
>   at 
> org.apache.logging.log4j.core.config.ConfigurationFactory$Factory.getConfiguration(ConfigurationFactory.java:450)
>   at 
> org.apache.logging.log4j.core.config.ConfigurationFactory.getConfiguration(ConfigurationFactory.java:257)
>   at 
> org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:560)
>   at 
> org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:577)
>   at 
> org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:212)
>   at 
> org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:152)
>   at 
> org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:45)
>   at org.apache.logging.log4j.LogManager.getContext(LogManager.java:194)
>   at 
> org.apache.logging.log4j.spi.AbstractLoggerAdapter.getContext(AbstractLoggerAdapter.java:103)
>   at 
> org.apache.logging.log4j.jcl.LogAdapter.getContext(LogAdapter.java:39)
>   at 
> org.apache.logging.log4j.spi.AbstractLoggerAdapter.getLogger(AbstractLoggerAdapter.java:42)
>   at 
> org.apache.logging.log4j.jcl.LogFactoryImpl.getInstance(LogFactoryImpl.java:40)
>   at 
> org.apache.logging.log4j.jcl.LogFactoryImpl.getInstance(LogFactoryImpl.java:55)
>   at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:655)
>   at 
> org.springframework.context.support.AbstractApplicationContext.(AbstractApplicationContext.java:159)
>   at 
> org.springframework.context.support.AbstractApplicationContext.(AbstractApplicationContext.java:223)
>   at 
> org.springframework.context.support.AbstractRefreshableApplicationContext.(AbstractRefreshableApplicationContext.java:88)
>   at 
> org.springframework.context.support.AbstractRefreshableConfigApplicationContext.(AbstractRefreshableConfigApplicationContext.java:58)
>   at 
> org.springframework.context.support.AbstractXmlApplicationContext.(AbstractXmlApplicationContext.java:61)
>   at 
> org.springframework.context.support.ClassPathXmlApplicationContext.(ClassPathXmlApplicationContext.java:136)
>   at 
> org.springframework.context.support.ClassPathXmlApplicationContext.(ClassPathXmlApplicationContext.java:83)
> x.y.z.Start.main(Start.java:12)
> {quote}
> The parameter "key" has the value "org" and the parameter properties has the 
> value {code}{activiti.engine.impl.level=info, 
> activiti.engine.impl.name=org.activiti.engine.impl}{code}
> The log4j2.properties in use:
> {code}
> # Root logger option
> rootLogger.level = info
> rootLogger.appenderRefs = stdout
> rootLogger.appenderRef.stdout.ref = STDOUT
> # Redirect log messages to console
> appenders = stdout
> appender.stdout.type = Console
> appender.stdout.name = STDOUT
> appender.stdout.layout.type = PatternLayout
> appender.stdout.layout.pattern = %d %-5p [%t] %c - %m%n
> {code}
> Sadly I have not been able to reproduce the issue in a simple standalone 
> application.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

Log4j 2.6.1

2016-06-01 Thread Ralph Goers

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 the 
only real fix for Windows.  However, I don’t want to do that in a point release.

LOG4J2-1180 was updated today and it seems the support for having Loggers 
stored by their message factory is not working correctly. Gary apparently is 
also experiencing this problem.

I would like to see if we can fix these three items this week and do another 
release this weekend.  If there are any other bugs that can be addressed by 
then I’m ok with that.

Thoughts?

Ralph

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

[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 midnight.
> ---
>
> Key: LOG4J2-1250
> URL: https://issues.apache.org/jira/browse/LOG4J2-1250
> Project: Log4j 2
>  Issue Type: Question
>  Components: Appenders
>Affects Versions: 2.5
>Reporter: lee yongjoong
>Assignee: Ralph Goers
>
> Hi.
> I tried CrontriggeringPolicy(added 2.5) for save daily log files at midnight.
> My goal is, for example.
> if today is 2015/01/01, "http.log" <- active file.
> and when midnight, "http.log" will be renamed "http_20150101.log", and create 
> new "http.log".
> But my problem is when midnight, "http.log" renamed "http_20150102.log"...
> I want to make that file's name "http_20150101.log" because that file has 
> 2015/01/01's log,
> Here's my configure xml.
> {code:xml}
> 
>   
> 
>filepattern="${path}/http_%d{MMdd}.log">
> 
> 
>   
> 
>   
> 
> {code}
> Please help me.
> Thanks for your help, I'm very appreciated it :D



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[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 and close.

> org.apache.logging.log4j.core.config.ConfigurationException: No name 
> attribute provided for Logger org
> --
>
> Key: LOG4J2-1402
> URL: https://issues.apache.org/jira/browse/LOG4J2-1402
> Project: Log4j 2
>  Issue Type: Bug
>  Components: JCL Bridge
>Affects Versions: 2.6
>Reporter: Pascal Schumacher
>Assignee: Ralph Goers
> Fix For: 2.6.1
>
>
> After upgrading log4j2 from 2.5 to 2.6 I get the following exception:
> {quote}
> Exception in thread "main" 
> org.apache.logging.log4j.core.config.ConfigurationException: No name 
> attribute provided for Logger org
>   at 
> org.apache.logging.log4j.core.config.properties.PropertiesConfigurationBuilder.createLogger(PropertiesConfigurationBuilder.java:215)
>   at 
> org.apache.logging.log4j.core.config.properties.PropertiesConfigurationBuilder.build(PropertiesConfigurationBuilder.java:140)
>   at 
> org.apache.logging.log4j.core.config.properties.PropertiesConfigurationFactory.getConfiguration(PropertiesConfigurationFactory.java:52)
>   at 
> org.apache.logging.log4j.core.config.properties.PropertiesConfigurationFactory.getConfiguration(PropertiesConfigurationFactory.java:34)
>   at 
> org.apache.logging.log4j.core.config.ConfigurationFactory$Factory.getConfiguration(ConfigurationFactory.java:510)
>   at 
> org.apache.logging.log4j.core.config.ConfigurationFactory$Factory.getConfiguration(ConfigurationFactory.java:450)
>   at 
> org.apache.logging.log4j.core.config.ConfigurationFactory.getConfiguration(ConfigurationFactory.java:257)
>   at 
> org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:560)
>   at 
> org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:577)
>   at 
> org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:212)
>   at 
> org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:152)
>   at 
> org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:45)
>   at org.apache.logging.log4j.LogManager.getContext(LogManager.java:194)
>   at 
> org.apache.logging.log4j.spi.AbstractLoggerAdapter.getContext(AbstractLoggerAdapter.java:103)
>   at 
> org.apache.logging.log4j.jcl.LogAdapter.getContext(LogAdapter.java:39)
>   at 
> org.apache.logging.log4j.spi.AbstractLoggerAdapter.getLogger(AbstractLoggerAdapter.java:42)
>   at 
> org.apache.logging.log4j.jcl.LogFactoryImpl.getInstance(LogFactoryImpl.java:40)
>   at 
> org.apache.logging.log4j.jcl.LogFactoryImpl.getInstance(LogFactoryImpl.java:55)
>   at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:655)
>   at 
> org.springframework.context.support.AbstractApplicationContext.(AbstractApplicationContext.java:159)
>   at 
> org.springframework.context.support.AbstractApplicationContext.(AbstractApplicationContext.java:223)
>   at 
> org.springframework.context.support.AbstractRefreshableApplicationContext.(AbstractRefreshableApplicationContext.java:88)
>   at 
> org.springframework.context.support.AbstractRefreshableConfigApplicationContext.(AbstractRefreshableConfigApplicationContext.java:58)
>   at 
> org.springframework.context.support.AbstractXmlApplicationContext.(AbstractXmlApplicationContext.java:61)
>   at 
> org.springframework.context.support.ClassPathXmlApplicationContext.(ClassPathXmlApplicationContext.java:136)
>   at 
> org.springframework.context.support.ClassPathXmlApplicationContext.(ClassPathXmlApplicationContext.java:83)
> x.y.z.Start.main(Start.java:12)
> {quote}
> The parameter "key" has the value "org" and the parameter properties has the 
> value {code}{activiti.engine.impl.level=info, 
> activiti.engine.impl.name=org.activiti.engine.impl}{code}
> The log4j2.properties in use:
> {code}
> # Root logger option
> rootLogger.level = info
> rootLogger.appenderRefs = stdout
> rootLogger.appenderRef.stdout.ref = STDOUT
> # Redirect log messages to console
> appenders = stdout
> appender.stdout.type = Console
> appender.stdout.name = STDOUT
> appender.stdout.layout.type = PatternLayout
> appender.stdout.layout.pattern = %d %-5p [%t] %c - %m%n
> {code}
> Sa

[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.ConfigurationException: No name 
> attribute provided for Logger org
> --
>
> Key: LOG4J2-1402
> URL: https://issues.apache.org/jira/browse/LOG4J2-1402
> Project: Log4j 2
>  Issue Type: Bug
>  Components: JCL Bridge
>Affects Versions: 2.6
>Reporter: Pascal Schumacher
>Assignee: Ralph Goers
>
> After upgrading log4j2 from 2.5 to 2.6 I get the following exception:
> {quote}
> Exception in thread "main" 
> org.apache.logging.log4j.core.config.ConfigurationException: No name 
> attribute provided for Logger org
>   at 
> org.apache.logging.log4j.core.config.properties.PropertiesConfigurationBuilder.createLogger(PropertiesConfigurationBuilder.java:215)
>   at 
> org.apache.logging.log4j.core.config.properties.PropertiesConfigurationBuilder.build(PropertiesConfigurationBuilder.java:140)
>   at 
> org.apache.logging.log4j.core.config.properties.PropertiesConfigurationFactory.getConfiguration(PropertiesConfigurationFactory.java:52)
>   at 
> org.apache.logging.log4j.core.config.properties.PropertiesConfigurationFactory.getConfiguration(PropertiesConfigurationFactory.java:34)
>   at 
> org.apache.logging.log4j.core.config.ConfigurationFactory$Factory.getConfiguration(ConfigurationFactory.java:510)
>   at 
> org.apache.logging.log4j.core.config.ConfigurationFactory$Factory.getConfiguration(ConfigurationFactory.java:450)
>   at 
> org.apache.logging.log4j.core.config.ConfigurationFactory.getConfiguration(ConfigurationFactory.java:257)
>   at 
> org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:560)
>   at 
> org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:577)
>   at 
> org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:212)
>   at 
> org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:152)
>   at 
> org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:45)
>   at org.apache.logging.log4j.LogManager.getContext(LogManager.java:194)
>   at 
> org.apache.logging.log4j.spi.AbstractLoggerAdapter.getContext(AbstractLoggerAdapter.java:103)
>   at 
> org.apache.logging.log4j.jcl.LogAdapter.getContext(LogAdapter.java:39)
>   at 
> org.apache.logging.log4j.spi.AbstractLoggerAdapter.getLogger(AbstractLoggerAdapter.java:42)
>   at 
> org.apache.logging.log4j.jcl.LogFactoryImpl.getInstance(LogFactoryImpl.java:40)
>   at 
> org.apache.logging.log4j.jcl.LogFactoryImpl.getInstance(LogFactoryImpl.java:55)
>   at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:655)
>   at 
> org.springframework.context.support.AbstractApplicationContext.(AbstractApplicationContext.java:159)
>   at 
> org.springframework.context.support.AbstractApplicationContext.(AbstractApplicationContext.java:223)
>   at 
> org.springframework.context.support.AbstractRefreshableApplicationContext.(AbstractRefreshableApplicationContext.java:88)
>   at 
> org.springframework.context.support.AbstractRefreshableConfigApplicationContext.(AbstractRefreshableConfigApplicationContext.java:58)
>   at 
> org.springframework.context.support.AbstractXmlApplicationContext.(AbstractXmlApplicationContext.java:61)
>   at 
> org.springframework.context.support.ClassPathXmlApplicationContext.(ClassPathXmlApplicationContext.java:136)
>   at 
> org.springframework.context.support.ClassPathXmlApplicationContext.(ClassPathXmlApplicationContext.java:83)
> x.y.z.Start.main(Start.java:12)
> {quote}
> The parameter "key" has the value "org" and the parameter properties has the 
> value {code}{activiti.engine.impl.level=info, 
> activiti.engine.impl.name=org.activiti.engine.impl}{code}
> The log4j2.properties in use:
> {code}
> # Root logger option
> rootLogger.level = info
> rootLogger.appenderRefs = stdout
> rootLogger.appenderRef.stdout.ref = STDOUT
> # Redirect log messages to console
> appenders = stdout
> appender.stdout.type = Console
> appender.stdout.name = STDOUT
> appender.stdout.layout.type = PatternLayout
> appender.stdout.layout.pattern = %d %-5p [%t] %c - %m%n
> {code}
> Sadly I have not been able to reproduce the issue in a simple standalone 
> application.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

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

> org.apache.logging.log4j.core.config.ConfigurationException: No name 
> attribute provided for Logger org
> --
>
> Key: LOG4J2-1402
> URL: https://issues.apache.org/jira/browse/LOG4J2-1402
> Project: Log4j 2
>  Issue Type: Bug
>  Components: JCL Bridge
>Affects Versions: 2.6
>Reporter: Pascal Schumacher
>
> After upgrading log4j2 from 2.5 to 2.6 I get the following exception:
> {quote}
> Exception in thread "main" 
> org.apache.logging.log4j.core.config.ConfigurationException: No name 
> attribute provided for Logger org
>   at 
> org.apache.logging.log4j.core.config.properties.PropertiesConfigurationBuilder.createLogger(PropertiesConfigurationBuilder.java:215)
>   at 
> org.apache.logging.log4j.core.config.properties.PropertiesConfigurationBuilder.build(PropertiesConfigurationBuilder.java:140)
>   at 
> org.apache.logging.log4j.core.config.properties.PropertiesConfigurationFactory.getConfiguration(PropertiesConfigurationFactory.java:52)
>   at 
> org.apache.logging.log4j.core.config.properties.PropertiesConfigurationFactory.getConfiguration(PropertiesConfigurationFactory.java:34)
>   at 
> org.apache.logging.log4j.core.config.ConfigurationFactory$Factory.getConfiguration(ConfigurationFactory.java:510)
>   at 
> org.apache.logging.log4j.core.config.ConfigurationFactory$Factory.getConfiguration(ConfigurationFactory.java:450)
>   at 
> org.apache.logging.log4j.core.config.ConfigurationFactory.getConfiguration(ConfigurationFactory.java:257)
>   at 
> org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:560)
>   at 
> org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:577)
>   at 
> org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:212)
>   at 
> org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:152)
>   at 
> org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:45)
>   at org.apache.logging.log4j.LogManager.getContext(LogManager.java:194)
>   at 
> org.apache.logging.log4j.spi.AbstractLoggerAdapter.getContext(AbstractLoggerAdapter.java:103)
>   at 
> org.apache.logging.log4j.jcl.LogAdapter.getContext(LogAdapter.java:39)
>   at 
> org.apache.logging.log4j.spi.AbstractLoggerAdapter.getLogger(AbstractLoggerAdapter.java:42)
>   at 
> org.apache.logging.log4j.jcl.LogFactoryImpl.getInstance(LogFactoryImpl.java:40)
>   at 
> org.apache.logging.log4j.jcl.LogFactoryImpl.getInstance(LogFactoryImpl.java:55)
>   at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:655)
>   at 
> org.springframework.context.support.AbstractApplicationContext.(AbstractApplicationContext.java:159)
>   at 
> org.springframework.context.support.AbstractApplicationContext.(AbstractApplicationContext.java:223)
>   at 
> org.springframework.context.support.AbstractRefreshableApplicationContext.(AbstractRefreshableApplicationContext.java:88)
>   at 
> org.springframework.context.support.AbstractRefreshableConfigApplicationContext.(AbstractRefreshableConfigApplicationContext.java:58)
>   at 
> org.springframework.context.support.AbstractXmlApplicationContext.(AbstractXmlApplicationContext.java:61)
>   at 
> org.springframework.context.support.ClassPathXmlApplicationContext.(ClassPathXmlApplicationContext.java:136)
>   at 
> org.springframework.context.support.ClassPathXmlApplicationContext.(ClassPathXmlApplicationContext.java:83)
> x.y.z.Start.main(Start.java:12)
> {quote}
> The parameter "key" has the value "org" and the parameter properties has the 
> value {code}{activiti.engine.impl.level=info, 
> activiti.engine.impl.name=org.activiti.engine.impl}{code}
> The log4j2.properties in use:
> {code}
> # Root logger option
> rootLogger.level = info
> rootLogger.appenderRefs = stdout
> rootLogger.appenderRef.stdout.ref = STDOUT
> # Redirect log messages to console
> appenders = stdout
> appender.stdout.type = Console
> appender.stdout.name = STDOUT
> appender.stdout.layout.type = PatternLayout
> appender.stdout.layout.pattern = %d %-5p [%t] %c - %m%n
> {code}
> Sadly I have not been able to reproduce the issue in a simple standalone 
> application.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[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 file support had no relationship to 1.x. The original code that 
I wrote and was delivered in 2.5 supported identifiers like what I showed 
above. We need to restore that.

I will modify log4j-rolling.properties so that it represents this case so it 
will fail and we can fix it.


was (Author: ralph.go...@dslextreme.com):
Our properties file support had no relationship to 1.x. The original code that 
I wrote and was delivered in 2.5 supported identifiers like what I showed 
above. We need to restore that.

> org.apache.logging.log4j.core.config.ConfigurationException: No name 
> attribute provided for Logger org
> --
>
> Key: LOG4J2-1402
> URL: https://issues.apache.org/jira/browse/LOG4J2-1402
> Project: Log4j 2
>  Issue Type: Bug
>  Components: JCL Bridge
>Affects Versions: 2.6
>Reporter: Pascal Schumacher
>
> After upgrading log4j2 from 2.5 to 2.6 I get the following exception:
> {quote}
> Exception in thread "main" 
> org.apache.logging.log4j.core.config.ConfigurationException: No name 
> attribute provided for Logger org
>   at 
> org.apache.logging.log4j.core.config.properties.PropertiesConfigurationBuilder.createLogger(PropertiesConfigurationBuilder.java:215)
>   at 
> org.apache.logging.log4j.core.config.properties.PropertiesConfigurationBuilder.build(PropertiesConfigurationBuilder.java:140)
>   at 
> org.apache.logging.log4j.core.config.properties.PropertiesConfigurationFactory.getConfiguration(PropertiesConfigurationFactory.java:52)
>   at 
> org.apache.logging.log4j.core.config.properties.PropertiesConfigurationFactory.getConfiguration(PropertiesConfigurationFactory.java:34)
>   at 
> org.apache.logging.log4j.core.config.ConfigurationFactory$Factory.getConfiguration(ConfigurationFactory.java:510)
>   at 
> org.apache.logging.log4j.core.config.ConfigurationFactory$Factory.getConfiguration(ConfigurationFactory.java:450)
>   at 
> org.apache.logging.log4j.core.config.ConfigurationFactory.getConfiguration(ConfigurationFactory.java:257)
>   at 
> org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:560)
>   at 
> org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:577)
>   at 
> org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:212)
>   at 
> org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:152)
>   at 
> org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:45)
>   at org.apache.logging.log4j.LogManager.getContext(LogManager.java:194)
>   at 
> org.apache.logging.log4j.spi.AbstractLoggerAdapter.getContext(AbstractLoggerAdapter.java:103)
>   at 
> org.apache.logging.log4j.jcl.LogAdapter.getContext(LogAdapter.java:39)
>   at 
> org.apache.logging.log4j.spi.AbstractLoggerAdapter.getLogger(AbstractLoggerAdapter.java:42)
>   at 
> org.apache.logging.log4j.jcl.LogFactoryImpl.getInstance(LogFactoryImpl.java:40)
>   at 
> org.apache.logging.log4j.jcl.LogFactoryImpl.getInstance(LogFactoryImpl.java:55)
>   at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:655)
>   at 
> org.springframework.context.support.AbstractApplicationContext.(AbstractApplicationContext.java:159)
>   at 
> org.springframework.context.support.AbstractApplicationContext.(AbstractApplicationContext.java:223)
>   at 
> org.springframework.context.support.AbstractRefreshableApplicationContext.(AbstractRefreshableApplicationContext.java:88)
>   at 
> org.springframework.context.support.AbstractRefreshableConfigApplicationContext.(AbstractRefreshableConfigApplicationContext.java:58)
>   at 
> org.springframework.context.support.AbstractXmlApplicationContext.(AbstractXmlApplicationContext.java:61)
>   at 
> org.springframework.context.support.ClassPathXmlApplicationContext.(ClassPathXmlApplicationContext.java:136)
>   at 
> org.springframework.context.support.ClassPathXmlApplicationContext.(ClassPathXmlApplicationContext.java:83)
> x.y.z.Start.main(Start.java:12)
> {quote}
> The parameter "key" has the value "org" and the parameter properties has the 
> value {code}{activiti.engine.impl.level=info, 
> activiti.engine.impl.name=org.activiti.engine.impl}{code}
> The log4j

[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. The original code that 
I wrote and was delivered in 2.5 supported identifiers like what I showed 
above. We need to restore that.

> org.apache.logging.log4j.core.config.ConfigurationException: No name 
> attribute provided for Logger org
> --
>
> Key: LOG4J2-1402
> URL: https://issues.apache.org/jira/browse/LOG4J2-1402
> Project: Log4j 2
>  Issue Type: Bug
>  Components: JCL Bridge
>Affects Versions: 2.6
>Reporter: Pascal Schumacher
>
> After upgrading log4j2 from 2.5 to 2.6 I get the following exception:
> {quote}
> Exception in thread "main" 
> org.apache.logging.log4j.core.config.ConfigurationException: No name 
> attribute provided for Logger org
>   at 
> org.apache.logging.log4j.core.config.properties.PropertiesConfigurationBuilder.createLogger(PropertiesConfigurationBuilder.java:215)
>   at 
> org.apache.logging.log4j.core.config.properties.PropertiesConfigurationBuilder.build(PropertiesConfigurationBuilder.java:140)
>   at 
> org.apache.logging.log4j.core.config.properties.PropertiesConfigurationFactory.getConfiguration(PropertiesConfigurationFactory.java:52)
>   at 
> org.apache.logging.log4j.core.config.properties.PropertiesConfigurationFactory.getConfiguration(PropertiesConfigurationFactory.java:34)
>   at 
> org.apache.logging.log4j.core.config.ConfigurationFactory$Factory.getConfiguration(ConfigurationFactory.java:510)
>   at 
> org.apache.logging.log4j.core.config.ConfigurationFactory$Factory.getConfiguration(ConfigurationFactory.java:450)
>   at 
> org.apache.logging.log4j.core.config.ConfigurationFactory.getConfiguration(ConfigurationFactory.java:257)
>   at 
> org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:560)
>   at 
> org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:577)
>   at 
> org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:212)
>   at 
> org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:152)
>   at 
> org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:45)
>   at org.apache.logging.log4j.LogManager.getContext(LogManager.java:194)
>   at 
> org.apache.logging.log4j.spi.AbstractLoggerAdapter.getContext(AbstractLoggerAdapter.java:103)
>   at 
> org.apache.logging.log4j.jcl.LogAdapter.getContext(LogAdapter.java:39)
>   at 
> org.apache.logging.log4j.spi.AbstractLoggerAdapter.getLogger(AbstractLoggerAdapter.java:42)
>   at 
> org.apache.logging.log4j.jcl.LogFactoryImpl.getInstance(LogFactoryImpl.java:40)
>   at 
> org.apache.logging.log4j.jcl.LogFactoryImpl.getInstance(LogFactoryImpl.java:55)
>   at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:655)
>   at 
> org.springframework.context.support.AbstractApplicationContext.(AbstractApplicationContext.java:159)
>   at 
> org.springframework.context.support.AbstractApplicationContext.(AbstractApplicationContext.java:223)
>   at 
> org.springframework.context.support.AbstractRefreshableApplicationContext.(AbstractRefreshableApplicationContext.java:88)
>   at 
> org.springframework.context.support.AbstractRefreshableConfigApplicationContext.(AbstractRefreshableConfigApplicationContext.java:58)
>   at 
> org.springframework.context.support.AbstractXmlApplicationContext.(AbstractXmlApplicationContext.java:61)
>   at 
> org.springframework.context.support.ClassPathXmlApplicationContext.(ClassPathXmlApplicationContext.java:136)
>   at 
> org.springframework.context.support.ClassPathXmlApplicationContext.(ClassPathXmlApplicationContext.java:83)
> x.y.z.Start.main(Start.java:12)
> {quote}
> The parameter "key" has the value "org" and the parameter properties has the 
> value {code}{activiti.engine.impl.level=info, 
> activiti.engine.impl.name=org.activiti.engine.impl}{code}
> The log4j2.properties in use:
> {code}
> # Root logger option
> rootLogger.level = info
> rootLogger.appenderRefs = stdout
> rootLogger.appenderRef.stdout.ref = STDOUT
> # Redirect log messages to console
> appenders = stdout
> appender.stdout.type = Console
> appender.stdout.name = STDOUT
> appender.stdout.layout.type = PatternLayout
> appender.stdout.layout.patt

[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 guessing the actual 
file contains
{code}
logger.org.activiti.engine.impl.level=info
logger.org.activiti.engine.impl.name=org.activiti.engine.impl
{code}

I believe this is due to the "enhancement" that was added to no longer require 
declaring the individual loggers as 

loggers = org.activiti.engine.impl

The code now only allows the logger identifier to be a single "word" without 
any periods and so breaks configurations such as the above. This is a break in 
compatibility and needs to be fixed asap by still honoring the list of logger 
identifiers if it is present.

> org.apache.logging.log4j.core.config.ConfigurationException: No name 
> attribute provided for Logger org
> --
>
> Key: LOG4J2-1402
> URL: https://issues.apache.org/jira/browse/LOG4J2-1402
> Project: Log4j 2
>  Issue Type: Bug
>  Components: JCL Bridge
>Affects Versions: 2.6
>Reporter: Pascal Schumacher
>
> After upgrading log4j2 from 2.5 to 2.6 I get the following exception:
> {quote}
> Exception in thread "main" 
> org.apache.logging.log4j.core.config.ConfigurationException: No name 
> attribute provided for Logger org
>   at 
> org.apache.logging.log4j.core.config.properties.PropertiesConfigurationBuilder.createLogger(PropertiesConfigurationBuilder.java:215)
>   at 
> org.apache.logging.log4j.core.config.properties.PropertiesConfigurationBuilder.build(PropertiesConfigurationBuilder.java:140)
>   at 
> org.apache.logging.log4j.core.config.properties.PropertiesConfigurationFactory.getConfiguration(PropertiesConfigurationFactory.java:52)
>   at 
> org.apache.logging.log4j.core.config.properties.PropertiesConfigurationFactory.getConfiguration(PropertiesConfigurationFactory.java:34)
>   at 
> org.apache.logging.log4j.core.config.ConfigurationFactory$Factory.getConfiguration(ConfigurationFactory.java:510)
>   at 
> org.apache.logging.log4j.core.config.ConfigurationFactory$Factory.getConfiguration(ConfigurationFactory.java:450)
>   at 
> org.apache.logging.log4j.core.config.ConfigurationFactory.getConfiguration(ConfigurationFactory.java:257)
>   at 
> org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:560)
>   at 
> org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:577)
>   at 
> org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:212)
>   at 
> org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:152)
>   at 
> org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:45)
>   at org.apache.logging.log4j.LogManager.getContext(LogManager.java:194)
>   at 
> org.apache.logging.log4j.spi.AbstractLoggerAdapter.getContext(AbstractLoggerAdapter.java:103)
>   at 
> org.apache.logging.log4j.jcl.LogAdapter.getContext(LogAdapter.java:39)
>   at 
> org.apache.logging.log4j.spi.AbstractLoggerAdapter.getLogger(AbstractLoggerAdapter.java:42)
>   at 
> org.apache.logging.log4j.jcl.LogFactoryImpl.getInstance(LogFactoryImpl.java:40)
>   at 
> org.apache.logging.log4j.jcl.LogFactoryImpl.getInstance(LogFactoryImpl.java:55)
>   at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:655)
>   at 
> org.springframework.context.support.AbstractApplicationContext.(AbstractApplicationContext.java:159)
>   at 
> org.springframework.context.support.AbstractApplicationContext.(AbstractApplicationContext.java:223)
>   at 
> org.springframework.context.support.AbstractRefreshableApplicationContext.(AbstractRefreshableApplicationContext.java:88)
>   at 
> org.springframework.context.support.AbstractRefreshableConfigApplicationContext.(AbstractRefreshableConfigApplicationContext.java:58)
>   at 
> org.springframework.context.support.AbstractXmlApplicationContext.(AbstractXmlApplicationContext.java:61)
>   at 
> org.springframework.context.support.ClassPathXmlApplicationContext.(ClassPathXmlApplicationContext.java:136)
>   at 
> org.springframework.context.support.ClassPathXmlApplicationContext.(ClassPathXmlApplicationContext.java:83)
> x.y.z.Start.main(Start.java:12)
> {quote}
> The parameter "key" has the value "org" and the parameter properties has the 
> value {code}{activiti.engine.impl.level=info, 
>

[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 confused. The error means that it found something like:
{code}
logger.org.level = info
logger.org.appenderRef.stdout.ref = STDOUT
{code}

but didn't find
{code}
logger.org.name = org.apache
{code}

But the sample above only shows the rootLogger, which doesn't even use the 
createLogger method.



was (Author: ralph.go...@dslextreme.com):
I'm a bit confused. The error means that it found something like:
{code}
logger.org.level = info
logger.appenderRef.stdout.ref = STDOUT
{code}

but didn't find
{code}
logger.org.name = org.apache
{code}

But the sample above only shows the rootLogger, which doesn't even use the 
createLogger method.


> org.apache.logging.log4j.core.config.ConfigurationException: No name 
> attribute provided for Logger org
> --
>
> Key: LOG4J2-1402
> URL: https://issues.apache.org/jira/browse/LOG4J2-1402
> Project: Log4j 2
>  Issue Type: Bug
>  Components: JCL Bridge
>Affects Versions: 2.6
>Reporter: Pascal Schumacher
>
> After upgrading log4j2 from 2.5 to 2.6 I get the following exception:
> {quote}
> Exception in thread "main" 
> org.apache.logging.log4j.core.config.ConfigurationException: No name 
> attribute provided for Logger org
>   at 
> org.apache.logging.log4j.core.config.properties.PropertiesConfigurationBuilder.createLogger(PropertiesConfigurationBuilder.java:215)
>   at 
> org.apache.logging.log4j.core.config.properties.PropertiesConfigurationBuilder.build(PropertiesConfigurationBuilder.java:140)
>   at 
> org.apache.logging.log4j.core.config.properties.PropertiesConfigurationFactory.getConfiguration(PropertiesConfigurationFactory.java:52)
>   at 
> org.apache.logging.log4j.core.config.properties.PropertiesConfigurationFactory.getConfiguration(PropertiesConfigurationFactory.java:34)
>   at 
> org.apache.logging.log4j.core.config.ConfigurationFactory$Factory.getConfiguration(ConfigurationFactory.java:510)
>   at 
> org.apache.logging.log4j.core.config.ConfigurationFactory$Factory.getConfiguration(ConfigurationFactory.java:450)
>   at 
> org.apache.logging.log4j.core.config.ConfigurationFactory.getConfiguration(ConfigurationFactory.java:257)
>   at 
> org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:560)
>   at 
> org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:577)
>   at 
> org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:212)
>   at 
> org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:152)
>   at 
> org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:45)
>   at org.apache.logging.log4j.LogManager.getContext(LogManager.java:194)
>   at 
> org.apache.logging.log4j.spi.AbstractLoggerAdapter.getContext(AbstractLoggerAdapter.java:103)
>   at 
> org.apache.logging.log4j.jcl.LogAdapter.getContext(LogAdapter.java:39)
>   at 
> org.apache.logging.log4j.spi.AbstractLoggerAdapter.getLogger(AbstractLoggerAdapter.java:42)
>   at 
> org.apache.logging.log4j.jcl.LogFactoryImpl.getInstance(LogFactoryImpl.java:40)
>   at 
> org.apache.logging.log4j.jcl.LogFactoryImpl.getInstance(LogFactoryImpl.java:55)
>   at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:655)
>   at 
> org.springframework.context.support.AbstractApplicationContext.(AbstractApplicationContext.java:159)
>   at 
> org.springframework.context.support.AbstractApplicationContext.(AbstractApplicationContext.java:223)
>   at 
> org.springframework.context.support.AbstractRefreshableApplicationContext.(AbstractRefreshableApplicationContext.java:88)
>   at 
> org.springframework.context.support.AbstractRefreshableConfigApplicationContext.(AbstractRefreshableConfigApplicationContext.java:58)
>   at 
> org.springframework.context.support.AbstractXmlApplicationContext.(AbstractXmlApplicationContext.java:61)
>   at 
> org.springframework.context.support.ClassPathXmlApplicationContext.(ClassPathXmlApplicationContext.java:136)
>   at 
> org.springframework.context.support.ClassPathXmlApplicationContext.(ClassPathXmlApplicationContext.java:83)
> x.y.z.Start.main(Start.java:12)
> {quote}
> The parameter "key" has the value "org" and the parameter properties ha

[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 like:
{code}
logger.org.level = info
logger.appenderRef.stdout.ref = STDOUT
{code}

but didn't find
{code}
logger.org.name = org.apache
{code}

But the sample above only shows the rootLogger, which doesn't even use the 
createLogger method.


> org.apache.logging.log4j.core.config.ConfigurationException: No name 
> attribute provided for Logger org
> --
>
> Key: LOG4J2-1402
> URL: https://issues.apache.org/jira/browse/LOG4J2-1402
> Project: Log4j 2
>  Issue Type: Bug
>  Components: JCL Bridge
>Affects Versions: 2.6
>Reporter: Pascal Schumacher
>
> After upgrading log4j2 from 2.5 to 2.6 I get the following exception:
> {quote}
> Exception in thread "main" 
> org.apache.logging.log4j.core.config.ConfigurationException: No name 
> attribute provided for Logger org
>   at 
> org.apache.logging.log4j.core.config.properties.PropertiesConfigurationBuilder.createLogger(PropertiesConfigurationBuilder.java:215)
>   at 
> org.apache.logging.log4j.core.config.properties.PropertiesConfigurationBuilder.build(PropertiesConfigurationBuilder.java:140)
>   at 
> org.apache.logging.log4j.core.config.properties.PropertiesConfigurationFactory.getConfiguration(PropertiesConfigurationFactory.java:52)
>   at 
> org.apache.logging.log4j.core.config.properties.PropertiesConfigurationFactory.getConfiguration(PropertiesConfigurationFactory.java:34)
>   at 
> org.apache.logging.log4j.core.config.ConfigurationFactory$Factory.getConfiguration(ConfigurationFactory.java:510)
>   at 
> org.apache.logging.log4j.core.config.ConfigurationFactory$Factory.getConfiguration(ConfigurationFactory.java:450)
>   at 
> org.apache.logging.log4j.core.config.ConfigurationFactory.getConfiguration(ConfigurationFactory.java:257)
>   at 
> org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:560)
>   at 
> org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:577)
>   at 
> org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:212)
>   at 
> org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:152)
>   at 
> org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:45)
>   at org.apache.logging.log4j.LogManager.getContext(LogManager.java:194)
>   at 
> org.apache.logging.log4j.spi.AbstractLoggerAdapter.getContext(AbstractLoggerAdapter.java:103)
>   at 
> org.apache.logging.log4j.jcl.LogAdapter.getContext(LogAdapter.java:39)
>   at 
> org.apache.logging.log4j.spi.AbstractLoggerAdapter.getLogger(AbstractLoggerAdapter.java:42)
>   at 
> org.apache.logging.log4j.jcl.LogFactoryImpl.getInstance(LogFactoryImpl.java:40)
>   at 
> org.apache.logging.log4j.jcl.LogFactoryImpl.getInstance(LogFactoryImpl.java:55)
>   at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:655)
>   at 
> org.springframework.context.support.AbstractApplicationContext.(AbstractApplicationContext.java:159)
>   at 
> org.springframework.context.support.AbstractApplicationContext.(AbstractApplicationContext.java:223)
>   at 
> org.springframework.context.support.AbstractRefreshableApplicationContext.(AbstractRefreshableApplicationContext.java:88)
>   at 
> org.springframework.context.support.AbstractRefreshableConfigApplicationContext.(AbstractRefreshableConfigApplicationContext.java:58)
>   at 
> org.springframework.context.support.AbstractXmlApplicationContext.(AbstractXmlApplicationContext.java:61)
>   at 
> org.springframework.context.support.ClassPathXmlApplicationContext.(ClassPathXmlApplicationContext.java:136)
>   at 
> org.springframework.context.support.ClassPathXmlApplicationContext.(ClassPathXmlApplicationContext.java:83)
> x.y.z.Start.main(Start.java:12)
> {quote}
> The parameter "key" has the value "org" and the parameter properties has the 
> value {code}{activiti.engine.impl.level=info, 
> activiti.engine.impl.name=org.activiti.engine.impl}{code}
> The log4j2.properties in use:
> {code}
> # Root logger option
> rootLogger.level = info
> rootLogger.appenderRefs = stdout
> rootLogger.appenderRef.stdout.ref = STDOUT
> # Redirect log messages to console
> appenders = stdout
> appender.stdout.type = Console
>

[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 and a createRootLogger 
method. We need to determine why createLogger is being called instead of 
createRootLogger.

> org.apache.logging.log4j.core.config.ConfigurationException: No name 
> attribute provided for Logger org
> --
>
> Key: LOG4J2-1402
> URL: https://issues.apache.org/jira/browse/LOG4J2-1402
> Project: Log4j 2
>  Issue Type: Bug
>  Components: JCL Bridge
>Affects Versions: 2.6
>Reporter: Pascal Schumacher
>
> After upgrading log4j2 from 2.5 to 2.6 I get the following exception:
> {quote}
> Exception in thread "main" 
> org.apache.logging.log4j.core.config.ConfigurationException: No name 
> attribute provided for Logger org
>   at 
> org.apache.logging.log4j.core.config.properties.PropertiesConfigurationBuilder.createLogger(PropertiesConfigurationBuilder.java:215)
>   at 
> org.apache.logging.log4j.core.config.properties.PropertiesConfigurationBuilder.build(PropertiesConfigurationBuilder.java:140)
>   at 
> org.apache.logging.log4j.core.config.properties.PropertiesConfigurationFactory.getConfiguration(PropertiesConfigurationFactory.java:52)
>   at 
> org.apache.logging.log4j.core.config.properties.PropertiesConfigurationFactory.getConfiguration(PropertiesConfigurationFactory.java:34)
>   at 
> org.apache.logging.log4j.core.config.ConfigurationFactory$Factory.getConfiguration(ConfigurationFactory.java:510)
>   at 
> org.apache.logging.log4j.core.config.ConfigurationFactory$Factory.getConfiguration(ConfigurationFactory.java:450)
>   at 
> org.apache.logging.log4j.core.config.ConfigurationFactory.getConfiguration(ConfigurationFactory.java:257)
>   at 
> org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:560)
>   at 
> org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:577)
>   at 
> org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:212)
>   at 
> org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:152)
>   at 
> org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:45)
>   at org.apache.logging.log4j.LogManager.getContext(LogManager.java:194)
>   at 
> org.apache.logging.log4j.spi.AbstractLoggerAdapter.getContext(AbstractLoggerAdapter.java:103)
>   at 
> org.apache.logging.log4j.jcl.LogAdapter.getContext(LogAdapter.java:39)
>   at 
> org.apache.logging.log4j.spi.AbstractLoggerAdapter.getLogger(AbstractLoggerAdapter.java:42)
>   at 
> org.apache.logging.log4j.jcl.LogFactoryImpl.getInstance(LogFactoryImpl.java:40)
>   at 
> org.apache.logging.log4j.jcl.LogFactoryImpl.getInstance(LogFactoryImpl.java:55)
>   at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:655)
>   at 
> org.springframework.context.support.AbstractApplicationContext.(AbstractApplicationContext.java:159)
>   at 
> org.springframework.context.support.AbstractApplicationContext.(AbstractApplicationContext.java:223)
>   at 
> org.springframework.context.support.AbstractRefreshableApplicationContext.(AbstractRefreshableApplicationContext.java:88)
>   at 
> org.springframework.context.support.AbstractRefreshableConfigApplicationContext.(AbstractRefreshableConfigApplicationContext.java:58)
>   at 
> org.springframework.context.support.AbstractXmlApplicationContext.(AbstractXmlApplicationContext.java:61)
>   at 
> org.springframework.context.support.ClassPathXmlApplicationContext.(ClassPathXmlApplicationContext.java:136)
>   at 
> org.springframework.context.support.ClassPathXmlApplicationContext.(ClassPathXmlApplicationContext.java:83)
> x.y.z.Start.main(Start.java:12)
> {quote}
> The parameter "key" has the value "org" and the parameter properties has the 
> value {code}{activiti.engine.impl.level=info, 
> activiti.engine.impl.name=org.activiti.engine.impl}{code}
> The log4j2.properties in use:
> {code}
> # Root logger option
> rootLogger.level = info
> rootLogger.appenderRefs = stdout
> rootLogger.appenderRef.stdout.ref = STDOUT
> # Redirect log messages to console
> appenders = stdout
> appender.stdout.type = Console
> appender.stdout.name = STDOUT
> appender.stdout.layout.type = PatternLayout
> appender.stdout.layout.pattern = %d %-5p [%t] %

[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 if this has anything to do with the problem, but 
LoggerRegistry.getOrCreateInnerMap is not thread-safe. It should be using 
putIfAbsent but if it does it will break the WeakMapFactory since that doesn't 
use a ConcurrentMap.

I am also having a hard time understanding how this message is even possible. 
First we obtain a logger from the registry using the logger name and message 
factory as keys.  Then we call AbstractLogger.checkMessageFactgory to verify 
that the Logger returned has the same factory as what was requested.  Under 
what circumstances would the LoggerRegistry return a Logger using a different 
MessageFactory?


was (Author: ralph.go...@dslextreme.com):
I don't know if this has anything to do with the problem, but 
LoggerRegistry.getOrCreateInnerMap is not thread-safe. It should be using 
putIfAbsent but if it does it will break the WeakMapFactory since that doesn't 
use a ConcurrentMap.

> Logger cache does not account for message factory
> -
>
> Key: LOG4J2-1180
> URL: https://issues.apache.org/jira/browse/LOG4J2-1180
> Project: Log4j 2
>  Issue Type: Bug
>  Components: API
>Affects Versions: 2.4.1
>Reporter: Gary Gregory
>Assignee: Gary Gregory
> Fix For: 2.5
>
> Attachments: LOG4J2-1180.diff
>
>
> The Logger cache does not account for a logger's message factory.
> If you call {{LogManager.getLogger(Class|Object|String, MessageFactory)}} and 
> then call a getLogger() API again with the same {{Class|Object|String}} a 
> different message factory, you get the Logger that was first created which 
> means you will not get the proper formatted messages.
> For example:
> {code:java}
> Logger loggerA1 = LogManager.getLogger("A", messageFactory1);
> Logger loggerA2 = LogManager.getLogger("A", messageFactory2);
> {code}
> loggerA1 is the same as loggerA2.
> This is a problem if two unrelated code bases (jars) both the same Logger 
> names|objects|classes.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

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