[jira] [Updated] (LOG4J2-546) Commons logging integration does not work in servlet 3.0

2014-02-21 Thread Leos Literak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leos Literak updated LOG4J2-546: Attachment: CommonsLog.war war with source code included Commons logging integration does not

[jira] [Updated] (LOG4J2-546) Commons logging integration does not work in servlet 3.0

2014-02-21 Thread Leos Literak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leos Literak updated LOG4J2-546: Description: I created trivial servlet 3.0 based web application that uses apache commons

[jira] [Updated] (LOG4J2-546) Commons logging integration does not work in servlet 3.0

2014-02-21 Thread Leos Literak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leos Literak updated LOG4J2-546: Affects Version/s: (was: 2.0-beta9) 2.0-rc1 Commons logging

[jira] [Updated] (LOG4J2-546) Commons logging integration does not work in servlet 3.0

2014-02-21 Thread Leos Literak (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leos Literak updated LOG4J2-546: Description: I created trivial servlet 3.0 based web application that uses apache commons

[jira] [Commented] (LOG4J2-542) LogEvents with exceptions fail to deserialize

2014-02-21 Thread Joern Huxhorn (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13908266#comment-13908266 ] Joern Huxhorn commented on LOG4J2-542: -- StackTrace string shouldn't be created at

Re: Health

2014-02-21 Thread Matt Sicker
Glad to hear you're doing better! Matt Sicker On Feb 20, 2014, at 23:19, Ralph Goers ralph.go...@dslextreme.com wrote: I just wanted to let you all know that I am out of the hospital and am now continuing to get better at home. I still require oxygen so I have a bit of a ways to go, but

Re: Health

2014-02-21 Thread Gary Gregory
Ralph, It is great to hear that you are out of the hospital! Please do take care of yourself and don't overdo it ;) Log4J can wait... :) Gary On Fri, Feb 21, 2014 at 12:19 AM, Ralph Goers ralph.go...@dslextreme.comwrote: I just wanted to let you all know that I am out of the hospital and am

Re: Site Download page

2014-02-21 Thread Gary Gregory
On Fri, Feb 21, 2014 at 12:13 AM, Ralph Goers ralph.go...@dslextreme.comwrote: The download page - http://logging.apache.org/log4j/2.x/download.html - lists the artifacts for the latest release. However, it says it was signed by me with my key. The page needs to be updated to reflect that it

Re: Site Download page

2014-02-21 Thread Nick Williams
I don't think it should even say WHO signed it. It already instructs users to download the KEYS file and import that file. Isn't that sufficient? As long as the artifacts are signed by someone in that KEYS file, doesn't that take care of it? Why does this page need to list someone's name? Nick

Re: Health

2014-02-21 Thread Scott Deboy
Hi Ralph, Glad to hear you're getting better! Scott On 2/21/14, Gary Gregory garydgreg...@gmail.com wrote: Ralph, It is great to hear that you are out of the hospital! Please do take care of yourself and don't overdo it ;) Log4J can wait... :) Gary On Fri, Feb 21, 2014 at 12:19 AM,

Re: Site Download page

2014-02-21 Thread Gary Gregory
On Fri, Feb 21, 2014 at 10:51 AM, Nick Williams nicho...@nicholaswilliams.net wrote: I don't think it should even say WHO signed it. It already instructs users to download the KEYS file and import that file. Isn't that sufficient? As long as the artifacts are signed by someone in that KEYS

Re: Logo contest: nominate your favorite logo

2014-02-21 Thread Ralph Goers
I am healthy enough that we can start anytime. I have forgotten, though, what we agreed upon for voting rules. I would like to be able to vote for 3 choices ranked as first, second, third. Presumably then others might vote my first choice as their second, etc, but would allow for a better

[jira] [Commented] (LOG4J2-474) MongoDBProvider won't work with databases that don't have authentication set up

2014-02-21 Thread Tal Liron (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13909096#comment-13909096 ] Tal Liron commented on LOG4J2-474: -- I'm not sure why you think Log4j needs to handle

[jira] [Commented] (LOG4J2-505) Memory leak with org.apache.logging.log4j.core.async.AsyncLoggerConfigHelper$Log4jEventWrapper

2014-02-21 Thread Tal Liron (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13909107#comment-13909107 ] Tal Liron commented on LOG4J2-505: -- Are there any known issues with the Disruptor

[jira] [Commented] (LOG4J2-505) Memory leak with org.apache.logging.log4j.core.async.AsyncLoggerConfigHelper$Log4jEventWrapper

2014-02-21 Thread Remko Popma (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13909137#comment-13909137 ] Remko Popma commented on LOG4J2-505: Sorry, I don't understand your question about

[jira] [Commented] (LOG4J2-505) Memory leak with org.apache.logging.log4j.core.async.AsyncLoggerConfigHelper$Log4jEventWrapper

2014-02-21 Thread Tal Liron (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13909142#comment-13909142 ] Tal Liron commented on LOG4J2-505: -- I meant to ask if there are any known disadvantages

[jira] [Commented] (LOG4J2-505) Memory leak with org.apache.logging.log4j.core.async.AsyncLoggerConfigHelper$Log4jEventWrapper

2014-02-21 Thread Remko Popma (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13909161#comment-13909161 ] Remko Popma commented on LOG4J2-505: About the Disruptor in general, I am not aware of

[jira] [Commented] (LOG4J2-505) Memory leak with org.apache.logging.log4j.core.async.AsyncLoggerConfigHelper$Log4jEventWrapper

2014-02-21 Thread Tal Liron (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13909163#comment-13909163 ] Tal Liron commented on LOG4J2-505: -- It does, thanks! It seems that Disruptor is indeed a

[jira] [Comment Edited] (LOG4J2-505) Memory leak with org.apache.logging.log4j.core.async.AsyncLoggerConfigHelper$Log4jEventWrapper

2014-02-21 Thread Remko Popma (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13909161#comment-13909161 ] Remko Popma edited comment on LOG4J2-505 at 2/22/14 2:15 AM: -

[jira] [Commented] (LOG4J2-505) Memory leak with org.apache.logging.log4j.core.async.AsyncLoggerConfigHelper$Log4jEventWrapper

2014-02-21 Thread Remko Popma (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13909203#comment-13909203 ] Remko Popma commented on LOG4J2-505: If you're interested in looking at the Disruptor