[jira] [Commented] (LOG4J2-673) plugin preloading fails in shaded jar files

[ https://issues.apache.org/jira/browse/LOG4J2-673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14595939#comment-14595939 ] Günther Falk commented on LOG4J2-673: - Hi, I have the same problem when creating

[jira] [Comment Edited] (LOG4J2-673) plugin preloading fails in shaded jar files

[ https://issues.apache.org/jira/browse/LOG4J2-673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14595939#comment-14595939 ] Günther Falk edited comment on LOG4J2-673 at 6/22/15 1:53 PM

[jira] [Commented] (LOG4J2-1059) log4j2 Configuration File not found in shaded jar

[ https://issues.apache.org/jira/browse/LOG4J2-1059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14595988#comment-14595988 ] Günther Falk commented on LOG4J2-1059: -- Hi, I discovered the same problem on my

[jira] [Comment Edited] (LOG4J2-1045) WAS8: externalize log4j2.xml via URL resource

[ https://issues.apache.org/jira/browse/LOG4J2-1045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14578624#comment-14578624 ] Günter Albrecht edited comment on LOG4J2-1045 at 6/10/15 4:00 PM

[jira] [Created] (LOG4J2-1054) PatternLayout in Socket appender writes the stacktrace of an exception to the socket, after it has written the pattern.

://issues.apache.org/jira/browse/LOG4J2-1054 Project: Log4j 2 Issue Type: Bug Components: Appenders Affects Versions: 2.3 Reporter: Anders Kreinøe I have the following configuration: {code:xml} ?xml version=1.0 encoding=UTF-8? Configuration status=WARN

[jira] [Updated] (LOG4J2-1054) PatternLayout in Socket appender writes the stacktrace of an exception to the socket, after it has written the pattern.

[ https://issues.apache.org/jira/browse/LOG4J2-1054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anders Kreinøe updated LOG4J2-1054: --- Description: I have the following configuration: {code:xml} ?xml version=1.0 encoding=UTF-8

[jira] [Resolved] (LOG4J2-1054) PatternLayout in Socket appender writes the stacktrace of an exception to the socket, after it has written the pattern.

[ https://issues.apache.org/jira/browse/LOG4J2-1054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anders Kreinøe resolved LOG4J2-1054. Resolution: Cannot Reproduce Going to the code, to see if I could create a patch, made me

[jira] [Commented] (LOG4J2-767) New module for Liquibase integration

[ https://issues.apache.org/jira/browse/LOG4J2-767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14585010#comment-14585010 ] Mikael Ståldal commented on LOG4J2-767: --- Works fine. New module for Liquibase

[jira] [Commented] (LOG4J2-1010) Possibility to set ThreadContext values in calls to Logger method

[ https://issues.apache.org/jira/browse/LOG4J2-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14584985#comment-14584985 ] Mikael Ståldal commented on LOG4J2-1010: The properties approach looks

[jira] [Commented] (LOG4J2-767) New module for Liquibase integration

[ https://issues.apache.org/jira/browse/LOG4J2-767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14584987#comment-14584987 ] Mikael Ståldal commented on LOG4J2-767: --- There is a typo in Log4j2Logger.java:26

[jira] [Commented] (LOG4J2-767) New module for Liquibase integration

[ https://issues.apache.org/jira/browse/LOG4J2-767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14585164#comment-14585164 ] Mikael Ståldal commented on LOG4J2-767: --- I cannot see the typo fix in Git. New

[jira] [Closed] (LOG4J2-767) New module for Liquibase integration

[ https://issues.apache.org/jira/browse/LOG4J2-767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal closed LOG4J2-767. - Everything is fine now. New module for Liquibase integration

[jira] [Commented] (LOG4J2-1043) Run initialization of AsyncAppender delegates asynchronously

[ https://issues.apache.org/jira/browse/LOG4J2-1043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14589805#comment-14589805 ] Mikael Ståldal commented on LOG4J2-1043: This is probably best done by allowing

[jira] [Commented] (LOG4J2-1010) Possibility to set ThreadContext values in calls to Logger method

[ https://issues.apache.org/jira/browse/LOG4J2-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14584690#comment-14584690 ] Mikael Ståldal commented on LOG4J2-1010: As I have already said, I believe

[jira] [Updated] (LOG4J2-767) Liquibase integration

[ https://issues.apache.org/jira/browse/LOG4J2-767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal updated LOG4J2-767: -- Attachment: log4j2-liquibase-2.diff New diff, on current master of Log4j, for latest version

[jira] [Closed] (LOG4J2-1025) Custom java.util.logging.Level gives null Log4j Level and causes NPE

[ https://issues.apache.org/jira/browse/LOG4J2-1025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal closed LOG4J2-1025. -- The fix is good enough, so closing this issue. Custom java.util.logging.Level gives null Log4j

[jira] [Updated] (LOG4J2-767) Liquibase integration

[ https://issues.apache.org/jira/browse/LOG4J2-767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal updated LOG4J2-767: -- Attachment: (was: log4j-liquibase.diff) Liquibase integration

[jira] [Updated] (LOG4J2-1012) AsyncAppender hang on shutdown if delegate Appender hangs

[ https://issues.apache.org/jira/browse/LOG4J2-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal updated LOG4J2-1012: --- Attachment: LOG4J2-1012.diff Here is a patch, with unit test. AsyncAppender hang

[jira] [Commented] (LOG4J2-1045) WAS8: externalize log4j2.xml via URL resource

[ https://issues.apache.org/jira/browse/LOG4J2-1045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14586322#comment-14586322 ] Günter Albrecht commented on LOG4J2-1045: - No, bug LOG4J2-1050 does not relate

[jira] [Updated] (LOG4J2-1045) WAS8: externalize log4j2.xml via URL resource

[ https://issues.apache.org/jira/browse/LOG4J2-1045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Günter Albrecht updated LOG4J2-1045: Attachment: ConfigurationFactoryLOG4J2-1045.patch Patch of {{method public Configuration

[jira] [Updated] (LOG4J2-1045) WAS8: externalize log4j2.xml via URL resource

[ https://issues.apache.org/jira/browse/LOG4J2-1045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Günter Albrecht updated LOG4J2-1045: Description: We're working with WebSphere 8.0 and our operations team has demanded

[jira] [Updated] (LOG4J2-1045) WAS8: externalize log4j2.xml via URL resource

[ https://issues.apache.org/jira/browse/LOG4J2-1045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Günter Albrecht updated LOG4J2-1045: Description: We're working with WebSphere 8.0 and our operations team has demanded

[jira] [Updated] (LOG4J2-1045) WAS8: externalize log4j2.xml via URL resource

[ https://issues.apache.org/jira/browse/LOG4J2-1045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Günter Albrecht updated LOG4J2-1045: Description: We're working with WebSphere 8.0 and our operations team has demanded

[jira] [Updated] (LOG4J2-1045) WAS8: externalize log4j2.xml via URL resource

[ https://issues.apache.org/jira/browse/LOG4J2-1045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Günter Albrecht updated LOG4J2-1045: Description: We're working with WebSphere 8.0 and our operations team has demanded

[jira] [Updated] (LOG4J2-1045) WAS8: externalize log4j2.xml via URL resource

[ https://issues.apache.org/jira/browse/LOG4J2-1045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Günter Albrecht updated LOG4J2-1045: Description: We're working with WebSphere 8.0 and our operations team has demanded

[jira] [Updated] (LOG4J2-1045) WAS8: externalize log4j2.xml via URL resource

[ https://issues.apache.org/jira/browse/LOG4J2-1045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Günter Albrecht updated LOG4J2-1045: Description: We're working with WebSphere 8.0 and our operations team has demanded

[jira] [Updated] (LOG4J2-1045) WAS8: externalize log4j2.xml via URL resource

[ https://issues.apache.org/jira/browse/LOG4J2-1045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Günter Albrecht updated LOG4J2-1045: Description: We're working with WebSphere 8.0 and our operations team has demanded

[jira] [Updated] (LOG4J2-1045) WAS8: externalize log4j2.xml via URL resource

[ https://issues.apache.org/jira/browse/LOG4J2-1045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Günter Albrecht updated LOG4J2-1045: Description: We're working with WebSphere 8.0 and our operations team has demanded

[jira] [Commented] (LOG4J2-1023) New RewritePolicy for changing level of a log event

[ https://issues.apache.org/jira/browse/LOG4J2-1023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14581604#comment-14581604 ] Mikael Ståldal commented on LOG4J2-1023: I refer to this: {code

[jira] [Commented] (LOG4J2-1010) Possibility to set ThreadContext values in calls to Logger method

[ https://issues.apache.org/jira/browse/LOG4J2-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14581618#comment-14581618 ] Mikael Ståldal commented on LOG4J2-1010: I am developing a Scala wrapper around

[jira] [Commented] (LOG4J2-1033) SimpleLogger creates unnecessary Map objects by calling ThreadContext.getContext() instead of getImmutableContext()

[ https://issues.apache.org/jira/browse/LOG4J2-1033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14564378#comment-14564378 ] Mikael Ståldal commented on LOG4J2-1033: Your fix looks good. I do not have

[jira] [Commented] (LOG4J2-1033) SimpleLogger creates unnecessary Map objects by calling ThreadContext.getContext() instead of getImmutableContext()

[ https://issues.apache.org/jira/browse/LOG4J2-1033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14564986#comment-14564986 ] Mikael Ståldal commented on LOG4J2-1033: Now when this is fixed, what

[jira] [Commented] (LOG4J2-1025) Custom java.util.logging.Level gives null Log4j Level

[ https://issues.apache.org/jira/browse/LOG4J2-1025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14567062#comment-14567062 ] Mikael Ståldal commented on LOG4J2-1025: A method does not have to return

[jira] [Commented] (LOG4J2-1033) SimpleLogger creates unnecessary Map objects by calling ThreadContext.getContext() instead of getImmutableContext()

[ https://issues.apache.org/jira/browse/LOG4J2-1033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14567554#comment-14567554 ] Mikael Ståldal commented on LOG4J2-1033: I am working on an alternative

[jira] [Commented] (LOG4J2-1025) Custom java.util.logging.Level gives null Log4j Level

[ https://issues.apache.org/jira/browse/LOG4J2-1025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14567548#comment-14567548 ] Mikael Ståldal commented on LOG4J2-1025: I think we have a potential thread

[jira] [Created] (LOG4J2-1072) Parameter mdcId is missing in documentation of SyslogAppender

Martin Schröder created LOG4J2-1072: --- Summary: Parameter mdcId is missing in documentation of SyslogAppender Key: LOG4J2-1072 URL: https://issues.apache.org/jira/browse/LOG4J2-1072 Project: Log4j 2

[jira] [Commented] (LOG4J2-1023) New RewritePolicy for changing level of a log event

[ https://issues.apache.org/jira/browse/LOG4J2-1023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14581629#comment-14581629 ] Mikael Ståldal commented on LOG4J2-1023: Then we are all set. (I have already

[jira] [Commented] (LOG4J2-767) Liquibase integration

[ https://issues.apache.org/jira/browse/LOG4J2-767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14581641#comment-14581641 ] Mikael Ståldal commented on LOG4J2-767: --- I am not using Loqibase anymore, but I

[jira] [Commented] (LOG4J2-1025) Custom java.util.logging.Level gives null Log4j Level

[ https://issues.apache.org/jira/browse/LOG4J2-1025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14555781#comment-14555781 ] Mikael Ståldal commented on LOG4J2-1025: In any case, I would suggest to add

[jira] [Commented] (LOG4J2-1023) New RewritePolicy for changing level of a log event

[ https://issues.apache.org/jira/browse/LOG4J2-1023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14555787#comment-14555787 ] Mikael Ståldal commented on LOG4J2-1023: What about the name

[jira] [Commented] (LOG4J2-1023) New RewritePolicy for changing level of a log event

[ https://issues.apache.org/jira/browse/LOG4J2-1023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14554507#comment-14554507 ] Mikael Ståldal commented on LOG4J2-1023: Thanks, this is exactly what I want

[jira] [Created] (LOG4J2-1025) Custom java.util.logging.Level gives null Log4j Level

Mikael Ståldal created LOG4J2-1025: -- Summary: Custom java.util.logging.Level gives null Log4j Level Key: LOG4J2-1025 URL: https://issues.apache.org/jira/browse/LOG4J2-1025 Project: Log4j 2

[jira] [Commented] (LOG4J2-1010) Possibility to set ThreadContext values in calls to Logger method

[ https://issues.apache.org/jira/browse/LOG4J2-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14554362#comment-14554362 ] Mikael Ståldal commented on LOG4J2-1010: It is not mine GelfLayout (any more

[jira] [Commented] (LOG4J2-952) FAQ: How do I configure log4j2 programmatically in code without a configuration file?

[ https://issues.apache.org/jira/browse/LOG4J2-952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14694867#comment-14694867 ] Mikael Ståldal commented on LOG4J2-952: --- I can see a problem with this, a simple

[jira] [Commented] (LOG4J2-952) FAQ: How do I configure log4j2 programmatically in code without a configuration file?

[ https://issues.apache.org/jira/browse/LOG4J2-952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14695243#comment-14695243 ] Mikael Ståldal commented on LOG4J2-952: --- My code was only meant to be an example

[jira] [Commented] (LOG4J2-952) FAQ: How do I configure log4j2 programmatically in code without a configuration file?

[ https://issues.apache.org/jira/browse/LOG4J2-952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14695279#comment-14695279 ] Mikael Ståldal commented on LOG4J2-952: --- But if we can make it report more errors

[jira] [Commented] (LOG4J2-952) FAQ: How do I configure log4j2 programmatically in code without a configuration file?

[ https://issues.apache.org/jira/browse/LOG4J2-952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14695325#comment-14695325 ] Mikael Ståldal commented on LOG4J2-952: --- I don't understand what the disadvantage

[jira] [Commented] (LOG4J2-952) FAQ: How do I configure log4j2 programmatically in code without a configuration file?

[ https://issues.apache.org/jira/browse/LOG4J2-952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14695358#comment-14695358 ] Mikael Ståldal commented on LOG4J2-952: --- Having some extra imports is not a big deal

[jira] [Comment Edited] (LOG4J2-1103) Failover appender does not fail over

[ https://issues.apache.org/jira/browse/LOG4J2-1103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14709187#comment-14709187 ] Martin Schröder edited comment on LOG4J2-1103 at 8/24/15 12:38 PM

[jira] [Commented] (LOG4J2-1103) Failover appender does not fail over

[ https://issues.apache.org/jira/browse/LOG4J2-1103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14709187#comment-14709187 ] Martin Schröder commented on LOG4J2-1103: - If we use (instead

[jira] [Commented] (LOG4J2-1103) Failover appender does not fail over

[ https://issues.apache.org/jira/browse/LOG4J2-1103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14709195#comment-14709195 ] Martin Schröder commented on LOG4J2-1103: - See also http://stackoverflow.com/q

[jira] [Updated] (LOG4J2-1103) Failover appender does not fail over

[ https://issues.apache.org/jira/browse/LOG4J2-1103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Schröder updated LOG4J2-1103: Attachment: log4j2.xml Failover appender does not fail over

[jira] [Comment Edited] (LOG4J2-1103) Failover appender does not fail over

[ https://issues.apache.org/jira/browse/LOG4J2-1103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14709187#comment-14709187 ] Martin Schröder edited comment on LOG4J2-1103 at 8/24/15 12:39 PM

[jira] [Comment Edited] (LOG4J2-1103) Failover appender does not fail over

[ https://issues.apache.org/jira/browse/LOG4J2-1103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14709187#comment-14709187 ] Martin Schröder edited comment on LOG4J2-1103 at 8/24/15 12:38 PM

[jira] [Comment Edited] (LOG4J2-1103) Failover appender does not fail over

[ https://issues.apache.org/jira/browse/LOG4J2-1103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14709187#comment-14709187 ] Martin Schröder edited comment on LOG4J2-1103 at 8/24/15 12:41 PM

[jira] [Created] (LOG4J2-1103) Failover appender does not fail over

Martin Schröder created LOG4J2-1103: --- Summary: Failover appender does not fail over Key: LOG4J2-1103 URL: https://issues.apache.org/jira/browse/LOG4J2-1103 Project: Log4j 2 Issue Type: Bug

[jira] [Commented] (LOG4J2-1094) Multi thread initialization problem

[ https://issues.apache.org/jira/browse/LOG4J2-1094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14709141#comment-14709141 ] Mikael Ståldal commented on LOG4J2-1094: You should be careful with catching

[jira] [Commented] (LOG4J2-599) Support lambda functions (or similar) for log message parameters

[ https://issues.apache.org/jira/browse/LOG4J2-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14658274#comment-14658274 ] Mikael Ståldal commented on LOG4J2-599: --- For Scala, the preferred approach

[jira] [Comment Edited] (LOG4J2-599) Support lambda functions (or similar) for log message parameters

[ https://issues.apache.org/jira/browse/LOG4J2-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14658274#comment-14658274 ] Mikael Ståldal edited comment on LOG4J2-599 at 8/5/15 2:24 PM

[jira] [Commented] (LOG4J2-599) Support lambda functions (or similar) for log message parameters

[ https://issues.apache.org/jira/browse/LOG4J2-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14658339#comment-14658339 ] Mikael Ståldal commented on LOG4J2-599: --- I agree that this would be useful in Java 8

[jira] [Commented] (LOG4J2-599) Support lambda functions (or similar) for log message parameters

[ https://issues.apache.org/jira/browse/LOG4J2-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14661487#comment-14661487 ] Mikael Ståldal commented on LOG4J2-599: --- An argument for going with technology based

[jira] [Commented] (LOG4J2-1010) Possibility to set ThreadContext values in calls to Logger method

[ https://issues.apache.org/jira/browse/LOG4J2-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14659863#comment-14659863 ] Mikael Ståldal commented on LOG4J2-1010: Thanks Ralph, this looks really

[jira] [Comment Edited] (LOG4J2-1010) Possibility to set ThreadContext values in calls to Logger method

[ https://issues.apache.org/jira/browse/LOG4J2-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14659995#comment-14659995 ] Mikael Ståldal edited comment on LOG4J2-1010 at 8/6/15 1:19 PM

[jira] [Commented] (LOG4J2-952) FAQ: How do I configure log4j2 programmatically in code without a configuration file?

[ https://issues.apache.org/jira/browse/LOG4J2-952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14695431#comment-14695431 ] Mikael Ståldal commented on LOG4J2-952: --- BTW, we could make the XML literal approach

[jira] [Comment Edited] (LOG4J2-952) FAQ: How do I configure log4j2 programmatically in code without a configuration file?

[ https://issues.apache.org/jira/browse/LOG4J2-952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14695431#comment-14695431 ] Mikael Ståldal edited comment on LOG4J2-952 at 8/13/15 4:03 PM

[jira] [Commented] (LOG4J2-1010) Possibility to set ThreadContext values in calls to Logger method

[ https://issues.apache.org/jira/browse/LOG4J2-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14679871#comment-14679871 ] Mikael Ståldal commented on LOG4J2-1010: Given the current architecture, I don't

[jira] [Commented] (LOG4J2-1010) Possibility to set ThreadContext values in calls to Logger method

[ https://issues.apache.org/jira/browse/LOG4J2-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14659997#comment-14659997 ] Mikael Ståldal commented on LOG4J2-1010: I tried to create my own custom Message

[jira] [Commented] (LOG4J2-1010) Possibility to set ThreadContext values in calls to Logger method

[ https://issues.apache.org/jira/browse/LOG4J2-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14659995#comment-14659995 ] Mikael Ståldal commented on LOG4J2-1010: After some testing, I realized

[jira] [Commented] (LOG4J2-599) Support lambda functions (or similar) for log message parameters

[ https://issues.apache.org/jira/browse/LOG4J2-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14659651#comment-14659651 ] Mikael Ståldal commented on LOG4J2-599: --- Another approach could be to keep

[jira] [Commented] (LOG4J2-1010) Possibility to set ThreadContext values in calls to Logger method

[ https://issues.apache.org/jira/browse/LOG4J2-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14640339#comment-14640339 ] Mikael Ståldal commented on LOG4J2-1010: It is still not clear to me how to use

[jira] [Commented] (LOG4J2-1045) Externalize log4j2.xml via URL resource

[ https://issues.apache.org/jira/browse/LOG4J2-1045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14631378#comment-14631378 ] Günter Albrecht commented on LOG4J2-1045: - It's not possible to test the nightly

[jira] [Commented] (LOG4J2-1045) Externalize log4j2.xml via URL resource

[ https://issues.apache.org/jira/browse/LOG4J2-1045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14632326#comment-14632326 ] Günter Albrecht commented on LOG4J2-1045: - With WebSphere 8.0 it's not possible

[jira] [Commented] (LOG4J2-1161) Builder like pattern to add values to MapMessage

[ https://issues.apache.org/jira/browse/LOG4J2-1161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14970951#comment-14970951 ] Mikael Ståldal commented on LOG4J2-1161: Renamed to "with". > Builder like pattern

[jira] [Resolved] (LOG4J2-1161) Builder like pattern to add values to MapMessage

[ https://issues.apache.org/jira/browse/LOG4J2-1161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal resolved LOG4J2-1161. Resolution: Fixed Merged to master > Builder like pattern to add values to MapMess

[jira] [Commented] (LOG4J2-1181) Scala wrapper for Log4j 2 API

[ https://issues.apache.org/jira/browse/LOG4J2-1181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14978777#comment-14978777 ] Mikael Ståldal commented on LOG4J2-1181: Work in progress in Git branch LOG4J-1181. > Sc

[jira] [Commented] (LOG4J2-1181) Scala wrapper for Log4j 2 API

[ https://issues.apache.org/jira/browse/LOG4J2-1181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14996791#comment-14996791 ] Mikael Ståldal commented on LOG4J2-1181: I have added some documentation now. > Scala wrap

[jira] [Commented] (LOG4J2-649) Close a dynamically created appender

[ https://issues.apache.org/jira/browse/LOG4J2-649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15006354#comment-15006354 ] Mikael Ståldal commented on LOG4J2-649: --- Have we thought about what will happen if an appender hang

[jira] [Created] (LOG4J2-1196) MongoDbConnection does not close MongoClient

René Zanner created LOG4J2-1196: --- Summary: MongoDbConnection does not close MongoClient Key: LOG4J2-1196 URL: https://issues.apache.org/jira/browse/LOG4J2-1196 Project: Log4j 2 Issue Type: Bug

[jira] [Updated] (LOG4J2-1196) MongoDbConnection does not close MongoClient

[ https://issues.apache.org/jira/browse/LOG4J2-1196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] René Zanner updated LOG4J2-1196: Affects Version/s: 2.3 2.4 2.4.1 > MongoDbConnect

[jira] [Commented] (LOG4J2-1180) Logger cache does not account for message factory

[ https://issues.apache.org/jira/browse/LOG4J2-1180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14985251#comment-14985251 ] Mikael Ståldal commented on LOG4J2-1180: In LoggerContext.java and SimpleLoggerContext.java

[jira] [Commented] (LOG4J2-1181) Scala wrapper for Log4j 2 API

[ https://issues.apache.org/jira/browse/LOG4J2-1181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14985289#comment-14985289 ] Mikael Ståldal commented on LOG4J2-1181: I have never used Eclipse with Scala, I use IntelliJ

[jira] [Comment Edited] (LOG4J2-1181) Scala wrapper for Log4j 2 API

[ https://issues.apache.org/jira/browse/LOG4J2-1181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14985297#comment-14985297 ] Mikael Ståldal edited comment on LOG4J2-1181 at 11/2/15 2:42 PM

[jira] [Commented] (LOG4J2-1181) Scala wrapper for Log4j 2 API

[ https://issues.apache.org/jira/browse/LOG4J2-1181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14985297#comment-14985297 ] Mikael Ståldal commented on LOG4J2-1181: {{Logging}} is a wrapper for {{LogManager

[jira] [Commented] (LOG4J2-1180) Logger cache does not account for message factory

[ https://issues.apache.org/jira/browse/LOG4J2-1180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14985282#comment-14985282 ] Mikael Ståldal commented on LOG4J2-1180: It seems to work though. > Logger cache d

[jira] [Commented] (LOG4J2-1181) Scala wrapper for Log4j 2 API

[ https://issues.apache.org/jira/browse/LOG4J2-1181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14985305#comment-14985305 ] Mikael Ståldal commented on LOG4J2-1181: Seems reasonable to rename to log4j-api-scala_*version

[jira] [Comment Edited] (LOG4J2-1180) Logger cache does not account for message factory

[ https://issues.apache.org/jira/browse/LOG4J2-1180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14985251#comment-14985251 ] Mikael Ståldal edited comment on LOG4J2-1180 at 11/2/15 3:43 PM

[jira] [Commented] (LOG4J2-1181) Scala wrapper for Log4j 2 API

[ https://issues.apache.org/jira/browse/LOG4J2-1181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14986960#comment-14986960 ] Mikael Ståldal commented on LOG4J2-1181: It is called {{Logging}} since it is used in another way

[jira] [Commented] (LOG4J2-1181) Scala wrapper for Log4j 2 API

[ https://issues.apache.org/jira/browse/LOG4J2-1181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14986943#comment-14986943 ] Mikael Ståldal commented on LOG4J2-1181: I know about the branch naming, I made a mistake when

[jira] [Commented] (LOG4J2-1181) Scala wrapper for Log4j 2 API

[ https://issues.apache.org/jira/browse/LOG4J2-1181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14986952#comment-14986952 ] Mikael Ståldal commented on LOG4J2-1181: Yes, we have a {{Logger}} class in both. > Sc

[jira] [Issue Comment Deleted] (LOG4J2-1181) Scala wrapper for Log4j 2 API

[ https://issues.apache.org/jira/browse/LOG4J2-1181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal updated LOG4J2-1181: --- Comment: was deleted (was: I know about the branch naming, I made a mistake when creating

[jira] [Commented] (LOG4J2-1181) Scala wrapper for Log4j 2 API

[ https://issues.apache.org/jira/browse/LOG4J2-1181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14986944#comment-14986944 ] Mikael Ståldal commented on LOG4J2-1181: I know, I made a mistake when creating this branch

[jira] [Commented] (LOG4J2-1181) Scala wrapper for Log4j 2 API

[ https://issues.apache.org/jira/browse/LOG4J2-1181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14982494#comment-14982494 ] Mikael Ståldal commented on LOG4J2-1181: I think it looks good now. What do you think? > Sc

[jira] [Updated] (LOG4J2-1192) Dynamic Subject for SMTP Appender

[ https://issues.apache.org/jira/browse/LOG4J2-1192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jörg Bretschneider updated LOG4J2-1192: --- Description: It is annoying to have log messages sent to users via SMTP Appender

[jira] [Commented] (LOG4J2-1180) Logger cache does not account for message factory

[ https://issues.apache.org/jira/browse/LOG4J2-1180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14985493#comment-14985493 ] Mikael Ståldal commented on LOG4J2-1180: Seems to work fine. > Logger cache does not acco

[jira] [Commented] (LOG4J2-1180) Logger cache does not account for message factory

[ https://issues.apache.org/jira/browse/LOG4J2-1180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14985481#comment-14985481 ] Mikael Ståldal commented on LOG4J2-1180: Looks OK, but is this comment (in LoggerContext.java

[jira] [Commented] (LOG4J2-1195) KafkaAppender doesn't work with SerializedLayout

[ https://issues.apache.org/jira/browse/LOG4J2-1195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14993349#comment-14993349 ] Mikael Ståldal commented on LOG4J2-1195: And may I ask why you use a custom Kafka serializer here

[jira] [Commented] (LOG4J2-1195) KafkaAppender doesn't work with SerializedLayout

[ https://issues.apache.org/jira/browse/LOG4J2-1195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14993348#comment-14993348 ] Mikael Ståldal commented on LOG4J2-1195: Can you share the source code

[jira] [Created] (LOG4J2-1192) Dynamic Subject for SMTP Appender

Jörg Bretschneider created LOG4J2-1192: -- Summary: Dynamic Subject for SMTP Appender Key: LOG4J2-1192 URL: https://issues.apache.org/jira/browse/LOG4J2-1192 Project: Log4j 2 Issue Type

[jira] [Updated] (LOG4J2-1192) Dynamic Subject for SMTP Appender

[ https://issues.apache.org/jira/browse/LOG4J2-1192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jörg Bretschneider updated LOG4J2-1192: --- Description: It is annoying to have log messages sent to users via SMTP Appender

[jira] [Updated] (LOG4J2-1192) Dynamic Subject for SMTP Appender

[ https://issues.apache.org/jira/browse/LOG4J2-1192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jörg Bretschneider updated LOG4J2-1192: --- Description: It is annoying to have log messages sent to users via SMTP Appender

<    1   2   3   4   5   6   7   8   9   10   >