[jira] [Reopened] (LOG4J2-625) Serialization error with SocketAppender and Asynch Logger

2014-04-30 Thread Ralph Goers (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers reopened LOG4J2-625: After looking at this again this is not a duplicate of LOG4J2-542. That has to do with

[jira] [Created] (LOG4J2-626) ThreadContext for Asynchronous logger in multithreaded environmant is overwriting the values.

2014-04-30 Thread sivan (JIRA)
sivan created LOG4J2-626: Summary: ThreadContext for Asynchronous logger in multithreaded environmant is overwriting the values. Key: LOG4J2-626 URL: https://issues.apache.org/jira/browse/LOG4J2-626 Project:

[jira] [Updated] (LOG4J2-624) Better structure of Thread Context Stack in JSONLayout

2014-04-30 Thread JIRA
[ https://issues.apache.org/jira/browse/LOG4J2-624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal updated LOG4J2-624: -- Description: The Thread Context Stack is currently represented like this in JSONLayout:

[jira] [Created] (LOG4J2-627) Better structure of Thread Context Stack in XMLLayout

2014-04-30 Thread JIRA
Mikael Ståldal created LOG4J2-627: - Summary: Better structure of Thread Context Stack in XMLLayout Key: LOG4J2-627 URL: https://issues.apache.org/jira/browse/LOG4J2-627 Project: Log4j 2

[jira] [Commented] (LOG4J2-626) ThreadContext for Asynchronous logger in multithreaded environmant is overwriting the values.

2014-04-30 Thread Remko Popma (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13985328#comment-13985328 ] Remko Popma commented on LOG4J2-626: Sorry but this is not enough information to even

[jira] [Updated] (LOG4J2-626) ThreadContext for Asynchronous logger in multithreaded environmant is overwriting the values.

2014-04-30 Thread sivan (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sivan updated LOG4J2-626: - Description: ThreadContext for Asynchronous loggers in multithreaded environmant is overwriting the values. Is

[jira] [Comment Edited] (LOG4J2-626) ThreadContext for Asynchronous logger in multithreaded environmant is overwriting the values.

2014-04-30 Thread Remko Popma (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13985328#comment-13985328 ] Remko Popma edited comment on LOG4J2-626 at 4/30/14 12:36 PM: --

[jira] [Commented] (LOG4J2-626) ThreadContext for Asynchronous logger in multithreaded environmant is overwriting the values.

2014-04-30 Thread sivan (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13985491#comment-13985491 ] sivan commented on LOG4J2-626: -- Log4j2 will not modify this. that is OK. But when many users

[jira] [Updated] (LOG4J2-626) ThreadContext for Asynchronous logger in multithreaded environmant is overwriting the values.

2014-04-30 Thread sivan (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sivan updated LOG4J2-626: - Description: ThreadContext for Asynchronous loggers in multithreaded environmant is overwriting the values. Is

Re: Log4j Project Guidelines

2014-04-30 Thread Matt Sicker
So it's a good idea to set up your IDE to warn if you override a synchronized method with an unsynchronized method? I remember seeing that one somewhere. On 30 April 2014 00:35, Remko Popma remko.po...@gmail.com wrote: Agreed that unless the synchronization is part of the public API it is

Re: Log4j Project Guidelines

2014-04-30 Thread Gary Gregory
I'm pretty sure Eclipse does that. Gary On Wed, Apr 30, 2014 at 9:50 AM, Matt Sicker boa...@gmail.com wrote: So it's a good idea to set up your IDE to warn if you override a synchronized method with an unsynchronized method? I remember seeing that one somewhere. On 30 April 2014 00:35,

Re: Log4j Project Guidelines

2014-04-30 Thread Remko Popma
Yes, overriding a synchronized method with an unsynchronized method sounds dangerous... Warnings would probably be helpful. On Wed, Apr 30, 2014 at 11:13 PM, Gary Gregory garydgreg...@gmail.comwrote: I'm pretty sure Eclipse does that. Gary On Wed, Apr 30, 2014 at 9:50 AM, Matt Sicker

synchronized vs. Lock (was: Log4j Project Guidelines)

2014-04-30 Thread Jörn Huxhorn
Did you try https://gist.github.com/huxi/81c152a672d1b39aed64 with different delays? (If you find anything wrong with that code, please let me know.) The output on my system with 0ms, 1ms and 10ms delays looks like this:  http://pastebin.com/za07QmUU Unfairness increases with the amount of time

Re: Log4j Project Guidelines

2014-04-30 Thread Ralph Goers
Actually, I believe there was a case where I did that because the method in the subclass used java.util.concurrent instead of requiring method synchronization. Ralph On Apr 30, 2014, at 7:19 AM, Remko Popma remko.po...@gmail.com wrote: Yes, overriding a synchronized method with an

[jira] [Commented] (LOG4J2-623) Better structure of Thread Context Map in JSONLayout

2014-04-30 Thread JIRA
[ https://issues.apache.org/jira/browse/LOG4J2-623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13985647#comment-13985647 ] Mikael Ståldal commented on LOG4J2-623: --- Currently, it does mimic the XMLLayout.

[jira] [Commented] (LOG4J2-623) Better structure of Thread Context Map in JSONLayout

2014-04-30 Thread Ralph Goers (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13985656#comment-13985656 ] Ralph Goers commented on LOG4J2-623: I didn't mean in terms of structure. I mean the

[jira] [Commented] (LOG4J2-623) Better structure of Thread Context Map in JSONLayout

2014-04-30 Thread JIRA
[ https://issues.apache.org/jira/browse/LOG4J2-623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13985672#comment-13985672 ] Mikael Ståldal commented on LOG4J2-623: --- Ah, yes then I agree. Better structure of

Re: Log4j Project Guidelines

2014-04-30 Thread Matt Sicker
There are legitimate reasons to do that as long as you maintain thread-safety such as the case Ralph mentioned. Though that would probably require full control of the API from top to bottom-ish. On 30 April 2014 10:22, Ralph Goers ralph.go...@dslextreme.com wrote: Actually, I believe there was

[jira] [Created] (LOG4J2-628) Cannot set log4j.Clock with Async appender

2014-04-30 Thread Bryan Hsueh (JIRA)
Bryan Hsueh created LOG4J2-628: -- Summary: Cannot set log4j.Clock with Async appender Key: LOG4J2-628 URL: https://issues.apache.org/jira/browse/LOG4J2-628 Project: Log4j 2 Issue Type: Question

[jira] [Commented] (LOG4J2-628) Cannot set log4j.Clock with Async appender

2014-04-30 Thread Remko Popma (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13986246#comment-13986246 ] Remko Popma commented on LOG4J2-628: This is expected behaviour as of RC-1. The use

[jira] [Commented] (LOG4J2-626) ThreadContext for Asynchronous logger in multithreaded environmant is overwriting the values.

2014-04-30 Thread Remko Popma (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13986258#comment-13986258 ] Remko Popma commented on LOG4J2-626: It should not matter whether you use asynchronous

Re: New log4j-streams Module

2014-04-30 Thread Bruce Brouwer
Can we agree to pull out jpa and jms? As for web, I know there was some discussion on how we could not register a shutdown hook. If we broke out log4j-web, maybe we could make it as simple as registering a shutdown hook if log4j-web is not included, but if log4j-web was included, the shutdown

Re: New log4j-streams Module

2014-04-30 Thread Ralph Goers
That makes a lot of sense to me Sent from my iPhone On Apr 30, 2014, at 6:05 PM, Bruce Brouwer bruce.brou...@gmail.com wrote: Can we agree to pull out jpa and jms? As for web, I know there was some discussion on how we could not register a shutdown hook. If we broke out log4j-web,

[jira] [Updated] (LOG4J2-609) StatusConfiguration doesn't close files

2014-04-30 Thread Bruce Brouwer (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Brouwer updated LOG4J2-609: - Attachment: log4j2-609.patch With log4j2-609.patch, now all tests pass with a clean install on

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

2014-04-30 Thread Ralph Goers (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-542. Resolution: Fixed Fix Version/s: 2.0-rc2 Throwable was made transient in revision 1591544.

[jira] [Assigned] (LOG4J2-609) StatusConfiguration doesn't close files

2014-04-30 Thread Ralph Goers (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers reassigned LOG4J2-609: -- Assignee: Ralph Goers StatusConfiguration doesn't close files