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

[ https://issues.apache.org/jira/browse/LOG4J2-907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15327037#comment-15327037 ] K P commented on LOG4J2-907: This would be a very welcome (actually needed) addition. It was

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

[ https://issues.apache.org/jira/browse/LOG4J2-1185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15327047#comment-15327047 ] K P commented on LOG4J2-1185: - This was indeed possible in log4j 1.x (actually, we also rely

[jira] [Comment Edited] (LOG4J2-907) Log4j2 rolling policy

[ https://issues.apache.org/jira/browse/LOG4J2-907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15327037#comment-15327037 ] K P edited comment on LOG4J2-907 at 6/13/16 9:30 AM: - This would be a

[jira] [Commented] (LOG4J2-1027) fileName variables not re-resolved at file rollover

[ https://issues.apache.org/jira/browse/LOG4J2-1027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15327070#comment-15327070 ] K P commented on LOG4J2-1027: - This was possible in log4j 1.x http://stackoverflow.com/quest

[jira] [Commented] (LOG4J2-239) RollingFileAppender should support logging directly to the file referenced in the filePattern.

[ https://issues.apache.org/jira/browse/LOG4J2-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15327075#comment-15327075 ] K P commented on LOG4J2-239: This would indeed help for a log4j 1.x feature that is missing in

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

[ https://issues.apache.org/jira/browse/LOG4J2-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15327074#comment-15327074 ] Mikael Ståldal commented on LOG4J2-1395: I added a caveat in the docs about this.

[jira] [Created] (LOG4J2-1426) Rollover should occur when server shutdown

karunakaran created LOG4J2-1426: --- Summary: Rollover should occur when server shutdown Key: LOG4J2-1426 URL: https://issues.apache.org/jira/browse/LOG4J2-1426 Project: Log4j 2 Issue Type: New Fe

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

[ https://issues.apache.org/jira/browse/LOG4J2-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15327115#comment-15327115 ] Remko Popma commented on LOG4J2-1395: - Yes, I'm okay to merge this into master. The

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

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

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

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

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

[ https://issues.apache.org/jira/browse/LOG4J2-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15327202#comment-15327202 ] Remko Popma commented on LOG4J2-1395: - Ralph, why do you think this may not work in o

[jira] [Commented] (LOG4J2-1419) Memory leak on tomcat shutdown

[ https://issues.apache.org/jira/browse/LOG4J2-1419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15327223#comment-15327223 ] Remko Popma commented on LOG4J2-1419: - [~vasiapupkin] I've tried to trace it down in

[jira] [Updated] (LOG4J2-1426) How to rotate logs on every server shutdown in log4j2

[ https://issues.apache.org/jira/browse/LOG4J2-1426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] karunakaran updated LOG4J2-1426: Summary: How to rotate logs on every server shutdown in log4j2 (was: Rollover should occur when se

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

rabee abif created LOG4J2-1427: -- Summary: zipping files not working when file is created from appender used in root logger. Key: LOG4J2-1427 URL: https://issues.apache.org/jira/browse/LOG4J2-1427 Project

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

[ https://issues.apache.org/jira/browse/LOG4J2-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15327282#comment-15327282 ] Mikael Ståldal commented on LOG4J2-1395: Just tried on Linux, and I cannot see an

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

[ https://issues.apache.org/jira/browse/LOG4J2-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15327280#comment-15327280 ] Mikael Ståldal commented on LOG4J2-1395: ConsoleAppender does not respect `System

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

[ https://issues.apache.org/jira/browse/LOG4J2-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15327280#comment-15327280 ] Mikael Ståldal edited comment on LOG4J2-1395 at 6/13/16 12:46 PM: -

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

[ https://issues.apache.org/jira/browse/LOG4J2-1426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] karunakaran updated LOG4J2-1426: Summary: Log Rotation or rollover on every server shutdown in log4j2 (was: How to rotate logs on e

[jira] [Commented] (LOG4J2-1419) Memory leak on tomcat shutdown

[ https://issues.apache.org/jira/browse/LOG4J2-1419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15327396#comment-15327396 ] Remko Popma commented on LOG4J2-1419: - I committed code to master that will print a s

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

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

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

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

[jira] [Commented] (LOG4J2-1419) Memory leak on tomcat shutdown

[ https://issues.apache.org/jira/browse/LOG4J2-1419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15327435#comment-15327435 ] Vasia commented on LOG4J2-1419: --- Surely I will do it tomorrow > Memory leak on tomcat shut

Jenkins build is unstable: Log4j 2.x #2027

See - 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&focusedCommentId=15327479#comment-15327479 ] Matt Sicker commented on LOG4J2-1395: - Do you have access to any alternative JVMs or

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

[ https://issues.apache.org/jira/browse/LOG4J2-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15327511#comment-15327511 ] Mikael Ståldal commented on LOG4J2-1395: OK, added some documentation about that

log4j2 evangelism

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

Re: log4j2 evangelism

I've noticed a big problem is that people don't realize you can use log4j-api the same way you would normally use slf4j-api. Plus it doesn't help that tons of Apache projects are using SLF4J which makes it a sort of tacit endorsement of it over log4j-api. Some attention on sites like Reddit or Sta

Re: log4j2 evangelism

Oh, another thing that would help is doing presentations on log4j. Myself and a few others run a virtual java user group (and an in-person one) in Illinois that accepts presenters from around the world for instance. Then there's the London VirtualJUG as well which is super popular. Plus any local J

Fwd: logging-log4j2 git commit: LOG4J2-1419 added system properties switch to enable locating where new LoggerContext is started

Shouldn't this be documented? Gary -- Forwarded message -- From: Date: Jun 13, 2016 6:43 AM Subject: logging-log4j2 git commit: LOG4J2-1419 added system properties switch to enable locating where new LoggerContext is started To: Cc: Repository: logging-log4j2 Updated Branches:

Re: log4j2 evangelism

I've done an in person preso at two JUG in Southern California that were well received. I did not think of recording them for YouTube though. Promoting within Apache and especially new projects would help IMO. I've also seen that folks do not know that Log4j 2 has a new modern architecture with a

Re: logging-log4j2 git commit: LOG4J2-1419 added system properties switch to enable locating where new LoggerContext is started

Maybe I was being lazy :-) but this change is mostly targeted to fixing/investigating LOG4J2-1419. I don't imagine many people would need this. I could be wrong... We can add this to the list of documented system properties to configure Log4j if you think it is generally useful. On Mon, Jun 13, 20

Jenkins build is back to stable : Log4j 2.x #2028

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

Re: log4j2 evangelism

I've already asked Ralph and now Gary, but let me pose the question openly instead. Would any of you be interested in doing an online presentation for Illinois JUG? Here's our meetup group: < http://www.meetup.com/illinoisJUGvirtual/>. I did a lightning talk about async logging (and a little bit on

Re: log4j2 evangelism

And to make things worse, some Apache projects (in particular Zookeeper) even uses SLF4J with a specific binding (Log4j 1 in this case) as a dependency, which makes it a P.I.T.A. to use it with Log4j 2 (or with any other logging framework such as Logback for that matter). On Mon, Jun 13, 2016 at 4

Re: logging-log4j2 git commit: LOG4J2-1419 added system properties switch to enable locating where new LoggerContext is started

Who knows who might find this helpful. So maybe yeah, it should be documented anyway? Slightly confusing: the prop has trace in the name but the level is debug. I know we are logging a stack _trace_ of course... but it feel weird when I look at the patch. Gary On Jun 13, 2016 8:09 AM, "Remko Popm

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

[ https://issues.apache.org/jira/browse/LOG4J2-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15327612#comment-15327612 ] Mikael Ståldal commented on LOG4J2-1395: I added this caveat in docs: Output wil

Re: logging-log4j2 git commit: LOG4J2-1419 added system properties switch to enable locating where new LoggerContext is started

You're right. I changed the name to log4j.LoggerContext.stacktrace.on.start On Tue, Jun 14, 2016 at 12:19 AM, Gary Gregory wrote: > Who knows who might find this helpful. So maybe yeah, it should be > documented anyway? > > Slightly confusing: the prop has trace in the name but the level is debu

[jira] [Commented] (LOG4J2-1419) Memory leak on tomcat shutdown

[ https://issues.apache.org/jira/browse/LOG4J2-1419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15327621#comment-15327621 ] Remko Popma commented on LOG4J2-1419: - After feedback from the Log4j community I chan

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

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

Re: log4j2 evangelism

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

Re: log4j2 evangelism

On Mon, Jun 13, 2016 at 10:03 AM, Ralph Goers 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

[jira] [Created] (LOG4J2-1428) Scala friedly overloading in MessageFactory(2)

Mikael Ståldal created LOG4J2-1428: -- Summary: Scala friedly overloading in MessageFactory(2) Key: LOG4J2-1428 URL: https://issues.apache.org/jira/browse/LOG4J2-1428 Project: Log4j 2 Issue Ty

Re: log4j2 evangelism

What would be neat would be a tool like this one: http://logback.qos.ch/translator/ On 13 June 2016 at 12:08, Gary Gregory wrote: > On Mon, Jun 13, 2016 at 10:03 AM, Ralph Goers > wrote: > >> The biggest complaints we seem to be getting are about the effort in >> transitioning from Log4j 1.x to

Re: log4j2 evangelism

http://log4j-props2xml.appspot.com/ https://github.com/jroyals/log4j-properties-converter/ https://github.com/mulesoft-labs/log4j2-migrator Ralph

Re: log4j2 evangelism

Shall we add links to those on our site? On 13 June 2016 at 12:57, Ralph Goers wrote: > http://log4j-props2xml.appspot.com/ > https://github.com/jroyals/log4j-properties-converter/ > > https://github.com/mulesoft-labs/log4j2-migrator > > Ralph > > > On Jun 13, 2016, at 10:37 AM, Matt Sicker wro

[jira] [Commented] (LOG4J2-1428) Scala friedly overloading in MessageFactory(2)

[ https://issues.apache.org/jira/browse/LOG4J2-1428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15327888#comment-15327888 ] Mikael Ståldal commented on LOG4J2-1428: An easy way to fix this would be to rena

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

[ https://issues.apache.org/jira/browse/LOG4J2-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15327893#comment-15327893 ] Mikael Ståldal commented on LOG4J2-1395: OK, what about this: Write directly to

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

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

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

[ https://issues.apache.org/jira/browse/LOG4J2-1181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal updated LOG4J2-1181: --- Affects Version/s: 2.6.1 > Scala wrapper for Log4j 2 API > - > >

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

[ https://issues.apache.org/jira/browse/LOG4J2-1181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15328081#comment-15328081 ] Mikael Ståldal commented on LOG4J2-1181: I am trying to keep this updated with ne

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

[ https://issues.apache.org/jira/browse/LOG4J2-1181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15328217#comment-15328217 ] Matt Sicker commented on LOG4J2-1181: - I think it would make most sense to use the le

[jira] [Commented] (LOG4J2-1428) Scala friedly overloading in MessageFactory(2)

[ https://issues.apache.org/jira/browse/LOG4J2-1428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15328250#comment-15328250 ] Gary Gregory commented on LOG4J2-1428: -- Gross! > Scala friedly overloading in Messa

Jenkins build became unstable: Log4j 2.x #2030

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

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

[ https://issues.apache.org/jira/browse/LOG4J2-1181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15328462#comment-15328462 ] Remko Popma commented on LOG4J2-1181: - For the Scala API it would make sense to have

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

[ https://issues.apache.org/jira/browse/LOG4J2-1181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15328471#comment-15328471 ] Gary Gregory commented on LOG4J2-1181: -- Did we blow it when we unrolled all of the L

[jira] [Commented] (LOG4J2-1428) Scala friedly overloading in MessageFactory(2)

[ https://issues.apache.org/jira/browse/LOG4J2-1428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15328479#comment-15328479 ] Remko Popma commented on LOG4J2-1428: - Ouch! The problem is that we have already publ

Jenkins build is back to stable : Log4j 2.x #2031

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

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

[ https://issues.apache.org/jira/browse/LOG4J2-1181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15328616#comment-15328616 ] Remko Popma commented on LOG4J2-1181: - No I don't think so. We considered that when

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

[ https://issues.apache.org/jira/browse/LOG4J2-1181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15328617#comment-15328617 ] Remko Popma commented on LOG4J2-1181: - No I don't think so. We considered that when

[jira] [Issue Comment Deleted] (LOG4J2-1181) Scala wrapper for Log4j 2 API

[ https://issues.apache.org/jira/browse/LOG4J2-1181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-1181: Comment: was deleted (was: No I don't think so. We considered that when the CharSequence API was

Re: logging-log4j2 git commit: Fix FQCN for Clock in async manual

Nice find! Sent from my iPhone > On 2016/06/14, at 6:00, mattsic...@apache.org wrote: > > Repository: logging-log4j2 > Updated Branches: > refs/heads/master 0cf1df05e -> 3ccc6531e > > > Fix FQCN for Clock in async manual > > > Project: http://git-wip-us.apache.org/repos/asf/logging-log4j2/r

Re: logging-log4j2 git commit: Fix FQCN for Clock in async manual

I've been migrating to async logging at work, so I've kinda been looking closely. ;) On 13 June 2016 at 19:04, Remko Popma wrote: > Nice find! > > Sent from my iPhone > > > On 2016/06/14, at 6:00, mattsic...@apache.org wrote: > > > > Repository: logging-log4j2 > > Updated Branches: > > refs/hea