[jira] [Comment Edited] (LOG4J2-1517) Add ThreadContext.setContext(Map<String, String>)

[ https://issues.apache.org/jira/browse/LOG4J2-1517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15420600#comment-15420600 ] Remko Popma edited comment on LOG4J2-1517 at 8/15/16 4:24 AM: -- Not sure I

[jira] [Commented] (LOG4J2-1517) Add ThreadContext.setContext(Map<String, String>)

[ https://issues.apache.org/jira/browse/LOG4J2-1517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15420610#comment-15420610 ] Ralph Goers commented on LOG4J2-1517: - I also have concerns about this. I'd really need to understand

[jira] [Commented] (LOG4J2-1516) Add ThreadContextMap.putAll(Map<String, String>)

[ https://issues.apache.org/jira/browse/LOG4J2-1516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15420596#comment-15420596 ] Remko Popma commented on LOG4J2-1516: - Gary, would you mind adding some reason for this change? >

[jira] [Created] (LOG4J2-1518) Deadlock when using pure async and toString logs another message

Leon Finker created LOG4J2-1518: --- Summary: Deadlock when using pure async and toString logs another message Key: LOG4J2-1518 URL: https://issues.apache.org/jira/browse/LOG4J2-1518 Project: Log4j 2

[jira] [Updated] (LOG4J2-1518) Deadlock when using pure async and toString logs another message

[ https://issues.apache.org/jira/browse/LOG4J2-1518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leon Finker updated LOG4J2-1518: Attachment: async_deadlock.txt > Deadlock when using pure async and toString logs another message

[jira] [Commented] (LOG4J2-1510) why MutableLogEvent don't keep original log object or even the ReusableObjectMessage

[ https://issues.apache.org/jira/browse/LOG4J2-1510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15420564#comment-15420564 ] Maple Wang commented on LOG4J2-1510: Hi Remko, Thanks for your confirmation. Best regards. > why

[jira] [Created] (LOG4J2-1517) Add ThreadContext.setContext(Map<String, String>)

Gary Gregory created LOG4J2-1517: Summary: Add ThreadContext.setContext(Map) Key: LOG4J2-1517 URL: https://issues.apache.org/jira/browse/LOG4J2-1517 Project: Log4j 2 Issue

[jira] [Created] (LOG4J2-1516) Add ThreadContextMap.putAll(Map<String, String>)

Gary Gregory created LOG4J2-1516: Summary: Add ThreadContextMap.putAll(Map) Key: LOG4J2-1516 URL: https://issues.apache.org/jira/browse/LOG4J2-1516 Project: Log4j 2 Issue

Fwd: logging-log4j2 git commit: Ported Log4j 1's XMLLayout

Nice! :-) Gary -- Forwarded message -- From: Date: Aug 14, 2016 12:37 PM Subject: logging-log4j2 git commit: Ported Log4j 1's XMLLayout To: Cc: Repository: logging-log4j2 Updated Branches: refs/heads/master f511f848c -> 8e01bde35

Re: Configuration

I guess not. If we based our config parser on Jackson, that would be an easy yes, but would require a dependency that most people would find odd. We could also base configuration on JAXB then you would get XML IO. For JSON, there is a new JAXB like JSR IIRC. Gary On Aug 14, 2016 1:14 PM, "Mikael

Configuration

Is there a way to serialize a Configuration into one of the config file formats we support?

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

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