[jira] [Comment Edited] (LOG4J2-403) MongoDB appender, username and password should be optional.

2015-05-21 Thread Gary Gregory (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14555614#comment-14555614 ] Gary Gregory edited comment on LOG4J2-403 at 5/22/15 5:35 AM: --

[jira] [Commented] (LOG4J2-403) MongoDB appender, username and password should be optional.

2015-05-21 Thread Gary Gregory (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14555614#comment-14555614 ] Gary Gregory commented on LOG4J2-403: - In {{org.apache.logging.log4j.nosql.appender.m

[jira] [Closed] (LOG4J2-1026) HighlightConverter does not obey noConsoleNoAnsi

2015-05-21 Thread Gary Gregory (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-1026. Resolution: Fixed > HighlightConverter does not obey noConsoleNoAnsi >

[jira] [Created] (LOG4J2-1026) HighlightConverter does not obey noConsoleNoAnsi

2015-05-21 Thread Gary Gregory (JIRA)
Gary Gregory created LOG4J2-1026: Summary: HighlightConverter does not obey noConsoleNoAnsi Key: LOG4J2-1026 URL: https://issues.apache.org/jira/browse/LOG4J2-1026 Project: Log4j 2 Issue Type

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

2015-05-21 Thread Gary Gregory (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14554967#comment-14554967 ] Gary Gregory commented on LOG4J2-1025: -- A smarter converter, perhaps a subclass of {

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

2015-05-21 Thread Gary Gregory (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14554837#comment-14554837 ] Gary Gregory commented on LOG4J2-1023: -- Oops, I meant for the plugin name to match t

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

2015-05-21 Thread Gary Gregory (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14554732#comment-14554732 ] Gary Gregory commented on LOG4J2-1025: -- You can fix this today by specifying the sys

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

2015-05-21 Thread Gary Gregory (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1025: - Affects Version/s: (was: 2.4) 2.3 Changed "Affects version" from 2.3 t

[jira] [Commented] (LOG4J2-403) MongoDB appender, username and password should be optional.

2015-05-21 Thread Jeremy Lautman (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14554704#comment-14554704 ] Jeremy Lautman commented on LOG4J2-403: --- Just came across this old story. While havi

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

2015-05-21 Thread JIRA
[ https://issues.apache.org/jira/browse/LOG4J2-1023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14554507#comment-14554507 ] Mikael Ståldal commented on LOG4J2-1023: Thanks, this is exactly what I want. Ju

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

2015-05-21 Thread JIRA
[ https://issues.apache.org/jira/browse/LOG4J2-1025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14554378#comment-14554378 ] Mikael Ståldal commented on LOG4J2-1025: The documentation says: bq. Using the d

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

2015-05-21 Thread JIRA
[ https://issues.apache.org/jira/browse/LOG4J2-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14554362#comment-14554362 ] Mikael Ståldal commented on LOG4J2-1010: It is not mine GelfLayout (any more), it

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

2015-05-21 Thread JIRA
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 I

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

2015-05-21 Thread Remko Popma (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14554330#comment-14554330 ] Remko Popma commented on LOG4J2-1010: - Your GelfLayout can detect GelfMessages and ta

[jira] [Created] (LOG4J2-1024) log4j2.xml not found by default in WEB-INF folder

2015-05-21 Thread Patrick Zimmermann (JIRA)
Patrick Zimmermann created LOG4J2-1024: -- Summary: log4j2.xml not found by default in WEB-INF folder Key: LOG4J2-1024 URL: https://issues.apache.org/jira/browse/LOG4J2-1024 Project: Log4j 2