[jira] [Commented] (LOG4J2-1119) Disable JMX by default

[ https://issues.apache.org/jira/browse/LOG4J2-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14739962#comment-14739962 ] Remko Popma commented on LOG4J2-1119: - I think I acted too quickly here. The java run

[jira] [Reopened] (LOG4J2-1119) Disable JMX by default

[ https://issues.apache.org/jira/browse/LOG4J2-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma reopened LOG4J2-1119: - I just saw your message now. I do prefer a positive name as well (users can enable it now by saying

[jira] [Closed] (LOG4J2-1119) Disable JMX by default

[ https://issues.apache.org/jira/browse/LOG4J2-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma closed LOG4J2-1119. --- > Disable JMX by default > -- > > Key: LOG4J2-1119 >

[jira] [Resolved] (LOG4J2-1119) Disable JMX by default

[ https://issues.apache.org/jira/browse/LOG4J2-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-1119. - Resolution: Fixed Fixed in master in commit 6084061. > Disable JMX by default >

[jira] [Commented] (LOG4J2-1119) Disable JMX by default

[ https://issues.apache.org/jira/browse/LOG4J2-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14739861#comment-14739861 ] Gary Gregory commented on LOG4J2-1119: -- I think it is OK to change the prop name. Or

[jira] [Updated] (LOG4J2-1119) Disable JMX by default

[ https://issues.apache.org/jira/browse/LOG4J2-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-1119: Priority: Critical (was: Blocker) Changed priority to "Critical" since there is a workaround: user

[jira] [Commented] (LOG4J2-1119) Disable JMX by default

[ https://issues.apache.org/jira/browse/LOG4J2-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14739477#comment-14739477 ] Gary Gregory commented on LOG4J2-1119: -- But I would not call it a "Blocker". > Disa

[jira] [Commented] (LOG4J2-1119) Disable JMX by default

[ https://issues.apache.org/jira/browse/LOG4J2-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14739475#comment-14739475 ] Gary Gregory commented on LOG4J2-1119: -- I like it, that will make Log4j more lightwe

Fwd: logging-log4j2 git commit: Checkstyle fixes; use loop over enum values instead of explicitly specifying enum values; fixed typo in enum value name

Nice! Gary -- Forwarded message -- From: Date: Thu, Sep 10, 2015 at 9:09 AM Subject: logging-log4j2 git commit: Checkstyle fixes; use loop over enum values instead of explicitly specifying enum values; fixed typo in enum value name To: [email protected] Repository: logg

Re: logging-log4j2 git commit: Add missing license headers

Looking at Log4jLogEvent::hashCode, there are many unnecessary Checkstyle MagicNumber warnings for this. I've tried surrounding the offending lines between //Check:OFF: MagicNumber and // Check:ON: MagicNumber comments, and added a SuppressionCommentFilter to /logging-log4j2/checkstyle.xml but Chec

[jira] [Created] (LOG4J2-1119) Disable JMX by default

Remko Popma created LOG4J2-1119: --- Summary: Disable JMX by default Key: LOG4J2-1119 URL: https://issues.apache.org/jira/browse/LOG4J2-1119 Project: Log4j 2 Issue Type: Improvement Comp

[jira] [Closed] (LOG4J2-1118) Lambda support for custom log levels: update Logger wrapper generator tool

[ https://issues.apache.org/jira/browse/LOG4J2-1118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma closed LOG4J2-1118. --- > Lambda support for custom log levels: update Logger wrapper generator tool > --

[jira] [Resolved] (LOG4J2-1118) Lambda support for custom log levels: update Logger wrapper generator tool

[ https://issues.apache.org/jira/browse/LOG4J2-1118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-1118. - Resolution: Fixed Fixed in master in commit 278015d7. The Generate tool now generates code for t

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

See - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]

Jenkins build became unstable: Log4j 2.x #1358

See - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]

[jira] [Updated] (LOG4J2-1118) Lambda support for custom log levels: update Logger wrapper generator tool

[ https://issues.apache.org/jira/browse/LOG4J2-1118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-1118: Summary: Lambda support for custom log levels: update Logger wrapper generator tool (was: Update L

[jira] [Updated] (LOG4J2-1118) Update Logger wrapper generator tool for lambda support methods added to Logger

[ https://issues.apache.org/jira/browse/LOG4J2-1118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-1118: Summary: Update Logger wrapper generator tool for lambda support methods added to Logger (was: Upd

[jira] [Created] (LOG4J2-1118) Update Generate tool for lambda support methods added to Logger

Remko Popma created LOG4J2-1118: --- Summary: Update Generate tool for lambda support methods added to Logger Key: LOG4J2-1118 URL: https://issues.apache.org/jira/browse/LOG4J2-1118 Project: Log4j 2

[jira] [Commented] (LOG4J2-1116) upgrade to log4j2 causes too frequent minor gc

[ https://issues.apache.org/jira/browse/LOG4J2-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14738579#comment-14738579 ] Remko Popma commented on LOG4J2-1116: - How can I reproduce the problem? > upgrade to

[jira] [Commented] (LOG4J2-1115) Allow fine-grained control over which properties are passed to child threads.

[ https://issues.apache.org/jira/browse/LOG4J2-1115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14738497#comment-14738497 ] Mikael Ståldal commented on LOG4J2-1115: Perhaps you should take this into consid

[jira] [Created] (LOG4J2-1117) OutputStreamManager in ConsoleAppender leaking managers?

Marcus Thiesen created LOG4J2-1117: -- Summary: OutputStreamManager in ConsoleAppender leaking managers? Key: LOG4J2-1117 URL: https://issues.apache.org/jira/browse/LOG4J2-1117 Project: Log4j 2

[jira] [Created] (LOG4J2-1116) upgrade to log4j2 causes too frequent minor gc

Mingjiang Shi created LOG4J2-1116: - Summary: upgrade to log4j2 causes too frequent minor gc Key: LOG4J2-1116 URL: https://issues.apache.org/jira/browse/LOG4J2-1116 Project: Log4j 2 Issue Type