[jira] [Updated] (LOG4J2-1676) Use Message.getThrowable() in log(Message) methods

[ https://issues.apache.org/jira/browse/LOG4J2-1676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joern Huxhorn updated LOG4J2-1676: -- Attachment: 0004-Using-Throwable-of-Message-if-not-explicitly-given.patch

[jira] [Updated] (LOG4J2-1676) Use Message.getThrowable() in log(Message) methods

[ https://issues.apache.org/jira/browse/LOG4J2-1676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joern Huxhorn updated LOG4J2-1676: -- Attachment: (was: 0002-Using-Throwable-of-Message-if-not-explicitly-given.patch) > Use

[jira] [Updated] (LOG4J2-1676) Use Message.getThrowable() in log(Message) methods

[ https://issues.apache.org/jira/browse/LOG4J2-1676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joern Huxhorn updated LOG4J2-1676: -- Attachment: (was: 0001-Using-Throwable-of-Message-if-available.patch) > Use

[jira] [Commented] (LOG4J2-1676) Use Message.getThrowable() in log(Message) methods

[ https://issues.apache.org/jira/browse/LOG4J2-1676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15672954#comment-15672954 ] Joern Huxhorn commented on LOG4J2-1676: --- I'll probably give it a shot over the weekend. No

[jira] [Closed] (LOG4J2-1710) Build is currently broken in SocketAppender SocketOptions tests and Jacoco on MacOS

[ https://issues.apache.org/jira/browse/LOG4J2-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joern Huxhorn closed LOG4J2-1710. - Works. Thanks. > Build is currently broken in SocketAppender SocketOptions tests and Jacoco on >

[jira] [Commented] (LOG4J2-1676) Use Message.getThrowable() in log(Message) methods

[ https://issues.apache.org/jira/browse/LOG4J2-1676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15670964#comment-15670964 ] Joern Huxhorn commented on LOG4J2-1676: --- I know. Can you give me some hints about where/how you

[jira] [Updated] (LOG4J2-1710) Build is currently broken.

[ https://issues.apache.org/jira/browse/LOG4J2-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joern Huxhorn updated LOG4J2-1710: -- Attachment: 0001-Fixing-LOG4J2-1710.patch The attached patch contains my workaround/fix for

[jira] [Updated] (LOG4J2-1676) Use Message.getThrowable() in log(Message) methods

[ https://issues.apache.org/jira/browse/LOG4J2-1676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joern Huxhorn updated LOG4J2-1676: -- Attachment: 0002-Using-Throwable-of-Message-if-not-explicitly-given.patch

[jira] [Commented] (LOG4J2-1710) Build is currently broken.

[ https://issues.apache.org/jira/browse/LOG4J2-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15670517#comment-15670517 ] Joern Huxhorn commented on LOG4J2-1710: --- Removing {{@{argLine} -Xms256m -Xmx1024m}} from the

[jira] [Comment Edited] (LOG4J2-1710) Build is currently broken.

[ https://issues.apache.org/jira/browse/LOG4J2-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15670517#comment-15670517 ] Joern Huxhorn edited comment on LOG4J2-1710 at 11/16/16 2:18 PM: -

[jira] [Commented] (LOG4J2-1710) Build is currently broken.

[ https://issues.apache.org/jira/browse/LOG4J2-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15670475#comment-15670475 ] Joern Huxhorn commented on LOG4J2-1710: --- Hm. It seems like this didn't fix the tests in IDEA, only

[jira] [Created] (LOG4J2-1710) Build is currently broken.

Joern Huxhorn created LOG4J2-1710: - Summary: Build is currently broken. Key: LOG4J2-1710 URL: https://issues.apache.org/jira/browse/LOG4J2-1710 Project: Log4j 2 Issue Type: Bug

[jira] [Commented] (LOG4J2-1226) Message instances are simply serialized. They mustn't.

[ https://issues.apache.org/jira/browse/LOG4J2-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15666751#comment-15666751 ] Joern Huxhorn commented on LOG4J2-1226: --- Any ETA for 2.8 release? > Message instances are simply

[jira] [Commented] (LOG4J2-1676) Use Message.getThrowable() in log(Message) methods

[ https://issues.apache.org/jira/browse/LOG4J2-1676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1568#comment-1568 ] Joern Huxhorn commented on LOG4J2-1676: --- Is there any downside of this proposed change that I'm

[jira] [Commented] (LOG4J2-1676) Use Message.getThrowable() in log(Message) methods

[ https://issues.apache.org/jira/browse/LOG4J2-1676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15647134#comment-15647134 ] Joern Huxhorn commented on LOG4J2-1676: --- Others may correct me but I'm pretty sure it's there

[jira] [Comment Edited] (LOG4J2-1676) Use Message.getThrowable() in log(Message) methods

[ https://issues.apache.org/jira/browse/LOG4J2-1676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15647072#comment-15647072 ] Joern Huxhorn edited comment on LOG4J2-1676 at 11/8/16 9:52 AM: Because

[jira] [Commented] (LOG4J2-1676) Use Message.getThrowable() in log(Message) methods

[ https://issues.apache.org/jira/browse/LOG4J2-1676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15646990#comment-15646990 ] Joern Huxhorn commented on LOG4J2-1676: --- It is used to retrieve a potential {{Throwable}} from the

[jira] [Commented] (LOG4J2-1226) Message instances are simply serialized. They mustn't.

[ https://issues.apache.org/jira/browse/LOG4J2-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15646745#comment-15646745 ] Joern Huxhorn commented on LOG4J2-1226: --- I created LOG4J2-1676 for this. > Message instances are

[jira] [Created] (LOG4J2-1676) Use Message.getThrowable() in log(Message) methods

Joern Huxhorn created LOG4J2-1676: - Summary: Use Message.getThrowable() in log(Message) methods Key: LOG4J2-1676 URL: https://issues.apache.org/jira/browse/LOG4J2-1676 Project: Log4j 2 Issue

[jira] [Commented] (LOG4J2-1226) Message instances are simply serialized. They mustn't.

[ https://issues.apache.org/jira/browse/LOG4J2-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15644477#comment-15644477 ] Joern Huxhorn commented on LOG4J2-1226: --- Just checked against 2.5, 2.6 and 2.7. All show the same

[jira] [Commented] (LOG4J2-1226) Message instances are simply serialized. They mustn't.

[ https://issues.apache.org/jira/browse/LOG4J2-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15644436#comment-15644436 ] Joern Huxhorn commented on LOG4J2-1226: --- I have no idea. But that one was indeed especially

[jira] [Commented] (LOG4J2-1675) Compile-time incompatibility regarding SimpleMessage

[ https://issues.apache.org/jira/browse/LOG4J2-1675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15644406#comment-15644406 ] Joern Huxhorn commented on LOG4J2-1675: --- I know. That's why I gave this a "minor" priority. Just

[jira] [Comment Edited] (LOG4J2-1226) Message instances are simply serialized. They mustn't.

[ https://issues.apache.org/jira/browse/LOG4J2-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15644392#comment-15644392 ] Joern Huxhorn edited comment on LOG4J2-1226 at 11/7/16 2:55 PM: I don't

[jira] [Commented] (LOG4J2-1226) Message instances are simply serialized. They mustn't.

[ https://issues.apache.org/jira/browse/LOG4J2-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15644392#comment-15644392 ] Joern Huxhorn commented on LOG4J2-1226: --- I don't think so... In the

[jira] [Commented] (LOG4J2-1226) Message instances are simply serialized. They mustn't.

[ https://issues.apache.org/jira/browse/LOG4J2-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15644214#comment-15644214 ] Joern Huxhorn commented on LOG4J2-1226: --- The fact that {{FooMessage}} in the sandbox linked above

[jira] [Created] (LOG4J2-1675) Compile-time incompatibility regarding SimpleMessage

Joern Huxhorn created LOG4J2-1675: - Summary: Compile-time incompatibility regarding SimpleMessage Key: LOG4J2-1675 URL: https://issues.apache.org/jira/browse/LOG4J2-1675 Project: Log4j 2

[jira] [Commented] (LOG4J2-1226) Message instances are simply serialized. They mustn't.

[ https://issues.apache.org/jira/browse/LOG4J2-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15644166#comment-15644166 ] Joern Huxhorn commented on LOG4J2-1226: --- The fix looks good so far. All messages of [my little

[jira] [Commented] (LOG4J2-1226) Message instances are simply serialized. They mustn't.

[ https://issues.apache.org/jira/browse/LOG4J2-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15389372#comment-15389372 ] Joern Huxhorn commented on LOG4J2-1226: --- That's what I meant, exactly. > Message instances are

[jira] [Commented] (LOG4J2-1226) Message instances are simply serialized. They mustn't.

[ https://issues.apache.org/jira/browse/LOG4J2-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15389336#comment-15389336 ] Joern Huxhorn commented on LOG4J2-1226: --- Your suggestion should fix the Lilith problem, assuming

[jira] [Commented] (LOG4J2-1226) Message instances are simply serialized. They mustn't.

[ https://issues.apache.org/jira/browse/LOG4J2-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15376998#comment-15376998 ] Joern Huxhorn commented on LOG4J2-1226: --- There's another big problem with live objects in log

[jira] [Commented] (LOG4J2-1226) Message instances are simply serialized. They mustn't.

[ https://issues.apache.org/jira/browse/LOG4J2-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15370756#comment-15370756 ] Joern Huxhorn commented on LOG4J2-1226: --- We don't need to discuss the pros and cons of Java

[jira] [Commented] (LOG4J2-1226) Message instances are simply serialized. They mustn't.

[ https://issues.apache.org/jira/browse/LOG4J2-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15370586#comment-15370586 ] Joern Huxhorn commented on LOG4J2-1226: --- I certainly have other formats for receiving logging

[jira] [Commented] (LOG4J2-601) Log.log and isEnabled react differently for marker filters

[ https://issues.apache.org/jira/browse/LOG4J2-601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15201251#comment-15201251 ] Joern Huxhorn commented on LOG4J2-601: -- A {{Result filter(Logger logger, Level level, Marker

[jira] [Commented] (LOG4J2-1226) Message instances are simply serialized. They mustn't.

[ https://issues.apache.org/jira/browse/LOG4J2-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15171730#comment-15171730 ] Joern Huxhorn commented on LOG4J2-1226: --- Any chance of getting this fixed in the near future?

[jira] [Created] (LOG4J2-1226) Message instances are simply serialized. They mustn't.

Joern Huxhorn created LOG4J2-1226: - Summary: Message instances are simply serialized. They mustn't. Key: LOG4J2-1226 URL: https://issues.apache.org/jira/browse/LOG4J2-1226 Project: Log4j 2

[jira] [Commented] (LOG4J2-1225) MessageSupplier should extend Supplier

[ https://issues.apache.org/jira/browse/LOG4J2-1225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15066466#comment-15066466 ] Joern Huxhorn commented on LOG4J2-1225: --- Ah, OK. Makes sense. Just thought it might have been an

[jira] [Created] (LOG4J2-1225) MessageSupplier should extend Supplier

Joern Huxhorn created LOG4J2-1225: - Summary: MessageSupplier should extend Supplier Key: LOG4J2-1225 URL: https://issues.apache.org/jira/browse/LOG4J2-1225 Project: Log4j 2 Issue Type:

[jira] [Updated] (LOG4J2-1226) Message instances are simply serialized. They mustn't.

[ https://issues.apache.org/jira/browse/LOG4J2-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joern Huxhorn updated LOG4J2-1226: -- Description: Right now, any Message instance used to call any log method are simply sent as

[jira] [Commented] (LOG4J2-1225) MessageSupplier should extend Supplier

[ https://issues.apache.org/jira/browse/LOG4J2-1225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15066300#comment-15066300 ] Joern Huxhorn commented on LOG4J2-1225: --- org.apache.logging.log4j.util.MessageSupplier should

[jira] [Comment Edited] (LOG4J2-1225) MessageSupplier should extend Supplier

[ https://issues.apache.org/jira/browse/LOG4J2-1225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15066418#comment-15066418 ] Joern Huxhorn edited comment on LOG4J2-1225 at 12/21/15 12:53 PM: -- No

[jira] [Commented] (LOG4J2-1225) MessageSupplier should extend Supplier

[ https://issues.apache.org/jira/browse/LOG4J2-1225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15066418#comment-15066418 ] Joern Huxhorn commented on LOG4J2-1225: --- No specific reason at all. I was just surfing the log4j

[jira] [Commented] (LOG4J2-1226) Message instances are simply serialized. They mustn't.

[ https://issues.apache.org/jira/browse/LOG4J2-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15066516#comment-15066516 ] Joern Huxhorn commented on LOG4J2-1226: --- I do have a stacktrace but it's in Lilith so it won't be

[jira] [Commented] (LOG4J2-1226) Message instances are simply serialized. They mustn't.

[ https://issues.apache.org/jira/browse/LOG4J2-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15066585#comment-15066585 ] Joern Huxhorn commented on LOG4J2-1226: --- I'd argue that they still can. Just not if they are using

[jira] [Created] (LOG4J2-684) ConsoleAppender does not print suppressed exceptions

Joern Huxhorn created LOG4J2-684: Summary: ConsoleAppender does not print suppressed exceptions Key: LOG4J2-684 URL: https://issues.apache.org/jira/browse/LOG4J2-684 Project: Log4j 2 Issue

[jira] [Commented] (LOG4J2-141) Documentation is lacking info about valid status levels

[ https://issues.apache.org/jira/browse/LOG4J2-141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14039251#comment-14039251 ] Joern Huxhorn commented on LOG4J2-141: -- The is one of the first things tools

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

[ https://issues.apache.org/jira/browse/LOG4J2-623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13999867#comment-13999867 ] Joern Huxhorn commented on LOG4J2-623: -- @Ralph Ah, I see. I wasn't aware that JSON

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

[ https://issues.apache.org/jira/browse/LOG4J2-623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13998320#comment-13998320 ] Joern Huxhorn commented on LOG4J2-623: -- I suppose moving the XML- and JSON-layouts

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

[ https://issues.apache.org/jira/browse/LOG4J2-623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13996192#comment-13996192 ] Joern Huxhorn commented on LOG4J2-623: -- I'd suggest to use something like

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

[ https://issues.apache.org/jira/browse/LOG4J2-623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13996256#comment-13996256 ] Joern Huxhorn commented on LOG4J2-623: -- If you are interested:

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

[ https://issues.apache.org/jira/browse/LOG4J2-623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13996793#comment-13996793 ] Joern Huxhorn commented on LOG4J2-623: -- @Gary Ah, ok. The earlier [comment from

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

[ 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

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

Joern Huxhorn created LOG4J2-542: Summary: LogEvents with exceptions fail to deserialize Key: LOG4J2-542 URL: https://issues.apache.org/jira/browse/LOG4J2-542 Project: Log4j 2 Issue Type:

[jira] [Closed] (LOG4J2-139) NPE while using SocketAppender

[ https://issues.apache.org/jira/browse/LOG4J2-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joern Huxhorn closed LOG4J2-139. Confirmed. NPE while using SocketAppender --

[jira] [Reopened] (LOG4J2-139) NPE while using SocketAppender

[ https://issues.apache.org/jira/browse/LOG4J2-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joern Huxhorn reopened LOG4J2-139: -- beta7 introduced a regression that causes the following NPE in the absence of a protocol

[jira] [Created] (LOG4J2-216) Detach ThrowableProxy from Throwable

Joern Huxhorn created LOG4J2-216: Summary: Detach ThrowableProxy from Throwable Key: LOG4J2-216 URL: https://issues.apache.org/jira/browse/LOG4J2-216 Project: Log4j 2 Issue Type: Wish

[jira] [Commented] (LOG4J2-216) Detach ThrowableProxy from Throwable

[ https://issues.apache.org/jira/browse/LOG4J2-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13637565#comment-13637565 ] Joern Huxhorn commented on LOG4J2-216: -- The same applies for StackTraceElement[]

[jira] [Closed] (LOG4J2-142) Exception while deserializing event from SocketAppender

[ https://issues.apache.org/jira/browse/LOG4J2-142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joern Huxhorn closed LOG4J2-142. Works, thanks! Exception while deserializing event from SocketAppender

[jira] [Closed] (LOG4J2-139) NPE while using SocketAppender

[ https://issues.apache.org/jira/browse/LOG4J2-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joern Huxhorn closed LOG4J2-139. Confirmed. NPE while using SocketAppender --

[jira] [Created] (LOG4J2-139) NPE while using SocketAppender

Joern Huxhorn created LOG4J2-139: Summary: NPE while using SocketAppender Key: LOG4J2-139 URL: https://issues.apache.org/jira/browse/LOG4J2-139 Project: Log4j 2 Issue Type: Bug Affects

[jira] [Created] (LOG4J2-141) Documentation is lacking info about valid status levels

Joern Huxhorn created LOG4J2-141: Summary: Documentation is lacking info about valid status levels Key: LOG4J2-141 URL: https://issues.apache.org/jira/browse/LOG4J2-141 Project: Log4j 2

[jira] [Closed] (LOG4J2-137) Build hangs during SMTPAppenderTest

[ https://issues.apache.org/jira/browse/LOG4J2-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joern Huxhorn closed LOG4J2-137. Thanks. Forgot to close this on time. Build hangs during SMTPAppenderTest

[jira] [Commented] (LOG4J2-139) NPE while using SocketAppender

[ https://issues.apache.org/jira/browse/LOG4J2-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13545271#comment-13545271 ] Joern Huxhorn commented on LOG4J2-139: -- Found the solution: the appender was missing

[jira] [Created] (LOG4J2-142) Exception while deserializing event from SocketAppender

Joern Huxhorn created LOG4J2-142: Summary: Exception while deserializing event from SocketAppender Key: LOG4J2-142 URL: https://issues.apache.org/jira/browse/LOG4J2-142 Project: Log4j 2

[jira] [Commented] (LOG4J2-137) Build hangs during SMTPAppenderTest

[ https://issues.apache.org/jira/browse/LOG4J2-137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13541155#comment-13541155 ] Joern Huxhorn commented on LOG4J2-137: -- Whatever you did, it seems to have fixed the

[jira] [Created] (LOG4J2-137) Build hangs during SMTPAppenderTest

Joern Huxhorn created LOG4J2-137: Summary: Build hangs during SMTPAppenderTest Key: LOG4J2-137 URL: https://issues.apache.org/jira/browse/LOG4J2-137 Project: Log4j 2 Issue Type: Bug

[jira] [Commented] (LOG4J2-137) Build hangs during SMTPAppenderTest

[ https://issues.apache.org/jira/browse/LOG4J2-137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13540595#comment-13540595 ] Joern Huxhorn commented on LOG4J2-137: -- Aww, crap. Some other program - in this case

[jira] [Updated] (LOG4J2-137) Build hangs during SMTPAppenderTest

[ https://issues.apache.org/jira/browse/LOG4J2-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joern Huxhorn updated LOG4J2-137: - Description: I was trying to build SVN revision r1426064 This is the stacktrace of the hang:

[jira] [Comment Edited] (LOG4J2-137) Build hangs during SMTPAppenderTest

[ https://issues.apache.org/jira/browse/LOG4J2-137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13540595#comment-13540595 ] Joern Huxhorn edited comment on LOG4J2-137 at 12/28/12 9:24 PM:

[jira] [Closed] (LOG4J2-85) Replace ThreadContext.push(String msg) with push(String msg, Object args...)

[ https://issues.apache.org/jira/browse/LOG4J2-85?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joern Huxhorn closed LOG4J2-85. --- Fixed, thanks! Replace ThreadContext.push(String msg) with push(String msg, Object

[jira] [Closed] (LOG4J2-83) Please provide means to disable MDC functionality on a global level.

[ https://issues.apache.org/jira/browse/LOG4J2-83?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joern Huxhorn closed LOG4J2-83. --- Looks good. Please provide means to disable MDC functionality on a global level.

[jira] [Closed] (LOG4J2-84) Please provide means to disable NDC functionality on a global level.

[ https://issues.apache.org/jira/browse/LOG4J2-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joern Huxhorn closed LOG4J2-84. --- Looks good. Please provide means to disable NDC functionality on a global level.

[jira] [Commented] (LOG4J2-83) Please provide means to disable MDC functionality on a global level.

[ https://issues.apache.org/jira/browse/LOG4J2-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13466445#comment-13466445 ] Joern Huxhorn commented on LOG4J2-83: - Not really since the map wouldn't be empty at

[jira] [Commented] (LOG4J2-85) Replace ThreadContext.push(String msg) with push(String msg, Object args...)

[ https://issues.apache.org/jira/browse/LOG4J2-85?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13461785#comment-13461785 ] Joern Huxhorn commented on LOG4J2-85: - The evaluation/formatting of the message should

[jira] [Created] (LOG4J2-83) Please provide means to disable MDC functionality on a global level.

Joern Huxhorn created LOG4J2-83: --- Summary: Please provide means to disable MDC functionality on a global level. Key: LOG4J2-83 URL: https://issues.apache.org/jira/browse/LOG4J2-83 Project: Log4j 2

[jira] [Created] (LOG4J2-84) Please provide means to disable NDC functionality on a global level.

Joern Huxhorn created LOG4J2-84: --- Summary: Please provide means to disable NDC functionality on a global level. Key: LOG4J2-84 URL: https://issues.apache.org/jira/browse/LOG4J2-84 Project: Log4j 2

[jira] [Created] (LOG4J2-85) Replace ThreadContext.push(String msg) with push(String msg, Object args...)

Joern Huxhorn created LOG4J2-85: --- Summary: Replace ThreadContext.push(String msg) with push(String msg, Object args...) Key: LOG4J2-85 URL: https://issues.apache.org/jira/browse/LOG4J2-85 Project:

[jira] [Updated] (LOG4J2-85) Replace ThreadContext.push(String msg) with push(String msg, Object args...)

[ https://issues.apache.org/jira/browse/LOG4J2-85?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joern Huxhorn updated LOG4J2-85: Issue Type: Improvement (was: New Feature) Replace ThreadContext.push(String msg) with