[jira] [Comment Edited] (LOG4J2-1159) ThreadLocal leaks in Tomcat8 (org.apache.logging.log4j.core.async.AsyncLogger.Info)

[ https://issues.apache.org/jira/browse/LOG4J2-1159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14962924#comment-14962924 ] Remko Popma edited comment on LOG4J2-1159 at 10/19/15 6:46 AM:

[jira] [Commented] (LOG4J2-1159) ThreadLocal leaks in Tomcat8 (org.apache.logging.log4j.core.async.AsyncLogger.Info)

[ https://issues.apache.org/jira/browse/LOG4J2-1159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14962924#comment-14962924 ] Remko Popma commented on LOG4J2-1159: - Interestingly, the sample web app does not use

[jira] [Updated] (LOG4J2-1159) ThreadLocal leaks in Tomcat8 (org.apache.logging.log4j.core.async.AsyncLogger.Info)

[ https://issues.apache.org/jira/browse/LOG4J2-1159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-1159: Description: (Regression of LOG4J2-323) Since v2.4 there a TreadLocal warnings reported by Tomcat

[jira] [Assigned] (LOG4J2-1159) ThreadLocal leaks in Tomcat8 (org.apache.logging.log4j.core.async.AsyncLogger.Info)

[ https://issues.apache.org/jira/browse/LOG4J2-1159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma reassigned LOG4J2-1159: --- Assignee: Remko Popma > ThreadLocal leaks in Tomcat8 > (org.apache.logging.log4j.core.async

[jira] [Updated] (LOG4J2-1050) Add a Log4jLookup class to help write log files relative to log4j2.xml

[ https://issues.apache.org/jira/browse/LOG4J2-1050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-1050: Priority: Critical (was: Major) > Add a Log4jLookup class to help write log files relative to log4

[jira] [Updated] (LOG4J2-836) Binary Logging Appender

[ https://issues.apache.org/jira/browse/LOG4J2-836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-836: --- Priority: Minor (was: Major) > Binary Logging Appender > --- > >

[jira] [Updated] (LOG4J2-850) [Perf] Add performance tests for MemoryMappedFileAppender

[ https://issues.apache.org/jira/browse/LOG4J2-850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-850: --- Priority: Minor (was: Major) > [Perf] Add performance tests for MemoryMappedFileAppender > --

[jira] [Updated] (LOG4J2-1050) Add a Log4jLookup class to help write log files relative to log4j2.xml

[ https://issues.apache.org/jira/browse/LOG4J2-1050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-1050: Priority: Major (was: Minor) > Add a Log4jLookup class to help write log files relative to log4j2.

[jira] [Updated] (LOG4J2-323) ThreadLocal-leak on tomcat shutdown when using async logging

[ https://issues.apache.org/jira/browse/LOG4J2-323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-323: --- Priority: Major (was: Minor) > ThreadLocal-leak on tomcat shutdown when using async logging > ---

[jira] [Updated] (LOG4J2-1159) ThreadLocal leaks in Tomcat8 (org.apache.logging.log4j.core.async.AsyncLogger.Info)

[ https://issues.apache.org/jira/browse/LOG4J2-1159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-1159: Priority: Major (was: Minor) > ThreadLocal leaks in Tomcat8 > (org.apache.logging.log4j.core.asyn

[jira] [Commented] (LOG4J2-1162) Memory-mapped file appender creates null-padded files.

[ https://issues.apache.org/jira/browse/LOG4J2-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14962756#comment-14962756 ] Gary Gregory commented on LOG4J2-1162: -- The test does not create the LC explicitly,

[jira] [Closed] (LOG4J2-1166) Applications using Log4j-2.5 with monitorInterval never shut down

[ https://issues.apache.org/jira/browse/LOG4J2-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma closed LOG4J2-1166. --- > Applications using Log4j-2.5 with monitorInterval never shut down > ---

[jira] [Resolved] (LOG4J2-1164) Configuration watch thread causes Tomcat memory leak

[ https://issues.apache.org/jira/browse/LOG4J2-1164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-1164. - Resolution: Fixed Addressed and fixed in LOG4J2-1166. > Configuration watch thread causes Tomcat

[jira] [Closed] (LOG4J2-1164) Configuration watch thread causes Tomcat memory leak

[ https://issues.apache.org/jira/browse/LOG4J2-1164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma closed LOG4J2-1164. --- Assignee: Remko Popma > Configuration watch thread causes Tomcat memory leak > --

[jira] [Commented] (LOG4J2-1162) Memory-mapped file appender creates null-padded files.

[ https://issues.apache.org/jira/browse/LOG4J2-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14962688#comment-14962688 ] Remko Popma commented on LOG4J2-1162: - I just tested your config with a simple standa

[jira] [Commented] (LOG4J2-671) Property using ${date:} is evaluated multiple times across appenders

[ https://issues.apache.org/jira/browse/LOG4J2-671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14962561#comment-14962561 ] Ralph Goers commented on LOG4J2-671: That seems very confusing. What would the differe

[jira] [Commented] (LOG4J2-671) Property using ${date:} is evaluated multiple times across appenders

[ https://issues.apache.org/jira/browse/LOG4J2-671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14962551#comment-14962551 ] Gary Gregory commented on LOG4J2-671: - I think I would call the plugin "now" or "times

[jira] [Commented] (LOG4J2-1162) Memory-mapped file appender creates null-padded files.

[ https://issues.apache.org/jira/browse/LOG4J2-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14962538#comment-14962538 ] Gary Gregory commented on LOG4J2-1162: -- But we still have an issue: If run a unit te

[jira] [Commented] (LOG4J2-1162) Memory-mapped file appender creates null-padded files.

[ https://issues.apache.org/jira/browse/LOG4J2-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14962530#comment-14962530 ] Remko Popma commented on LOG4J2-1162: - Thanks! > Memory-mapped file appender creates

[jira] [Commented] (LOG4J2-1162) Memory-mapped file appender creates null-padded files.

[ https://issues.apache.org/jira/browse/LOG4J2-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14962529#comment-14962529 ] Remko Popma commented on LOG4J2-1162: - Good, glad to hear that! > Memory-mapped file

[jira] [Commented] (LOG4J2-1162) Memory-mapped file appender creates null-padded files.

[ https://issues.apache.org/jira/browse/LOG4J2-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14962526#comment-14962526 ] Gary Gregory commented on LOG4J2-1162: -- That fixed it! It took longer than I thought

[jira] [Comment Edited] (LOG4J2-671) Property using ${date:} is evaluated multiple times across appenders

[ https://issues.apache.org/jira/browse/LOG4J2-671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14962435#comment-14962435 ] Remko Popma edited comment on LOG4J2-671 at 10/18/15 5:35 PM: --

[jira] [Commented] (LOG4J2-1162) Memory-mapped file appender creates null-padded files.

[ https://issues.apache.org/jira/browse/LOG4J2-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14962520#comment-14962520 ] Remko Popma commented on LOG4J2-1162: - That is strange. From the log it looks like {{

[jira] [Commented] (LOG4J2-671) Property using ${date:} is evaluated multiple times across appenders

[ https://issues.apache.org/jira/browse/LOG4J2-671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14962516#comment-14962516 ] Ralph Goers commented on LOG4J2-671: Normally, all variables with a single '$' are res

[jira] [Resolved] (LOG4J2-978) log4j2 2.2 made breaking changes to public classes

[ https://issues.apache.org/jira/browse/LOG4J2-978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-978. Resolution: Fixed Fix Version/s: 2.4 As of 2.4, Log4j provides an API for [Programmatic Conf

[jira] [Updated] (LOG4J2-1032) Rollover startegy failing on high load

[ https://issues.apache.org/jira/browse/LOG4J2-1032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-1032: Description: On windows virtual machines, the roll over strategy simply fails and the log size bec

[jira] [Commented] (LOG4J2-1162) Memory-mapped file appender creates null-padded files.

[ https://issues.apache.org/jira/browse/LOG4J2-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14962505#comment-14962505 ] Gary Gregory commented on LOG4J2-1162: -- I changed my tear down to: {code:java}

[jira] [Commented] (LOG4J2-1162) Memory-mapped file appender creates null-padded files.

[ https://issues.apache.org/jira/browse/LOG4J2-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14962504#comment-14962504 ] Gary Gregory commented on LOG4J2-1162: -- I fixed some of that in Git master. > Memor

[jira] [Comment Edited] (LOG4J2-879) Minor documentation issues with the 2.1 release

[ https://issues.apache.org/jira/browse/LOG4J2-879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14179590#comment-14179590 ] Remko Popma edited comment on LOG4J2-879 at 10/18/15 4:50 PM: --

[jira] [Updated] (LOG4J2-879) Minor documentation issues with the 2.1 release

[ https://issues.apache.org/jira/browse/LOG4J2-879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-879: --- Fix Version/s: 2.5 > Minor documentation issues with the 2.1 release > ---

[jira] [Resolved] (LOG4J2-764) Migrate PerformanceComparison to log4j-perf

[ https://issues.apache.org/jira/browse/LOG4J2-764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-764. Resolution: Won't Fix I think Ralph likes keeping the PerformanceComparison JUnit test as a quick an

[jira] [Comment Edited] (LOG4J2-1162) Memory-mapped file appender creates null-padded files.

[ https://issues.apache.org/jira/browse/LOG4J2-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14962473#comment-14962473 ] Remko Popma edited comment on LOG4J2-1162 at 10/18/15 4:06 PM:

[jira] [Comment Edited] (LOG4J2-1162) Memory-mapped file appender creates null-padded files.

[ https://issues.apache.org/jira/browse/LOG4J2-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14962473#comment-14962473 ] Remko Popma edited comment on LOG4J2-1162 at 10/18/15 3:59 PM:

[jira] [Commented] (LOG4J2-1162) Memory-mapped file appender creates null-padded files.

[ https://issues.apache.org/jira/browse/LOG4J2-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14962473#comment-14962473 ] Remko Popma commented on LOG4J2-1162: - Note in that output how it seems to start two

[jira] [Resolved] (LOG4J2-573) TimeBasedTriggeringPolicy does not accept %i increment FilePattern

[ https://issues.apache.org/jira/browse/LOG4J2-573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-573. Resolution: Won't Fix Closing as Won't Fix. If this request is still required, please reopen or open

[jira] [Updated] (LOG4J2-536) Project Dependencies page has no content

[ https://issues.apache.org/jira/browse/LOG4J2-536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-536: --- Affects Version/s: 2.4.1 As of 2.4.1, the [Dependencies|http://logging.apache.org/log4j/2.x/dependenc

[jira] [Commented] (LOG4J2-1162) Memory-mapped file appender creates null-padded files.

[ https://issues.apache.org/jira/browse/LOG4J2-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14962451#comment-14962451 ] Gary Gregory commented on LOG4J2-1162: -- Tangent: {noformat} 2015-10-18 08:27:03,563

[jira] [Updated] (LOG4J2-124) Gracefully stopping LogContext using the api interfaces

[ https://issues.apache.org/jira/browse/LOG4J2-124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-124: --- Component/s: API > Gracefully stopping LogContext using the api interfaces > -

[jira] [Updated] (LOG4J2-124) Gracefully stopping LogContext using the api interfaces

[ https://issues.apache.org/jira/browse/LOG4J2-124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-124: --- Fix Version/s: 2.5 > Gracefully stopping LogContext using the api interfaces > ---

[jira] [Commented] (LOG4J2-1162) Memory-mapped file appender creates null-padded files.

[ https://issues.apache.org/jira/browse/LOG4J2-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14962448#comment-14962448 ] Gary Gregory commented on LOG4J2-1162: -- I tried with Git master/2.5-SNAPSHOT and I s

[jira] [Updated] (LOG4J2-1148) log4j.plugin.packages no taken into account

[ https://issues.apache.org/jira/browse/LOG4J2-1148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-1148: Component/s: Configurators > log4j.plugin.packages no taken into account >

[jira] [Updated] (LOG4J2-1162) Memory-mapped file appender creates null-padded files.

[ https://issues.apache.org/jira/browse/LOG4J2-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-1162: Fix Version/s: 2.5 > Memory-mapped file appender creates null-padded files. > -

[jira] [Updated] (LOG4J2-1164) Configuration watch thread causes Tomcat memory leak

[ https://issues.apache.org/jira/browse/LOG4J2-1164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-1164: Fix Version/s: 2.5 > Configuration watch thread causes Tomcat memory leak > ---

[jira] [Updated] (LOG4J2-323) ThreadLocal-leak on tomcat shutdown when using async logging

[ https://issues.apache.org/jira/browse/LOG4J2-323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-323: --- Fix Version/s: 2.5 > ThreadLocal-leak on tomcat shutdown when using async logging > --

[jira] [Updated] (LOG4J2-1159) ThreadLocal leaks in Tomcat8 (org.apache.logging.log4j.core.async.AsyncLogger.Info)

[ https://issues.apache.org/jira/browse/LOG4J2-1159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-1159: Fix Version/s: 2.5 > ThreadLocal leaks in Tomcat8 > (org.apache.logging.log4j.core.async.AsyncLogg

[jira] [Updated] (LOG4J2-1050) Add a Log4jLookup class to help write log files relative to log4j2.xml

[ https://issues.apache.org/jira/browse/LOG4J2-1050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-1050: Fix Version/s: 2.5 > Add a Log4jLookup class to help write log files relative to log4j2.xml > -

[jira] [Commented] (LOG4J2-671) Property using ${date:} is evaluated multiple times across appenders

[ https://issues.apache.org/jira/browse/LOG4J2-671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14962435#comment-14962435 ] Remko Popma commented on LOG4J2-671: Apologies for the very late response. One soluti

[jira] [Commented] (LOG4J2-603) Use Gora as storage abstraction for Log4j 2.X

[ https://issues.apache.org/jira/browse/LOG4J2-603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14962434#comment-14962434 ] Gary Gregory commented on LOG4J2-603: - Wow, this issue is old. [~lewismc]: Do you stil

[jira] [Commented] (LOG4J2-1165) Improve Log4j initialization status messages

[ https://issues.apache.org/jira/browse/LOG4J2-1165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14962431#comment-14962431 ] Gary Gregory commented on LOG4J2-1165: -- I can't recall the Jira #, but I have a list

Fwd: logging-log4j2 git commit: LOG4J2-1166 AbstractConfiguration executor should use a DaemonThreadFactory.

Good one! Gary -- Forwarded message -- From: Date: Sun, Oct 18, 2015 at 5:12 AM Subject: logging-log4j2 git commit: LOG4J2-1166 AbstractConfiguration executor should use a DaemonThreadFactory. To: comm...@logging.apache.org Repository: logging-log4j2 Updated Branches: refs/he

[jira] [Updated] (LOG4J2-671) Property using ${date:} is evaluated multiple times across appenders

[ https://issues.apache.org/jira/browse/LOG4J2-671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-671: --- Description: At the top of my log4j2.xml config I have the following properties: {code} ${date:y

[jira] [Updated] (LOG4J2-905) Ability to disable (date) lookup completely, compatibility issues with other libraries like camel

[ https://issues.apache.org/jira/browse/LOG4J2-905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-905: --- Priority: Critical (was: Major) > Ability to disable (date) lookup completely, compatibility issues w

[jira] [Updated] (LOG4J2-905) Ability to disable (date) lookup completely, compatibility issues with other libraries like camel

[ https://issues.apache.org/jira/browse/LOG4J2-905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-905: --- Component/s: Lookups > Ability to disable (date) lookup completely, compatibility issues with other >

[jira] [Updated] (LOG4J2-915) Wrong timestamp of filename when SizeBasedTriggering and TimeBasedTrigger used simultaniously with RollingFileAppender

[ https://issues.apache.org/jira/browse/LOG4J2-915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-915: --- Fix Version/s: 2.5 > Wrong timestamp of filename when SizeBasedTriggering and TimeBasedTrigger > used

[jira] [Updated] (LOG4J2-850) [Perf] Add performance tests for MemoryMappedFileAppender

[ https://issues.apache.org/jira/browse/LOG4J2-850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-850: --- Fix Version/s: 2.5 > [Perf] Add performance tests for MemoryMappedFileAppender > -

[jira] [Updated] (LOG4J2-849) [Perf] Add performance tests to compare overhead of various logging APIs

[ https://issues.apache.org/jira/browse/LOG4J2-849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-849: --- Fix Version/s: (was: 2.3) 2.5 > [Perf] Add performance tests to compare overhea

[jira] [Updated] (LOG4J2-850) [Perf] Add performance tests for MemoryMappedFileAppender

[ https://issues.apache.org/jira/browse/LOG4J2-850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-850: --- Fix Version/s: (was: 2.3) > [Perf] Add performance tests for MemoryMappedFileAppender > --

[jira] [Updated] (LOG4J2-851) Create RollingMemoryMappedFileAppender

[ https://issues.apache.org/jira/browse/LOG4J2-851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-851: --- Fix Version/s: (was: 2.3) > Create RollingMemoryMappedFileAppender > -

[jira] [Updated] (LOG4J2-846) Combine Log4jWebInitializerImpl into a LoggerContext/LifeCycle wrapper class

[ https://issues.apache.org/jira/browse/LOG4J2-846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-846: --- Fix Version/s: (was: 2.3) > Combine Log4jWebInitializerImpl into a LoggerContext/LifeCycle wrapper

[jira] [Updated] (LOG4J2-857) Add support for the @Order annotation on all @Plugin classes.

[ https://issues.apache.org/jira/browse/LOG4J2-857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-857: --- Fix Version/s: (was: 2.3) > Add support for the @Order annotation on all @Plugin classes. > --

[jira] [Updated] (LOG4J2-836) Binary Logging Appender

[ https://issues.apache.org/jira/browse/LOG4J2-836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-836: --- Fix Version/s: (was: 2.3) 2.5 > Binary Logging Appender > -

[jira] [Updated] (LOG4J2-960) Custom ConfigurationFactory that uses no configuration file will never be used

[ https://issues.apache.org/jira/browse/LOG4J2-960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-960: --- Fix Version/s: 2.5 Version 2.4 added better support for programmatic configuration with LOG4J2-952. Ca

Re: Is there anything besides the Logger name that uniquely identifies a Logger?

The problem we had in tel he past was with the life cycle class IIRC. Gary  Original message From: Matt Sicker Date: 10/18/2015 02:39 (GMT-08:00) To: Log4J Developers List Subject: Re: Is there anything besides the Logger name that uniquely identifies a Logger? Alright,

[jira] [Updated] (LOG4J2-1011) Dependencies for layouts should be documentated

[ https://issues.apache.org/jira/browse/LOG4J2-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-1011: Affects Version/s: 2.3 2.4 2.4.1 Priority

[jira] [Resolved] (LOG4J2-1109) Archiving doesn't work

[ https://issues.apache.org/jira/browse/LOG4J2-1109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-1109. - Resolution: Fixed Fix Version/s: 2.4.1 Fixed in 2.4.1 (see also LOG4J2-1135, sorry I did n

[jira] [Commented] (LOG4J2-1112) Using both OnStartupTriggeringPolicy and TimeBasedTriggeringPolicy create log file with wrong date

[ https://issues.apache.org/jira/browse/LOG4J2-1112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14962408#comment-14962408 ] Remko Popma commented on LOG4J2-1112: - Can you please provide your log4j2.xml configu

[jira] [Updated] (LOG4J2-1112) Using both OnStartupTriggeringPolicy and TimeBasedTriggeringPolicy create log file with wrong date

[ https://issues.apache.org/jira/browse/LOG4J2-1112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-1112: Description: We found this bug while we were updating our logging library (from log4j 1.x to 2.3)

[jira] [Updated] (LOG4J2-1080) Drop events when the RingBuffer is full

[ https://issues.apache.org/jira/browse/LOG4J2-1080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-1080: Fix Version/s: 2.5 > Drop events when the RingBuffer is full >

[jira] [Commented] (LOG4J2-929) Roll over of log files

[ https://issues.apache.org/jira/browse/LOG4J2-929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14962404#comment-14962404 ] Remko Popma commented on LOG4J2-929: In addition to Ralph's comments, you may want to

[jira] [Resolved] (LOG4J2-648) Support a programmatic DSL for configuration.

[ https://issues.apache.org/jira/browse/LOG4J2-648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-648. Resolution: Fixed Fix Version/s: 2.4 Implemented in LOG4J2-952. > Support a programmatic DSL

[jira] [Comment Edited] (LOG4J2-607) log4j2 json files do not support property substitutions

[ https://issues.apache.org/jira/browse/LOG4J2-607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13973243#comment-13973243 ] Remko Popma edited comment on LOG4J2-607 at 10/18/15 2:11 PM: --

[jira] [Comment Edited] (LOG4J2-607) log4j2 json files do not support property substitutions

[ https://issues.apache.org/jira/browse/LOG4J2-607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13973501#comment-13973501 ] Remko Popma edited comment on LOG4J2-607 at 10/18/15 2:11 PM: --

[jira] [Comment Edited] (LOG4J2-607) log4j2 json files do not support property substitutions

[ https://issues.apache.org/jira/browse/LOG4J2-607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14009081#comment-14009081 ] Remko Popma edited comment on LOG4J2-607 at 10/18/15 2:09 PM: --

[jira] [Updated] (LOG4J2-603) Use Gora as storage abstraction for Log4j 2.X

[ https://issues.apache.org/jira/browse/LOG4J2-603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-603: --- Fix Version/s: (was: 2.3) > Use Gora as storage abstraction for Log4j 2.X > --

[jira] [Updated] (LOG4J2-594) Log4j configuration file is not loading at time of Websphere 8.5 app server start when config file not in classpath

[ https://issues.apache.org/jira/browse/LOG4J2-594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-594: --- Summary: Log4j configuration file is not loading at time of Websphere 8.5 app server start when config

[jira] [Commented] (LOG4J2-565) Log4j2 loading time on single-board (embedded) computers

[ https://issues.apache.org/jira/browse/LOG4J2-565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14962390#comment-14962390 ] Remko Popma commented on LOG4J2-565: Is this still a problem? Various improvements hav

[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=14962389#comment-14962389 ] Remko Popma commented on LOG4J2-1116: - As Ralph said, can you please provide your log

[jira] [Updated] (LOG4J2-400) [OSGi] Provide Appender-Bundles

[ https://issues.apache.org/jira/browse/LOG4J2-400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-400: --- Fix Version/s: (was: 2.3) > [OSGi] Provide Appender-Bundles > --- > >

[jira] [Updated] (LOG4J2-1013) Log4j2 Main Arguments Lookup by name doesn't work

[ https://issues.apache.org/jira/browse/LOG4J2-1013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-1013: Fix Version/s: 2.5 Description: Accessing Main Arguments by using index based look up works :

[jira] [Resolved] (LOG4J2-799) Log4j 2 throws ArrayIndexOutOfBoundsException

[ https://issues.apache.org/jira/browse/LOG4J2-799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-799. Resolution: Fixed Fix Version/s: 2.1 Closing as fixed. Please re-open if this is still an iss

[jira] [Commented] (LOG4J2-875) Log file getting overwritten on Microsoft Windows Maschines

[ https://issues.apache.org/jira/browse/LOG4J2-875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14962383#comment-14962383 ] Remko Popma commented on LOG4J2-875: Could you try again with the latest version (2.4.

[jira] [Updated] (LOG4J2-875) Log file getting overwritten on Microsoft Windows Maschines

[ https://issues.apache.org/jira/browse/LOG4J2-875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-875: --- Description: A problem with slashes? does not work since version 2.0, but in rc1: filePattern = "

[jira] [Comment Edited] (LOG4J2-875) Log file getting overwritten on Microsoft Windows Maschines

[ https://issues.apache.org/jira/browse/LOG4J2-875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14174769#comment-14174769 ] Remko Popma edited comment on LOG4J2-875 at 10/18/15 1:39 PM: --

[jira] [Comment Edited] (LOG4J2-1162) Memory-mapped file appender creates null-padded files.

[ https://issues.apache.org/jira/browse/LOG4J2-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14962329#comment-14962329 ] Remko Popma edited comment on LOG4J2-1162 at 10/18/15 1:30 PM:

[jira] [Comment Edited] (LOG4J2-1162) Memory-mapped file appender creates null-padded files.

[ https://issues.apache.org/jira/browse/LOG4J2-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14962329#comment-14962329 ] Remko Popma edited comment on LOG4J2-1162 at 10/18/15 1:28 PM:

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

See - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org

[jira] [Updated] (LOG4J2-1165) Improve Log4j initialization status messages

[ https://issues.apache.org/jira/browse/LOG4J2-1165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-1165: Summary: Improve Log4j initialization status messages (was: Reduce verbosity of Log4j initializati

[jira] [Commented] (LOG4J2-1162) Memory-mapped file appender creates null-padded files.

[ https://issues.apache.org/jira/browse/LOG4J2-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14962329#comment-14962329 ] Remko Popma commented on LOG4J2-1162: - I think this was caused by LOG4J2-1166: since

[jira] [Updated] (LOG4J2-1166) Applications using Log4j-2.5 with monitorInterval never shut down

[ https://issues.apache.org/jira/browse/LOG4J2-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-1166: Description: The new WatchManager introduced in 2.5 uses a ScheduledThreadPoolExecutor so it can r

[jira] [Resolved] (LOG4J2-1166) AbstractConfiguration executor should use a DaemonThreadFactory

[ https://issues.apache.org/jira/browse/LOG4J2-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-1166. - Resolution: Fixed Fixed in master in Commit: d2747d6b. > AbstractConfiguration executor should u

[jira] [Comment Edited] (LOG4J2-1165) Reduce verbosity of Log4j initialization status messages

[ https://issues.apache.org/jira/browse/LOG4J2-1165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14962280#comment-14962280 ] Remko Popma edited comment on LOG4J2-1165 at 10/18/15 12:14 PM: ---

[jira] [Created] (LOG4J2-1166) AbstractConfiguration executor should use a DaemonThreadFactory

Remko Popma created LOG4J2-1166: --- Summary: AbstractConfiguration executor should use a DaemonThreadFactory Key: LOG4J2-1166 URL: https://issues.apache.org/jira/browse/LOG4J2-1166 Project: Log4j 2

[jira] [Commented] (LOG4J2-1130) CsvLogEventLayout NanoTime timestamp is always zero.

[ https://issues.apache.org/jira/browse/LOG4J2-1130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14962323#comment-14962323 ] Remko Popma commented on LOG4J2-1130: - I did some research for LOG4J2-1074 a while ba

Jenkins build became unstable: Log4j 2.x #1468

See - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org

[jira] [Resolved] (LOG4J2-1165) Reduce verbosity of Log4j initialization status messages

[ https://issues.apache.org/jira/browse/LOG4J2-1165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-1165. - Resolution: Fixed Initial improvements added to master in commit: 6b457022. > Reduce verbosity o

[jira] [Commented] (LOG4J2-1165) Reduce verbosity of Log4j initialization status messages

[ https://issues.apache.org/jira/browse/LOG4J2-1165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14962269#comment-14962269 ] Remko Popma commented on LOG4J2-1165: - Okay, I guess it is hard to see what changed.

Re: Is there anything besides the Logger name that uniquely identifies a Logger?

Alright, thanks for the heads up. On 18 October 2015 at 04:24, Remko Popma wrote: > Hi Matt, sorry, but please don't add equals/hashCode implementation to > AbstractLogger. Concrete subclasses are okay of course. > We had a few issues with this with another abstract Log4j class (can't > find the

Re: Is there anything besides the Logger name that uniquely identifies a Logger?

Hi Matt, sorry, but please don't add equals/hashCode implementation to AbstractLogger. Concrete subclasses are okay of course. We had a few issues with this with another abstract Log4j class (can't find the Jira ticket now). On Sun, Oct 18, 2015 at 2:00 PM, Matt Sicker wrote: > Alright, I've got

[jira] [Commented] (LOG4J2-1165) Reduce verbosity of Log4j initialization status messages

[ https://issues.apache.org/jira/browse/LOG4J2-1165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14962236#comment-14962236 ] Gary Gregory commented on LOG4J2-1165: -- My preference would be to avoid loosing any

[jira] [Created] (LOG4J2-1165) Reduce verbosity of Log4j initialization status messages

Remko Popma created LOG4J2-1165: --- Summary: Reduce verbosity of Log4j initialization status messages Key: LOG4J2-1165 URL: https://issues.apache.org/jira/browse/LOG4J2-1165 Project: Log4j 2 Issu

  1   2   >