[jira] [Commented] (LOG4J2-435) Feature request: auto-delete older log files

2015-11-13 Thread Remko Popma (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15005216#comment-15005216 ] Remko Popma commented on LOG4J2-435: Update: I am finding that Java 7's [Files.walkFi

[jira] [Updated] (LOG4J2-826) Manage a single Clock and NanoClock instance in Configuration

2015-11-13 Thread Remko Popma (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-826: --- Description: LOG4J2-819 brought to light a number of weaknesses and inconsistencies in the way Clocks

[jira] [Updated] (LOG4J2-826) Manage a single Clock and NanoClock instance in Configuration

2015-11-13 Thread Remko Popma (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-826: --- Summary: Manage a single Clock and NanoClock instance in Configuration (was: Manage a single Clock in

[jira] [Updated] (LOG4J2-826) Manage a single Clock instance in LoggerContext

2015-11-13 Thread Remko Popma (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-826: --- Description: LOG4J2-819 brought to light a number of weaknesses and inconsistencies in the way Clocks

[jira] [Updated] (LOG4J2-435) Feature request: auto-delete older log files

2015-11-13 Thread Remko Popma (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-435: --- Description: Original description: {quote} DefaultRolloverStrategy max attribute only applies if you

[jira] [Updated] (LOG4J2-1171) LoggerContext names in web apps are cryptic

2015-11-13 Thread Remko Popma (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-1171: Summary: LoggerContext names in web apps are cryptic (was: LoggerContext names are cryptic) > Log

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

2015-11-13 Thread Aleksey Zvolinsky (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15004020#comment-15004020 ] Aleksey Zvolinsky commented on LOG4J2-649: -- [~ralph.go...@dslextreme.com], Do yo

Re: Out of date team list

2015-11-13 Thread Mikael Ståldal
So what are you supposed to put in your .rdf file? This perhaps: Log4j 2 http://logging.apache.org/log4j/2.x/"/> On Thu, Nov 12, 2015 at 9:05 PM, Paul Benedict wrote: > That's all generated content. I believe you use this to manage it: > http://people.apache.org/foaf/index.html > > > Cheers

Re: Layouts requiring headers vs. message based appenders

2015-11-13 Thread Mikael Ståldal
I don't think so, this is what is expected. It currently says: The Layout to use to format the LogEvent. If you do not specify a layout, the appender will send the formatted message to Kafka as a UTF-8 encoded string. On Thu, Nov 12, 2015 at 8:45 PM, Gary Gregory wrote: > Does that need to be