[jira] [Updated] (LOG4J2-467) Thread name caching in async logger incompatible with use of Thread.setName()

[ https://issues.apache.org/jira/browse/LOG4J2-467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-467: --- Attachment: PerfTestDriver.java Gary, I've tested the performance difference like you asked. I used t

[jira] [Comment Edited] (LOG4J2-467) Thread name caching in async logger incompatible with use of Thread.setName()

[ https://issues.apache.org/jira/browse/LOG4J2-467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13861384#comment-13861384 ] Remko Popma edited comment on LOG4J2-467 at 1/3/14 9:52 AM: Ga

[jira] [Resolved] (LOG4J2-467) Thread name caching in async logger incompatible with use of Thread.setName()

[ https://issues.apache.org/jira/browse/LOG4J2-467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-467. Resolution: Fixed Fix Version/s: 2.0-rc1 Assignee: Remko Popma Anthony, I've added

[jira] [Commented] (LOG4J2-479) Use of InheritableThreadLocal in Map ThreadContext is dangerous and unhelpful

[ https://issues.apache.org/jira/browse/LOG4J2-479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13861501#comment-13861501 ] Remko Popma commented on LOG4J2-479: Hmm... I'm not sure how to proceed here. On the

[jira] [Commented] (LOG4J2-479) Use of InheritableThreadLocal in Map ThreadContext is dangerous and unhelpful

[ https://issues.apache.org/jira/browse/LOG4J2-479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13861507#comment-13861507 ] MK commented on LOG4J2-479: --- One other thing I want to stress, is that missing thread context is

[jira] [Resolved] (LOG4J2-482) The attribute of Route to refer to an appender is "ref" not "AppenderRef"

[ https://issues.apache.org/jira/browse/LOG4J2-482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-482. Resolution: Fixed Fix Version/s: 2.0-rc1 Thanks for pointing this out. I've changed the docu

[jira] [Updated] (LOG4J2-471) toString methods that perform logging can deadlock AsyncLogger

[ https://issues.apache.org/jira/browse/LOG4J2-471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-471: --- Fix Version/s: 2.0 > toString methods that perform logging can deadlock AsyncLogger > ---

[jira] [Commented] (LOG4J2-462) LevelPatternConverter.format may throw NPE

[ https://issues.apache.org/jira/browse/LOG4J2-462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13861588#comment-13861588 ] Remko Popma commented on LOG4J2-462: Daisuke, both this issue and LOG4J2-465 occur bec

Re: Next release of 2.0

I'm not sure what policy WRT binary and source compatibility we have in log4j 1 and 2. Over in Commons, if you break BC, in general, that means a package name change and a Maven name change, for example from o.a.commons.lang to lang3. This is using the Clirr report to check for errors. There are ex

Re: Next release of 2.0

On Fri, Jan 3, 2014 at 11:26 AM, Gary Gregory wrote: > I'm not sure what policy WRT binary and source compatibility we have in > log4j 1 and 2. Over in Commons, if you break BC, in general, that means a > package name change and a Maven name change, for example from > o.a.commons.lang to lang3. Th

[jira] [Commented] (LOG4J2-482) The attribute of Route to refer to an appender is "ref" not "AppenderRef"

[ https://issues.apache.org/jira/browse/LOG4J2-482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13861641#comment-13861641 ] Gary Gregory commented on LOG4J2-482: - I would vote for whatever is _consistent_ with

[jira] [Commented] (LOG4J2-462) LevelPatternConverter.format may throw NPE

[ https://issues.apache.org/jira/browse/LOG4J2-462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13861639#comment-13861639 ] Gary Gregory commented on LOG4J2-462: - I like the idea of using {{Level.OFF}}, it is O

[jira] [Commented] (LOG4J2-467) Thread name caching in async logger incompatible with use of Thread.setName()

[ https://issues.apache.org/jira/browse/LOG4J2-467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13861644#comment-13861644 ] Gary Gregory commented on LOG4J2-467: - Thank you for the update Remko. Interesting num

[jira] [Commented] (LOG4J2-479) Use of InheritableThreadLocal in Map ThreadContext is dangerous and unhelpful

[ https://issues.apache.org/jira/browse/LOG4J2-479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13861649#comment-13861649 ] Ralph Goers commented on LOG4J2-479: Log4j 1.x used an InheritableThreadLocal for the

[jira] [Commented] (LOG4J2-462) LevelPatternConverter.format may throw NPE

[ https://issues.apache.org/jira/browse/LOG4J2-462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13861652#comment-13861652 ] Ralph Goers commented on LOG4J2-462: Yes, that make sense to me as well. > LevelPatte

Re: Next release of 2.0

What are contemplating changing in log4j-api? Ralph On Jan 3, 2014, at 8:28 AM, Gary Gregory wrote: > On Fri, Jan 3, 2014 at 11:26 AM, Gary Gregory wrote: > I'm not sure what policy WRT binary and source compatibility we have in log4j > 1 and 2. Over in Commons, if you break BC, in general,

Re: Next release of 2.0

IMO, being unable to change the API in log4j1 due to compatibility concerns is what caused development of log4j to essentially stop (other than the occasional bug fix commit). I'd hate for us to end up in the same place with log4j2. Scott On 1/3/14, Ralph Goers wrote: > What are contemplating c

[jira] [Commented] (LOG4J2-479) Use of InheritableThreadLocal in Map ThreadContext is dangerous and unhelpful

[ https://issues.apache.org/jira/browse/LOG4J2-479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13861671#comment-13861671 ] MK commented on LOG4J2-479: --- I'll take a property > Use of InheritableThreadLocal in Map Thread

Re: Next release of 2.0

The point of separating the API from the implementation was to try to address some of that. In Log4j 1 it isn’t clear at all where the public API stops. Even though the API is separate in Log4j 2 it is clear that we will want to be careful changing things like the Layout and Appender interface

[jira] [Commented] (LOG4J2-479) Use of InheritableThreadLocal in Map ThreadContext is dangerous and unhelpful

[ https://issues.apache.org/jira/browse/LOG4J2-479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13861703#comment-13861703 ] Nick Williams commented on LOG4J2-479: -- In my opinion, we need to take one of two pat

[jira] [Comment Edited] (LOG4J2-479) Use of InheritableThreadLocal in Map ThreadContext is dangerous and unhelpful

[ https://issues.apache.org/jira/browse/LOG4J2-479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13861703#comment-13861703 ] Nick Williams edited comment on LOG4J2-479 at 1/3/14 5:40 PM: --

Re: Next release of 2.0

On Fri, Jan 3, 2014 at 11:46 AM, Ralph Goers wrote: > What are contemplating changing in log4j-api? > I'm knee deep in some other project ATM and cannot think of anything in log4j-api, but in the guts, maybe for appenders and layouts. I'll see the light of day in a few days... Gary Ralph On

[jira] [Closed] (LOG4J2-467) Thread name caching in async logger incompatible with use of Thread.setName()

[ https://issues.apache.org/jira/browse/LOG4J2-467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baldocchi closed LOG4J2-467. Using a single-threaded executor, thread names in my test log output change when the Runnable

[jira] [Created] (LOG4J2-484) log4j2 and ServletContextListeners

Giovanni Mondo created LOG4J2-484: - Summary: log4j2 and ServletContextListeners Key: LOG4J2-484 URL: https://issues.apache.org/jira/browse/LOG4J2-484 Project: Log4j 2 Issue Type: Question

[jira] [Updated] (LOG4J2-484) log4j2 and ServletContextListeners

[ https://issues.apache.org/jira/browse/LOG4J2-484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giovanni Mondo updated LOG4J2-484: -- Attachment: MavenWeb.zip > log4j2 and ServletContextListeners > ---

[jira] [Updated] (LOG4J2-484) log4j2 and ServletContextListeners

[ https://issues.apache.org/jira/browse/LOG4J2-484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giovanni Mondo updated LOG4J2-484: -- Description: Logging configuration is done by two config file: WEB-INF/classes/log4j2.xml log

[jira] [Updated] (LOG4J2-484) log4j2 and ServletContextListeners

[ https://issues.apache.org/jira/browse/LOG4J2-484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giovanni Mondo updated LOG4J2-484: -- Description: Logging configuration is done by two config file: WEB-INF/classes/log4j2.xml log

Re: Next release of 2.0

On 3 Jan 2014, at 18:02, Scott Deboy wrote: IMO, being unable to change the API in log4j1 due to compatibility concerns is what caused development of log4j to essentially stop (other than the occasional bug fix commit). I'd hate for us to end up in the same place with log4j2. +1 I was not th

[jira] [Commented] (LOG4J2-467) Thread name caching in async logger incompatible with use of Thread.setName()

[ https://issues.apache.org/jira/browse/LOG4J2-467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862126#comment-13862126 ] Remko Popma commented on LOG4J2-467: Gary, after rebooting my windows laptop I'm getti

[jira] [Reopened] (LOG4J2-482) The attribute of Route to refer to an appender is "ref" not "AppenderRef"

[ https://issues.apache.org/jira/browse/LOG4J2-482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma reopened LOG4J2-482: Assignee: Remko Popma (Reopening issue) Now that we are talking about coming out of beta on the m

[jira] [Commented] (LOG4J2-467) Thread name caching in async logger incompatible with use of Thread.setName()

[ https://issues.apache.org/jira/browse/LOG4J2-467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862187#comment-13862187 ] Scott Deboy commented on LOG4J2-467: What should be the bottleneck in this test? I ra

[jira] [Resolved] (LOG4J2-482) The attribute of Route to refer to an appender is "ref" not "AppenderRef"

[ https://issues.apache.org/jira/browse/LOG4J2-482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-482. Resolution: Fixed Hmm... Perhaps I was too enthusiastic there... After taking another good look, u

[jira] [Comment Edited] (LOG4J2-482) The attribute of Route to refer to an appender is "ref" not "AppenderRef"

[ https://issues.apache.org/jira/browse/LOG4J2-482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862192#comment-13862192 ] Remko Popma edited comment on LOG4J2-482 at 1/4/14 3:46 AM: Hm

[jira] [Commented] (LOG4J2-467) Thread name caching in async logger incompatible with use of Thread.setName()

[ https://issues.apache.org/jira/browse/LOG4J2-467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862194#comment-13862194 ] Remko Popma commented on LOG4J2-467: Hi Scott! Good question, not sure. Disk access s

[jira] [Commented] (LOG4J2-467) Thread name caching in async logger incompatible with use of Thread.setName()

[ https://issues.apache.org/jira/browse/LOG4J2-467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862199#comment-13862199 ] Scott Deboy commented on LOG4J2-467: The test fails part way through for me since it i

[jira] [Commented] (LOG4J2-467) Thread name caching in async logger incompatible with use of Thread.setName()

[ https://issues.apache.org/jira/browse/LOG4J2-467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862203#comment-13862203 ] Remko Popma commented on LOG4J2-467: (away from PC) You shouldn't need slf4j to run th

[jira] [Commented] (LOG4J2-467) Thread name caching in async logger incompatible with use of Thread.setName()

[ https://issues.apache.org/jira/browse/LOG4J2-467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862217#comment-13862217 ] Scott Deboy commented on LOG4J2-467: I'm not sure why, but I do get an slf4j error as

[jira] [Commented] (LOG4J2-481) Stream-Interface for Loggers

[ https://issues.apache.org/jira/browse/LOG4J2-481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862225#comment-13862225 ] Matt Sicker commented on LOG4J2-481: I like this idea, and I'll take a whack at making

[jira] [Reopened] (LOG4J2-467) Thread name caching in async logger incompatible with use of Thread.setName()

[ https://issues.apache.org/jira/browse/LOG4J2-467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma reopened LOG4J2-467: Reopening so I can attach files and edit old comments. > Thread name caching in async logger incompati

[jira] [Updated] (LOG4J2-467) Thread name caching in async logger incompatible with use of Thread.setName()

[ https://issues.apache.org/jira/browse/LOG4J2-467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-467: --- Attachment: PerfTestDriver.java Scott, If you see "Logback..." you are not using the PerfTestDriver c

[jira] [Commented] (LOG4J2-467) Thread name caching in async logger incompatible with use of Thread.setName()

[ https://issues.apache.org/jira/browse/LOG4J2-467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862236#comment-13862236 ] Remko Popma commented on LOG4J2-467: Performance test result update: The numbers I re

[jira] [Comment Edited] (LOG4J2-467) Thread name caching in async logger incompatible with use of Thread.setName()

[ https://issues.apache.org/jira/browse/LOG4J2-467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862126#comment-13862126 ] Remko Popma edited comment on LOG4J2-467 at 1/4/14 7:50 AM: Ga