[jira] [Commented] (LOG4J2-425) Permgen leak in AsyncLoggerConfigHelper

[ https://issues.apache.org/jira/browse/LOG4J2-425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13794700#comment-13794700 ] Remko Popma commented on LOG4J2-425: To be exact, this issue is not exactly a

[jira] [Resolved] (LOG4J2-425) Permgen leak in AsyncLoggerConfigHelper

[ https://issues.apache.org/jira/browse/LOG4J2-425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-425. Resolution: Duplicate Permgen leak in AsyncLoggerConfigHelper

[jira] [Commented] (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:comment-tabpanelfocusedCommentId=13794704#comment-13794704 ] Remko Popma commented on LOG4J2-323: This issue is similar to LOG4J2-425. Both

[jira] [Commented] (LOG4J2-406) JMX MBeans are not being unregistered when a tomcat web application that uses log4j is undeployed, leading to a permgen memory leak.

[ https://issues.apache.org/jira/browse/LOG4J2-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13794708#comment-13794708 ] Remko Popma commented on LOG4J2-406: Linked to LOG4J2-323: some more

[jira] [Commented] (LOG4J2-426) Permgen leak: Log4j2 does not unregister MBeans on shutdown

[ https://issues.apache.org/jira/browse/LOG4J2-426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13794714#comment-13794714 ] Remko Popma commented on LOG4J2-426: Sergey (I almost missed this), you mention as far

[jira] [Comment Edited] (LOG4J2-406) JMX MBeans are not being unregistered when a tomcat web application that uses log4j is undeployed, leading to a permgen memory leak.

[ https://issues.apache.org/jira/browse/LOG4J2-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13794708#comment-13794708 ] Remko Popma edited comment on LOG4J2-406 at 10/15/13 12:43 AM:

[jira] [Comment Edited] (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:comment-tabpanelfocusedCommentId=13794704#comment-13794704 ] Remko Popma edited comment on LOG4J2-323 at 10/15/13 12:47 AM:

[jira] [Commented] (LOG4J2-426) Permgen leak: Log4j2 does not unregister MBeans on shutdown

[ https://issues.apache.org/jira/browse/LOG4J2-426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13794921#comment-13794921 ] Remko Popma commented on LOG4J2-426: My assumption was that the logging context name

[jira] [Reopened] (LOG4J2-425) Permgen leak in AsyncLoggerConfigHelper

[ https://issues.apache.org/jira/browse/LOG4J2-425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma reopened LOG4J2-425: Assignee: Remko Popma Permgen leak in AsyncLoggerConfigHelper

[jira] [Resolved] (LOG4J2-425) Permgen leak in AsyncLoggerConfigHelper

[ https://issues.apache.org/jira/browse/LOG4J2-425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-425. Resolution: Fixed Fix Version/s: 2.0-rc1 Eliminated ThreadLocal from

[jira] [Resolved] (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 resolved LOG4J2-323. Resolution: Fixed Fix Version/s: 2.0-rc1 Resolved memory leak by releasing reference to

[jira] [Resolved] (LOG4J2-354) log4j2 + FastFileAppender + Tomcat logrotate problem

[ https://issues.apache.org/jira/browse/LOG4J2-354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-354. Resolution: Won't Fix Resolving this issue as Won't Fix. The issue is that the

[jira] [Updated] (LOG4J2-423) Provide a means to inspect queue usage for Async Loggers and Async Appender

[ https://issues.apache.org/jira/browse/LOG4J2-423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-423: --- Attachment: jconsole2.png jconsole1.png Provide a means to inspect queue usage for

[jira] [Resolved] (LOG4J2-423) Provide a means to inspect queue usage for Async Loggers and Async Appender

[ https://issues.apache.org/jira/browse/LOG4J2-423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-423. Resolution: Fixed * Exposed various read-only attributes on AsyncAppender * Added MBean

[jira] [Updated] (LOG4J2-423) Provide a means to inspect queue usage for Async Loggers and Async Appender

[ https://issues.apache.org/jira/browse/LOG4J2-423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-423: --- Attachment: (was: jconsole2.png) Provide a means to inspect queue usage for Async Loggers and

[jira] [Updated] (LOG4J2-423) Provide a means to inspect queue usage for Async Loggers and Async Appender

[ https://issues.apache.org/jira/browse/LOG4J2-423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-423: --- Attachment: (was: jconsole1.png) Provide a means to inspect queue usage for Async Loggers and

[jira] [Updated] (LOG4J2-423) Provide a means to inspect queue usage for Async Loggers and Async Appender

[ https://issues.apache.org/jira/browse/LOG4J2-423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-423: --- Attachment: jconsole2.png jconsole1.png Provide a means to inspect queue usage for

[jira] [Commented] (LOG4J2-429) Class name and file number not filled with Async appender

[ https://issues.apache.org/jira/browse/LOG4J2-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13796657#comment-13796657 ] Remko Popma commented on LOG4J2-429: Yes, this is normal. With AsyncAppender (and

[jira] [Commented] (LOG4J2-416) ConcurrentModificationException when logging maps that are being worked on

[ https://issues.apache.org/jira/browse/LOG4J2-416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13796673#comment-13796673 ] Remko Popma commented on LOG4J2-416: Dimitry, glad to hear that. Regarding locking,

[jira] [Updated] (LOG4J2-429) Class name and file number not filled with Async appender

[ https://issues.apache.org/jira/browse/LOG4J2-429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-429: --- Description: Hi everyone, I found an annoying issue with async appender, with this configuration:

[jira] [Closed] (LOG4J2-423) Provide a means to inspect queue usage for Async Loggers and Async Appender

[ https://issues.apache.org/jira/browse/LOG4J2-423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma closed LOG4J2-423. -- Provide a means to inspect queue usage for Async Loggers and Async Appender

[jira] [Resolved] (LOG4J2-416) ConcurrentModificationException when logging maps that are being worked on

[ https://issues.apache.org/jira/browse/LOG4J2-416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-416. Resolution: Not A Problem Assignee: Remko Popma Dimitry, I'm resolving this issue as Not A

[jira] [Commented] (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:comment-tabpanelfocusedCommentId=13796717#comment-13796717 ] Remko Popma commented on LOG4J2-323: Hi Hudson, so before you were seeing the Tomcat

[jira] [Commented] (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:comment-tabpanelfocusedCommentId=13796745#comment-13796745 ] Remko Popma commented on LOG4J2-323: Oh. :-) Sorry Francesco. And thanks for the

[jira] [Created] (LOG4J2-431) Create MemoryMappedFileAppender

Remko Popma created LOG4J2-431: -- Summary: Create MemoryMappedFileAppender Key: LOG4J2-431 URL: https://issues.apache.org/jira/browse/LOG4J2-431 Project: Log4j 2 Issue Type: New Feature

[jira] [Updated] (LOG4J2-437) Log4J2 Performs poorly with 500 concurrent users with Jboss 5.1.GA and JDK 6

[ https://issues.apache.org/jira/browse/LOG4J2-437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-437: --- Description: Environment Details JDK: 1.6.0_18 APP Server:

[jira] [Updated] (LOG4J2-437) Log4J2 Performs poorly with 500 concurrent users with Jboss 5.1.GA and JDK 6

[ https://issues.apache.org/jira/browse/LOG4J2-437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-437: --- Description: Environment Details JDK: 1.6.0_18 APP Server:

[jira] [Updated] (LOG4J2-437) Log4J2 Performs poorly with 500 concurrent users with Jboss 5.1.GA and JDK 6

[ https://issues.apache.org/jira/browse/LOG4J2-437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-437: --- Description: Environment Details JDK: 1.6.0_18 APP Server:

[jira] [Commented] (LOG4J2-437) Log4J2 Performs poorly with 500 concurrent users with Jboss 5.1.GA and JDK 6

[ https://issues.apache.org/jira/browse/LOG4J2-437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13806032#comment-13806032 ] Remko Popma commented on LOG4J2-437: Giri, in addition to Ralph's questions, can I

[jira] [Commented] (LOG4J2-437) Log4J2 Performs poorly with 500 concurrent users with Jboss 5.1.GA and JDK 6

[ https://issues.apache.org/jira/browse/LOG4J2-437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13806039#comment-13806039 ] Remko Popma commented on LOG4J2-437: Actually, looking at the stack traces, I don't

[jira] [Commented] (LOG4J2-437) Log4J2 Performs poorly with 500 concurrent users with Jboss 5.1.GA and JDK 6

[ https://issues.apache.org/jira/browse/LOG4J2-437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13806048#comment-13806048 ] Remko Popma commented on LOG4J2-437: I had a quick look at the CXF documentation but I

[jira] [Commented] (LOG4J2-437) Log4J2 Performs poorly with 500 concurrent users with Jboss 5.1.GA and JDK 6

[ https://issues.apache.org/jira/browse/LOG4J2-437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13806049#comment-13806049 ] Remko Popma commented on LOG4J2-437: Also, in your system properties you have start

[jira] [Commented] (LOG4J2-437) Log4J2 Performs poorly with 500 concurrent users with Jboss 5.1.GA and JDK 6

[ https://issues.apache.org/jira/browse/LOG4J2-437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13806090#comment-13806090 ] Remko Popma commented on LOG4J2-437: If your application uses the SLF4J logging API,

[jira] [Commented] (LOG4J2-428) Integration of GELF Appender

[ https://issues.apache.org/jira/browse/LOG4J2-428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13812366#comment-13812366 ] Remko Popma commented on LOG4J2-428: Hi Mark, I've taken a (brief) look at the patch

[jira] [Comment Edited] (LOG4J2-437) Log4J2 Performs poorly with 500 concurrent users with Jboss 5.1.GA and JDK 6

[ https://issues.apache.org/jira/browse/LOG4J2-437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13812369#comment-13812369 ] Remko Popma edited comment on LOG4J2-437 at 11/3/13 1:42 PM: -

[jira] [Commented] (LOG4J2-437) Log4J2 Performs poorly with 500 concurrent users with Jboss 5.1.GA and JDK 6

[ https://issues.apache.org/jira/browse/LOG4J2-437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13812369#comment-13812369 ] Remko Popma commented on LOG4J2-437: Giri, how did thing work out? Log4J2 Performs

[jira] [Commented] (LOG4J2-436) RollingRandomAccessFile pattern layout not work for mathod and line no

[ https://issues.apache.org/jira/browse/LOG4J2-436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13812376#comment-13812376 ] Remko Popma commented on LOG4J2-436: Kent, You need to add {{includeLocation=true}} to

[jira] [Resolved] (LOG4J2-429) Class name and file number not filled with Async appender

[ https://issues.apache.org/jira/browse/LOG4J2-429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-429. Resolution: Not A Problem Assignee: Remko Popma Hemri, I assume that you were able to get

[jira] [Commented] (LOG4J2-434) exception related data put into one log file and rest of them put into another log file

[ https://issues.apache.org/jira/browse/LOG4J2-434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13812379#comment-13812379 ] Remko Popma commented on LOG4J2-434: Venkata, is this still a problem? If not, can you

[jira] [Resolved] (LOG4J2-414) Async all loggers cause OutOfMemory error in log4j-2.0-beta9

[ https://issues.apache.org/jira/browse/LOG4J2-414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-414. Resolution: Unresolved Yiru, thanks for your response. I understand that your company does not

[jira] [Closed] (LOG4J2-414) Async all loggers cause OutOfMemory error in log4j-2.0-beta9

[ https://issues.apache.org/jira/browse/LOG4J2-414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma closed LOG4J2-414. -- Async all loggers cause OutOfMemory error in log4j-2.0-beta9

[jira] [Updated] (LOG4J2-392) Intermittent errors with appenders

[ https://issues.apache.org/jira/browse/LOG4J2-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-392: --- Affects Version/s: 2.0-beta9 Intermittent errors with appenders --

[jira] [Commented] (LOG4J2-392) Intermittent errors with appenders

[ https://issues.apache.org/jira/browse/LOG4J2-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13812390#comment-13812390 ] Remko Popma commented on LOG4J2-392: Andre, Thanks for looking into this. I added

[jira] [Commented] (LOG4J2-440) exception on shutdown tomcat in Mac OSX

[ https://issues.apache.org/jira/browse/LOG4J2-440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13813857#comment-13813857 ] Remko Popma commented on LOG4J2-440: Do you have a stack trace? exception on

[jira] [Updated] (LOG4J2-441) logger level configuration does not work correct

[ https://issues.apache.org/jira/browse/LOG4J2-441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-441: --- Description: Configuring the loglevel in the logger does not work in combination with configuring

[jira] [Commented] (LOG4J2-441) logger level configuration does not work correct

[ https://issues.apache.org/jira/browse/LOG4J2-441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13815430#comment-13815430 ] Remko Popma commented on LOG4J2-441: In the configuration above, there is one logger

[jira] [Resolved] (LOG4J2-437) Log4J2 Performs poorly with 500 concurrent users with Jboss 5.1.GA and JDK 6

[ https://issues.apache.org/jira/browse/LOG4J2-437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-437. Resolution: Fixed Giri, Thanks for your feedback. Based on your comment, I will mark this issue as

[jira] [Updated] (LOG4J2-461) ERROR StatusLogger Unable to locate a logging implementation, using SimpleLogger

[ https://issues.apache.org/jira/browse/LOG4J2-461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-461: --- Description: ERROR StatusLogger Unable to locate a logging implementation, using SimpleLogger Code:

[jira] [Commented] (LOG4J2-461) ERROR StatusLogger Unable to locate a logging implementation, using SimpleLogger

[ https://issues.apache.org/jira/browse/LOG4J2-461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13840011#comment-13840011 ] Remko Popma commented on LOG4J2-461: Gaurav, the only way this error can occur is if

[jira] [Commented] (LOG4J2-467) Thread name caching in async logger incompatible with use of Thread.setName()

[ https://issues.apache.org/jira/browse/LOG4J2-467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13845962#comment-13845962 ] Remko Popma commented on LOG4J2-467: Anthony, thanks for your feedback. Caching the

[jira] [Commented] (LOG4J2-465) ThresholdFilter throws NPE

[ https://issues.apache.org/jira/browse/LOG4J2-465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13845976#comment-13845976 ] Remko Popma commented on LOG4J2-465: Thanks for reporting this! Can you also post your

[jira] [Commented] (LOG4J2-392) Intermittent errors with appenders

[ https://issues.apache.org/jira/browse/LOG4J2-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13845979#comment-13845979 ] Remko Popma commented on LOG4J2-392: Thanks Andre, Sorry for the slow response time...

[jira] [Updated] (LOG4J2-460) java.lang.ClassCastException: org.apache.logging.log4j.simple.SimpleLoggerContext cannot be cast to org.apache.logging.log4j.core.LoggerContext

[ https://issues.apache.org/jira/browse/LOG4J2-460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-460: --- Description: I'm trying to integrate Log4j2 in Android but getting the following error message:

[jira] [Commented] (LOG4J2-460) java.lang.ClassCastException: org.apache.logging.log4j.simple.SimpleLoggerContext cannot be cast to org.apache.logging.log4j.core.LoggerContext

[ https://issues.apache.org/jira/browse/LOG4J2-460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13845987#comment-13845987 ] Remko Popma commented on LOG4J2-460: This looks like a classpath issue. If both the

[jira] [Commented] (LOG4J2-461) ERROR StatusLogger Unable to locate a logging implementation, using SimpleLogger

[ https://issues.apache.org/jira/browse/LOG4J2-461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13845989#comment-13845989 ] Remko Popma commented on LOG4J2-461: (I'm copying my last comment from LOG4J2-460

[jira] [Commented] (LOG4J2-462) LevelPatternConverter.format may throw NPE

[ https://issues.apache.org/jira/browse/LOG4J2-462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13845993#comment-13845993 ] Remko Popma commented on LOG4J2-462: Thanks for reporting this. I'm very surprised

[jira] [Updated] (LOG4J2-458) Filters configuration

[ https://issues.apache.org/jira/browse/LOG4J2-458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-458: --- Description: Hi, Here is my log line: 2013-11-29 15:34:23,345: INFO : [main] : [myModule] :

[jira] [Commented] (LOG4J2-458) Filters configuration

[ https://issues.apache.org/jira/browse/LOG4J2-458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13845999#comment-13845999 ] Remko Popma commented on LOG4J2-458: Eric, Sorry for the late reply. By default, log

[jira] [Updated] (LOG4J2-454) TimeBasedTriggeringPolicy should use event time millis

[ https://issues.apache.org/jira/browse/LOG4J2-454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-454: --- Description: In the TimeBasedTriggeringPolicy.java, it's using system current timestamp to compare

[jira] [Commented] (LOG4J2-467) Thread name caching in async logger incompatible with use of Thread.setName()

[ https://issues.apache.org/jira/browse/LOG4J2-467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13846007#comment-13846007 ] Remko Popma commented on LOG4J2-467: Gary, I don't remember the exact numbers but I

[jira] [Commented] (LOG4J2-467) Thread name caching in async logger incompatible with use of Thread.setName()

[ https://issues.apache.org/jira/browse/LOG4J2-467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13846032#comment-13846032 ] Remko Popma commented on LOG4J2-467: Anthony, understood, thanks! I've given it some

[jira] [Assigned] (LOG4J2-471) toString methods that perform logging can deadlock AsyncLogger

[ https://issues.apache.org/jira/browse/LOG4J2-471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma reassigned LOG4J2-471: -- Assignee: Remko Popma toString methods that perform logging can deadlock AsyncLogger

[jira] [Commented] (LOG4J2-471) toString methods that perform logging can deadlock AsyncLogger

[ https://issues.apache.org/jira/browse/LOG4J2-471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13855123#comment-13855123 ] Remko Popma commented on LOG4J2-471: Anthony, from the stacktrace, I agree with your

[jira] [Assigned] (LOG4J2-472) BaseConfiguration class does not properly implement Configuration interface

[ https://issues.apache.org/jira/browse/LOG4J2-472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma reassigned LOG4J2-472: -- Assignee: Remko Popma BaseConfiguration class does not properly implement Configuration

[jira] [Resolved] (LOG4J2-472) BaseConfiguration class does not properly implement Configuration interface

[ https://issues.apache.org/jira/browse/LOG4J2-472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-472. Resolution: Fixed Fixed in revision 1552971. Please verify and close. BaseConfiguration class

[jira] [Assigned] (LOG4J2-454) TimeBasedTriggeringPolicy should use event time millis

[ https://issues.apache.org/jira/browse/LOG4J2-454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma reassigned LOG4J2-454: -- Assignee: Remko Popma TimeBasedTriggeringPolicy should use event time millis

[jira] [Resolved] (LOG4J2-454) TimeBasedTriggeringPolicy should use event time millis

[ https://issues.apache.org/jira/browse/LOG4J2-454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-454. Resolution: Fixed Fixed in revision 1552975. Please verify and close. TimeBasedTriggeringPolicy

[jira] [Commented] (LOG4J2-471) toString methods that perform logging can deadlock AsyncLogger

[ https://issues.apache.org/jira/browse/LOG4J2-471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13855153#comment-13855153 ] Remko Popma commented on LOG4J2-471: Anthony, I've taken a quick look at the patch you

[jira] [Commented] (LOG4J2-455) RingBufferLogEvent should use Messsage timestamp first

[ https://issues.apache.org/jira/browse/LOG4J2-455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13855176#comment-13855176 ] Remko Popma commented on LOG4J2-455: That is an option but would entail an API change:

[jira] [Assigned] (LOG4J2-477) NPE in ClassLoaderContextSelector

[ https://issues.apache.org/jira/browse/LOG4J2-477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma reassigned LOG4J2-477: -- Assignee: Remko Popma NPE in ClassLoaderContextSelector -

[jira] [Resolved] (LOG4J2-477) NPE in ClassLoaderContextSelector

[ https://issues.apache.org/jira/browse/LOG4J2-477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-477. Resolution: Fixed Fixed in revision 1552996. Please verify and close. NPE in

[jira] [Commented] (LOG4J2-468) Dynamically (programmatically) add logger in Log4j2

[ https://issues.apache.org/jira/browse/LOG4J2-468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13855183#comment-13855183 ] Remko Popma commented on LOG4J2-468: Ralph, would it be an idea to add this code

[jira] [Commented] (LOG4J2-431) Create MemoryMappedFileAppender

[ https://issues.apache.org/jira/browse/LOG4J2-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13855647#comment-13855647 ] Remko Popma commented on LOG4J2-431: Claude, thank you for your contribution! I've

[jira] [Resolved] (LOG4J2-455) RingBufferLogEvent should use Messsage timestamp first

[ https://issues.apache.org/jira/browse/LOG4J2-455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-455. Resolution: Fixed Assignee: Remko Popma Fixed in revision 1553122. Please verify and close.

[jira] [Resolved] (LOG4J2-477) NPE in ClassLoaderContextSelector

[ https://issues.apache.org/jira/browse/LOG4J2-477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-477. Resolution: Fixed Tal, thanks for checking! I've made the following change: {code} private

[jira] [Comment Edited] (LOG4J2-477) NPE in ClassLoaderContextSelector

[ https://issues.apache.org/jira/browse/LOG4J2-477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13856265#comment-13856265 ] Remko Popma edited comment on LOG4J2-477 at 12/24/13 10:44 AM:

[jira] [Commented] (LOG4J2-479) Use of InheritableThreadLocal in Map ThreadContext is dangerous and unhelpful

[ https://issues.apache.org/jira/browse/LOG4J2-479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13857920#comment-13857920 ] Remko Popma commented on LOG4J2-479: Could you elaborate on what problems you think

[jira] [Commented] (LOG4J2-481) Stream-Interface for Loggers

[ https://issues.apache.org/jira/browse/LOG4J2-481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13859782#comment-13859782 ] Remko Popma commented on LOG4J2-481: Hi Joe, Would you like to contribute a patch?

[jira] [Commented] (LOG4J2-361) Allow plugins to have hyphens in configuration files to be automatically aliased to non-hyphenated versions.

[ https://issues.apache.org/jira/browse/LOG4J2-361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13860128#comment-13860128 ] Remko Popma commented on LOG4J2-361: If I remember correctly the consensus was to only

[jira] [Commented] (LOG4J2-479) Use of InheritableThreadLocal in Map ThreadContext is dangerous and unhelpful

[ https://issues.apache.org/jira/browse/LOG4J2-479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13861104#comment-13861104 ] Remko Popma commented on LOG4J2-479: Can you confirm the desired behaviour? In the

[jira] [Updated] (LOG4J2-467) Thread name caching in async logger incompatible with use of Thread.setName()

[ https://issues.apache.org/jira/browse/LOG4J2-467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-467: --- Attachment: PerfTestDriver.java Gary, I've tested the performance difference like you asked. I used

[jira] [Comment Edited] (LOG4J2-467) Thread name caching in async logger incompatible with use of Thread.setName()

[ https://issues.apache.org/jira/browse/LOG4J2-467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13861384#comment-13861384 ] Remko Popma edited comment on LOG4J2-467 at 1/3/14 9:52 AM:

[jira] [Resolved] (LOG4J2-467) Thread name caching in async logger incompatible with use of Thread.setName()

[ https://issues.apache.org/jira/browse/LOG4J2-467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-467. Resolution: Fixed Fix Version/s: 2.0-rc1 Assignee: Remko Popma Anthony, I've added

[jira] [Commented] (LOG4J2-479) Use of InheritableThreadLocal in Map ThreadContext is dangerous and unhelpful

[ https://issues.apache.org/jira/browse/LOG4J2-479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13861501#comment-13861501 ] Remko Popma commented on LOG4J2-479: Hmm... I'm not sure how to proceed here. On the

[jira] [Resolved] (LOG4J2-482) The attribute of Route to refer to an appender is ref not AppenderRef

[ https://issues.apache.org/jira/browse/LOG4J2-482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-482. Resolution: Fixed Fix Version/s: 2.0-rc1 Thanks for pointing this out. I've changed the

[jira] [Updated] (LOG4J2-471) toString methods that perform logging can deadlock AsyncLogger

[ https://issues.apache.org/jira/browse/LOG4J2-471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-471: --- Fix Version/s: 2.0 toString methods that perform logging can deadlock AsyncLogger

[jira] [Commented] (LOG4J2-462) LevelPatternConverter.format may throw NPE

[ https://issues.apache.org/jira/browse/LOG4J2-462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13861588#comment-13861588 ] Remko Popma commented on LOG4J2-462: Daisuke, both this issue and LOG4J2-465 occur

[jira] [Commented] (LOG4J2-467) Thread name caching in async logger incompatible with use of Thread.setName()

[ https://issues.apache.org/jira/browse/LOG4J2-467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13862126#comment-13862126 ] Remko Popma commented on LOG4J2-467: Gary, after rebooting my windows laptop I'm

[jira] [Reopened] (LOG4J2-482) The attribute of Route to refer to an appender is ref not AppenderRef

[ https://issues.apache.org/jira/browse/LOG4J2-482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma reopened LOG4J2-482: Assignee: Remko Popma (Reopening issue) Now that we are talking about coming out of beta on the

[jira] [Resolved] (LOG4J2-482) The attribute of Route to refer to an appender is ref not AppenderRef

[ https://issues.apache.org/jira/browse/LOG4J2-482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-482. Resolution: Fixed Hmm... Perhaps I was too enthusiastic there... After taking another good look,

[jira] [Comment Edited] (LOG4J2-482) The attribute of Route to refer to an appender is ref not AppenderRef

[ https://issues.apache.org/jira/browse/LOG4J2-482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13862192#comment-13862192 ] Remko Popma edited comment on LOG4J2-482 at 1/4/14 3:46 AM:

[jira] [Commented] (LOG4J2-467) Thread name caching in async logger incompatible with use of Thread.setName()

[ https://issues.apache.org/jira/browse/LOG4J2-467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13862194#comment-13862194 ] Remko Popma commented on LOG4J2-467: Hi Scott! Good question, not sure. Disk access

[jira] [Commented] (LOG4J2-467) Thread name caching in async logger incompatible with use of Thread.setName()

[ https://issues.apache.org/jira/browse/LOG4J2-467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13862203#comment-13862203 ] Remko Popma commented on LOG4J2-467: (away from PC) You shouldn't need slf4j to run

[jira] [Reopened] (LOG4J2-467) Thread name caching in async logger incompatible with use of Thread.setName()

[ https://issues.apache.org/jira/browse/LOG4J2-467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma reopened LOG4J2-467: Reopening so I can attach files and edit old comments. Thread name caching in async logger

[jira] [Updated] (LOG4J2-467) Thread name caching in async logger incompatible with use of Thread.setName()

[ https://issues.apache.org/jira/browse/LOG4J2-467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-467: --- Attachment: PerfTestDriver.java Scott, If you see Logback... you are not using the PerfTestDriver

[jira] [Commented] (LOG4J2-467) Thread name caching in async logger incompatible with use of Thread.setName()

[ https://issues.apache.org/jira/browse/LOG4J2-467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13862236#comment-13862236 ] Remko Popma commented on LOG4J2-467: Performance test result update: The numbers I

[jira] [Comment Edited] (LOG4J2-467) Thread name caching in async logger incompatible with use of Thread.setName()

[ https://issues.apache.org/jira/browse/LOG4J2-467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13862126#comment-13862126 ] Remko Popma edited comment on LOG4J2-467 at 1/4/14 7:50 AM:

[jira] [Commented] (LOG4J2-471) toString methods that perform logging can deadlock AsyncLogger

[ https://issues.apache.org/jira/browse/LOG4J2-471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13862250#comment-13862250 ] Remko Popma commented on LOG4J2-471: Anthony, thanks again for the patch! I've applied

[jira] [Resolved] (LOG4J2-471) toString methods that perform logging can deadlock AsyncLogger

[ https://issues.apache.org/jira/browse/LOG4J2-471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-471. Resolution: Fixed Fix Version/s: 2.0-rc1 toString methods that perform logging can

[jira] [Assigned] (LOG4J2-462) LevelPatternConverter.format may throw NPE

[ https://issues.apache.org/jira/browse/LOG4J2-462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma reassigned LOG4J2-462: -- Assignee: Remko Popma LevelPatternConverter.format may throw NPE

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