[jira] [Comment Edited] (LOG4J2-223) IllegalStateException thrown during Tomcat shutdown

[ https://issues.apache.org/jira/browse/LOG4J2-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13661524#comment-13661524 ] Remko Popma edited comment on LOG4J2-223 at 5/19/13 10:34 AM: --

[jira] [Comment Edited] (LOG4J2-228) Log4j2 UDP socket configure error. Class not found org.apache.logging.log4j.core.impl.Log4jLogEvent$LogEventProxy

[ https://issues.apache.org/jira/browse/LOG4J2-228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13663867#comment-13663867 ] Remko Popma edited comment on LOG4J2-228 at 5/22/13 6:55 AM: -

[jira] [Commented] (LOG4J2-228) Log4j2 UDP socket configure error. Class not found org.apache.logging.log4j.core.impl.Log4jLogEvent$LogEventProxy

[ https://issues.apache.org/jira/browse/LOG4J2-228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13663867#comment-13663867 ] Remko Popma commented on LOG4J2-228: Hi Imesh, I am in a similar situation as Ralph,

[jira] [Commented] (LOG4J2-232) Custom Converter plugin won't load.

[ https://issues.apache.org/jira/browse/LOG4J2-232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13667018#comment-13667018 ] Remko Popma commented on LOG4J2-232: I'm wondering what to do with this Jira ticket. I

[jira] [Commented] (LOG4J2-238) OSGi dependency failures in core

[ https://issues.apache.org/jira/browse/LOG4J2-238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13667043#comment-13667043 ] Remko Popma commented on LOG4J2-238: Done. OSGi dependency failures

[jira] [Commented] (LOG4J2-154) ThreadContext performance improvement: shallow copies for reads, deep copies for writes

[ https://issues.apache.org/jira/browse/LOG4J2-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13667175#comment-13667175 ] Remko Popma commented on LOG4J2-154: Request for feedback: In interface

[jira] [Comment Edited] (LOG4J2-154) ThreadContext performance improvement: shallow copies for reads, deep copies for writes

[ https://issues.apache.org/jira/browse/LOG4J2-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13667175#comment-13667175 ] Remko Popma edited comment on LOG4J2-154 at 5/26/13 2:18 AM: -

[jira] [Comment Edited] (LOG4J2-154) ThreadContext performance improvement: shallow copies for reads, deep copies for writes

[ https://issues.apache.org/jira/browse/LOG4J2-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13667175#comment-13667175 ] Remko Popma edited comment on LOG4J2-154 at 5/26/13 2:29 AM: -

[jira] [Commented] (LOG4J2-154) ThreadContext performance improvement: shallow copies for reads, deep copies for writes

[ https://issues.apache.org/jira/browse/LOG4J2-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13667421#comment-13667421 ] Remko Popma commented on LOG4J2-154: Initial fix for this issue (use copy-on-write map

[jira] [Commented] (LOG4J2-154) ThreadContext performance improvement: shallow copies for reads, deep copies for writes

[ https://issues.apache.org/jira/browse/LOG4J2-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13667444#comment-13667444 ] Remko Popma commented on LOG4J2-154: Just FYI, I'm seeing some nice performance

[jira] [Commented] (LOG4J2-228) Log4j2 UDP socket configure error. Class not found org.apache.logging.log4j.core.impl.Log4jLogEvent$LogEventProxy

[ https://issues.apache.org/jira/browse/LOG4J2-228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13667709#comment-13667709 ] Remko Popma commented on LOG4J2-228: Imesh, I was actually serious when I suggested

[jira] [Commented] (LOG4J2-228) Log4j2 UDP socket configure error. Class not found org.apache.logging.log4j.core.impl.Log4jLogEvent$LogEventProxy

[ https://issues.apache.org/jira/browse/LOG4J2-228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13668106#comment-13668106 ] Remko Popma commented on LOG4J2-228: Imesh, here are some relevant classes:

[jira] [Resolved] (LOG4J2-232) Custom Converter plugin won't load.

[ https://issues.apache.org/jira/browse/LOG4J2-232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-232. Resolution: Cannot Reproduce Great, thanks for the confirmation! Custom

[jira] [Closed] (LOG4J2-232) Custom Converter plugin won't load.

[ https://issues.apache.org/jira/browse/LOG4J2-232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma closed LOG4J2-232. -- Custom Converter plugin won't load. --- Key:

[jira] [Resolved] (LOG4J2-154) ThreadContext performance improvement: shallow copies for reads, deep copies for writes

[ https://issues.apache.org/jira/browse/LOG4J2-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-154. Resolution: Fixed Fix Version/s: 2.0-beta7 ThreadContext performance improvement:

[jira] [Commented] (LOG4J2-276) java.lang.NoSuchMethodError: org.apache.logging.log4j.spi.LoggerContextFactory.removeContext

[ https://issues.apache.org/jira/browse/LOG4J2-276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13679027#comment-13679027 ] Remko Popma commented on LOG4J2-276: Is it possible that you upgraded the core jar but

[jira] [Commented] (LOG4J2-276) java.lang.NoSuchMethodError: org.apache.logging.log4j.spi.LoggerContextFactory.removeContext

[ https://issues.apache.org/jira/browse/LOG4J2-276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13679034#comment-13679034 ] Remko Popma commented on LOG4J2-276: Great! Glad I was able to help.

[jira] [Closed] (LOG4J2-276) java.lang.NoSuchMethodError: org.apache.logging.log4j.spi.LoggerContextFactory.removeContext

[ https://issues.apache.org/jira/browse/LOG4J2-276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma closed LOG4J2-276. -- java.lang.NoSuchMethodError: org.apache.logging.log4j.spi.LoggerContextFactory.removeContext

[jira] [Commented] (LOG4J2-280) AsynchAppender's AsynchThread blocks Tomcat shutdown

[ https://issues.apache.org/jira/browse/LOG4J2-280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13680784#comment-13680784 ] Remko Popma commented on LOG4J2-280: A similar issue was fixed in beta6. Can you try

[jira] [Assigned] (LOG4J2-292) FastFileAppender overwrites previous log entries

[ https://issues.apache.org/jira/browse/LOG4J2-292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma reassigned LOG4J2-292: -- Assignee: Remko Popma FastFileAppender overwrites previous log entries

[jira] [Assigned] (LOG4J2-267) FastRollingFileAppender doesn't work well with TimeBasedTriggeringPolicy

[ https://issues.apache.org/jira/browse/LOG4J2-267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma reassigned LOG4J2-267: -- Assignee: Remko Popma FastRollingFileAppender doesn't work well with

[jira] [Commented] (LOG4J2-292) FastFileAppender overwrites previous log entries

[ https://issues.apache.org/jira/browse/LOG4J2-292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13691309#comment-13691309 ] Remko Popma commented on LOG4J2-292: Thanks Thomas! I'll take a look as soon as I can.

[jira] [Commented] (LOG4J2-267) FastRollingFileAppender doesn't work well with TimeBasedTriggeringPolicy

[ https://issues.apache.org/jira/browse/LOG4J2-267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13691311#comment-13691311 ] Remko Popma commented on LOG4J2-267: Thanks Thomas! I'll take a look at your patch(es)

[jira] [Commented] (LOG4J2-267) FastRollingFileAppender doesn't work well with TimeBasedTriggeringPolicy

[ https://issues.apache.org/jira/browse/LOG4J2-267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13691602#comment-13691602 ] Remko Popma commented on LOG4J2-267: Thomas, you also provided a patch for

[jira] [Comment Edited] (LOG4J2-267) FastRollingFileAppender doesn't work well with TimeBasedTriggeringPolicy

[ https://issues.apache.org/jira/browse/LOG4J2-267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13691602#comment-13691602 ] Remko Popma edited comment on LOG4J2-267 at 6/23/13 9:20 PM: -

[jira] [Assigned] (LOG4J2-295) BufferOverflowException in FastFileManager when logging huge messages

[ https://issues.apache.org/jira/browse/LOG4J2-295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma reassigned LOG4J2-295: -- Assignee: Remko Popma BufferOverflowException in FastFileManager when logging huge

[jira] [Commented] (LOG4J2-295) BufferOverflowException in FastFileManager when logging huge messages

[ https://issues.apache.org/jira/browse/LOG4J2-295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13695302#comment-13695302 ] Remko Popma commented on LOG4J2-295: Thanks for the report! I'll take a look as soon

[jira] [Comment Edited] (LOG4J2-271) FastRollingFileAppender

[ https://issues.apache.org/jira/browse/LOG4J2-271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13696106#comment-13696106 ] Remko Popma edited comment on LOG4J2-271 at 6/29/13 12:01 PM: --

[jira] [Resolved] (LOG4J2-295) BufferOverflowException in FastFileManager when logging huge messages

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

[jira] [Resolved] (LOG4J2-267) FastRollingFileAppender doesn't work well with TimeBasedTriggeringPolicy

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

[jira] [Resolved] (LOG4J2-292) FastFileAppender overwrites previous log entries

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

[jira] [Commented] (LOG4J2-271) FastRollingFileAppender

[ https://issues.apache.org/jira/browse/LOG4J2-271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13696228#comment-13696228 ] Remko Popma commented on LOG4J2-271: Fixed in revision 1498044. Please verify and

[jira] [Assigned] (LOG4J2-271) FastRollingFileAppender

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

[jira] [Updated] (LOG4J2-292) FastFileAppender overwrites previous log entries

[ https://issues.apache.org/jira/browse/LOG4J2-292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-292: --- Fix Version/s: 2.0-beta8 FastFileAppender overwrites previous log entries

[jira] [Updated] (LOG4J2-295) BufferOverflowException in FastFileManager when logging huge messages

[ https://issues.apache.org/jira/browse/LOG4J2-295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-295: --- Fix Version/s: 2.0-beta8 BufferOverflowException in FastFileManager when logging huge messages

[jira] [Updated] (LOG4J2-267) FastRollingFileAppender doesn't work well with TimeBasedTriggeringPolicy

[ https://issues.apache.org/jira/browse/LOG4J2-267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-267: --- Fix Version/s: 2.0-beta8 FastRollingFileAppender doesn't work well with

[jira] [Updated] (LOG4J2-271) FastRollingFileAppender

[ https://issues.apache.org/jira/browse/LOG4J2-271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-271: --- Fix Version/s: (was: 2.0-beta6) 2.0-beta8 FastRollingFileAppender

[jira] [Assigned] (LOG4J2-280) AsynchAppender's AsynchThread blocks Tomcat shutdown

[ https://issues.apache.org/jira/browse/LOG4J2-280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma reassigned LOG4J2-280: -- Assignee: Remko Popma AsynchAppender's AsynchThread blocks Tomcat shutdown

[jira] [Updated] (LOG4J2-280) AsynchAppender's AsynchThread blocks Tomcat shutdown

[ https://issues.apache.org/jira/browse/LOG4J2-280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-280: --- Fix Version/s: 2.0-beta8 Affects Version/s: 2.0-beta4 2.0-beta5

[jira] [Resolved] (LOG4J2-280) AsynchAppender's AsynchThread blocks Tomcat shutdown

[ https://issues.apache.org/jira/browse/LOG4J2-280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-280. Resolution: Fixed Fixed in revision 1498051: threads used by the async loggers are now daemon

[jira] [Commented] (LOG4J2-270) Improve logging initialization in Servlet containers; reduce amount of extra configuration needed in these contexts

[ https://issues.apache.org/jira/browse/LOG4J2-270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13701569#comment-13701569 ] Remko Popma commented on LOG4J2-270: Nick, while reading the commit email, I noticed

[jira] [Commented] (LOG4J2-229) New JDBC, JPA, and NoSQL database Appenders

[ https://issues.apache.org/jira/browse/LOG4J2-229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13701721#comment-13701721 ] Remko Popma commented on LOG4J2-229: I'm seeing 2 failing JUnit tests that break the

[jira] [Comment Edited] (LOG4J2-229) New JDBC, JPA, and NoSQL database Appenders

[ https://issues.apache.org/jira/browse/LOG4J2-229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13701721#comment-13701721 ] Remko Popma edited comment on LOG4J2-229 at 7/8/13 1:36 AM:

[jira] [Commented] (LOG4J2-229) New JDBC, JPA, and NoSQL database Appenders

[ https://issues.apache.org/jira/browse/LOG4J2-229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13701730#comment-13701730 ] Remko Popma commented on LOG4J2-229: Yes, I'm using windows. Sure I can test after you

[jira] [Commented] (LOG4J2-229) New JDBC, JPA, and NoSQL database Appenders

[ https://issues.apache.org/jira/browse/LOG4J2-229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13701735#comment-13701735 ] Remko Popma commented on LOG4J2-229: Nick, I think that worked. Thanks for the quick

[jira] [Assigned] (LOG4J2-302) NDCPatternConverter broken in beta7

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

[jira] [Created] (LOG4J2-304) Async Loggers cause excessive memory usage and GC pauses

Remko Popma created LOG4J2-304: -- Summary: Async Loggers cause excessive memory usage and GC pauses Key: LOG4J2-304 URL: https://issues.apache.org/jira/browse/LOG4J2-304 Project: Log4j 2 Issue

[jira] [Created] (LOG4J2-307) Upgrade LMAX disruptor library from 3.0.1 to 3.1.1

Remko Popma created LOG4J2-307: -- Summary: Upgrade LMAX disruptor library from 3.0.1 to 3.1.1 Key: LOG4J2-307 URL: https://issues.apache.org/jira/browse/LOG4J2-307 Project: Log4j 2 Issue Type:

[jira] [Resolved] (LOG4J2-307) Upgrade LMAX disruptor library from 3.0.1 to 3.1.1

[ https://issues.apache.org/jira/browse/LOG4J2-307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-307. Resolution: Fixed Committed in revision 1502781, updated docs in revision 1502927.

[jira] [Closed] (LOG4J2-307) Upgrade LMAX disruptor library from 3.0.1 to 3.1.1

[ https://issues.apache.org/jira/browse/LOG4J2-307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma closed LOG4J2-307. -- Upgrade LMAX disruptor library from 3.0.1 to 3.1.1

[jira] [Created] (LOG4J2-308) Clarify which library versions were used in Async Loggers performance test

Remko Popma created LOG4J2-308: -- Summary: Clarify which library versions were used in Async Loggers performance test Key: LOG4J2-308 URL: https://issues.apache.org/jira/browse/LOG4J2-308 Project: Log4j

[jira] [Resolved] (LOG4J2-308) Clarify which library versions were used in Async Loggers performance test

[ https://issues.apache.org/jira/browse/LOG4J2-308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-308. Resolution: Fixed Manual page updated in revision 1502783. Changes.xml updated in revision

[jira] [Closed] (LOG4J2-308) Clarify which library versions were used in Async Loggers performance test

[ https://issues.apache.org/jira/browse/LOG4J2-308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma closed LOG4J2-308. -- Clarify which library versions were used in Async Loggers performance test

[jira] [Updated] (LOG4J2-311) FastFileAppender and FastRollingFileAppender not thread-safe

[ https://issues.apache.org/jira/browse/LOG4J2-311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-311: --- Description: FastFileManager#flush method needs to be synchronized. I'm seeing the exception below.

[jira] [Created] (LOG4J2-311) FastFileAppender and FastRollingFileAppender not thread-safe

Remko Popma created LOG4J2-311: -- Summary: FastFileAppender and FastRollingFileAppender not thread-safe Key: LOG4J2-311 URL: https://issues.apache.org/jira/browse/LOG4J2-311 Project: Log4j 2

[jira] [Assigned] (LOG4J2-311) FastFileAppender and FastRollingFileAppender not thread-safe

[ https://issues.apache.org/jira/browse/LOG4J2-311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma reassigned LOG4J2-311: -- Assignee: Remko Popma FastFileAppender and FastRollingFileAppender not thread-safe

[jira] [Resolved] (LOG4J2-311) FastFileAppender and FastRollingFileAppender not thread-safe

[ https://issues.apache.org/jira/browse/LOG4J2-311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-311. Resolution: Fixed Fixed in revision 1504297: Made close() and flush() methods synchronized in

[jira] [Commented] (LOG4J2-238) OSGi dependency failures in core

[ https://issues.apache.org/jira/browse/LOG4J2-238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13712086#comment-13712086 ] Remko Popma commented on LOG4J2-238: Bob, some work was done on this issue as well as

[jira] [Commented] (LOG4J2-10) log4j 2.0 should work well with OSGi and Apache Felix

[ https://issues.apache.org/jira/browse/LOG4J2-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13712087#comment-13712087 ] Remko Popma commented on LOG4J2-10: --- Ralph, did you eventually commit this? If so,

[jira] [Commented] (LOG4J2-314) Multiple thread creation problem with AsyncAppender

[ https://issues.apache.org/jira/browse/LOG4J2-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13713341#comment-13713341 ] Remko Popma commented on LOG4J2-314: Thanks! Can you also show how you

[jira] [Comment Edited] (LOG4J2-314) Multiple thread creation problem with AsyncAppender

[ https://issues.apache.org/jira/browse/LOG4J2-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13713341#comment-13713341 ] Remko Popma edited comment on LOG4J2-314 at 7/19/13 6:03 AM: -

[jira] [Commented] (LOG4J2-315) Multiple threads logging to same AsyncAppender- Data Loss

[ https://issues.apache.org/jira/browse/LOG4J2-315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13713567#comment-13713567 ] Remko Popma commented on LOG4J2-315: I was able to reproduce the issue. I got this

[jira] [Commented] (LOG4J2-315) Multiple threads logging to same AsyncAppender- Data Loss

[ https://issues.apache.org/jira/browse/LOG4J2-315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13713783#comment-13713783 ] Remko Popma commented on LOG4J2-315: Sudharma, I did not mean to say you should use

[jira] [Commented] (LOG4J2-314) Multiple thread creation problem with AsyncAppender

[ https://issues.apache.org/jira/browse/LOG4J2-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13713832#comment-13713832 ] Remko Popma commented on LOG4J2-314: Sudharma, I appreciate you taking the time to

[jira] [Created] (LOG4J2-317) Rename FastFileAppender and FastRollingFileAppender

Remko Popma created LOG4J2-317: -- Summary: Rename FastFileAppender and FastRollingFileAppender Key: LOG4J2-317 URL: https://issues.apache.org/jira/browse/LOG4J2-317 Project: Log4j 2 Issue Type:

[jira] [Commented] (LOG4J2-314) Multiple thread creation problem with AsyncAppender

[ https://issues.apache.org/jira/browse/LOG4J2-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13714346#comment-13714346 ] Remko Popma commented on LOG4J2-314: [~sdeboy]: One thread (AsyncLoggers or

[jira] [Commented] (LOG4J2-191) Improve plugin uniqueness by name and type, not just name

[ https://issues.apache.org/jira/browse/LOG4J2-191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13714358#comment-13714358 ] Remko Popma commented on LOG4J2-191: Scott, what are your plans for this ticket?

[jira] [Commented] (LOG4J2-10) log4j 2.0 should work well with OSGi and Apache Felix

[ https://issues.apache.org/jira/browse/LOG4J2-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13714359#comment-13714359 ] Remko Popma commented on LOG4J2-10: --- Timothy, we may not have the expertise in the Log4j

[jira] [Commented] (LOG4J2-242) Make Messages more fluent

[ https://issues.apache.org/jira/browse/LOG4J2-242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13714362#comment-13714362 ] Remko Popma commented on LOG4J2-242: Nick, Ralph, Gary, is this in scope for the 2.0

[jira] [Updated] (LOG4J2-166) Routing Appender default Route broken for references

[ https://issues.apache.org/jira/browse/LOG4J2-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-166: --- Description: I recently updated to using beta4 and ran into a problem upon startup where I received

[jira] [Updated] (LOG4J2-166) Routing Appender default Route broken for references

[ https://issues.apache.org/jira/browse/LOG4J2-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-166: --- Description: I recently updated to using beta4 and ran into a problem upon startup where I received

[jira] [Commented] (LOG4J2-303) No WriterAppender functionality in Log4j2

[ https://issues.apache.org/jira/browse/LOG4J2-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13714373#comment-13714373 ] Remko Popma commented on LOG4J2-303: Tom, is this issue resolved? No

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

[ https://issues.apache.org/jira/browse/LOG4J2-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13714375#comment-13714375 ] Remko Popma commented on LOG4J2-124: Should we add a #shutdown() method to LogManager

[jira] [Commented] (LOG4J2-318) On termination Log4j terminates before the application

[ https://issues.apache.org/jira/browse/LOG4J2-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13714423#comment-13714423 ] Remko Popma commented on LOG4J2-318: Or log4j2.disable.shutdownHook=true (because it's

[jira] [Commented] (LOG4J2-317) Rename FastFileAppender and FastRollingFileAppender

[ https://issues.apache.org/jira/browse/LOG4J2-317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13714426#comment-13714426 ] Remko Popma commented on LOG4J2-317: Tricky to find a good name for the rolling

[jira] [Commented] (LOG4J2-317) Rename FastFileAppender and FastRollingFileAppender

[ https://issues.apache.org/jira/browse/LOG4J2-317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13714428#comment-13714428 ] Remko Popma commented on LOG4J2-317: These make for some really wacky acronyms too:

[jira] [Commented] (LOG4J2-318) On termination Log4j terminates before the application

[ https://issues.apache.org/jira/browse/LOG4J2-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13714431#comment-13714431 ] Remko Popma commented on LOG4J2-318: I don't disagree with you. If you want to

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

[ https://issues.apache.org/jira/browse/LOG4J2-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13714654#comment-13714654 ] Remko Popma commented on LOG4J2-124: Ralph, in LOG4J2-318 you mention that you don't

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

[ https://issues.apache.org/jira/browse/LOG4J2-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13714666#comment-13714666 ] Remko Popma edited comment on LOG4J2-124 at 7/21/13 8:28 AM: -

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

[ https://issues.apache.org/jira/browse/LOG4J2-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13714669#comment-13714669 ] Remko Popma commented on LOG4J2-124: I forget: is Configurator part of api or core?

[jira] [Commented] (LOG4J2-280) AsynchAppender's AsynchThread blocks Tomcat shutdown

[ https://issues.apache.org/jira/browse/LOG4J2-280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13714961#comment-13714961 ] Remko Popma commented on LOG4J2-280: Matej, AsyncLogger threads are definitely daemon

[jira] [Reopened] (LOG4J2-280) AsynchAppender's AsynchThread blocks Tomcat shutdown

[ https://issues.apache.org/jira/browse/LOG4J2-280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma reopened LOG4J2-280: Ah... My mistake! Only AsyncLogger threads are daemon threads. I did not fix the AsyncAppender

[jira] [Commented] (LOG4J2-280) AsynchAppender's AsynchThread blocks Tomcat shutdown

[ https://issues.apache.org/jira/browse/LOG4J2-280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13715126#comment-13715126 ] Remko Popma commented on LOG4J2-280: The simplest way to use AsyncLoggers would be to

[jira] [Comment Edited] (LOG4J2-314) Multiple thread creation problem with AsyncAppender

[ https://issues.apache.org/jira/browse/LOG4J2-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13716219#comment-13716219 ] Remko Popma edited comment on LOG4J2-314 at 7/23/13 8:06 AM: -

[jira] [Commented] (LOG4J2-314) Multiple thread creation problem with AsyncAppender

[ https://issues.apache.org/jira/browse/LOG4J2-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13716261#comment-13716261 ] Remko Popma commented on LOG4J2-314: I'm not that familiar with how the

[jira] [Commented] (LOG4J2-314) Multiple thread creation problem with AsyncAppender

[ https://issues.apache.org/jira/browse/LOG4J2-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13716270#comment-13716270 ] Remko Popma commented on LOG4J2-314: I don't understand why the 1st does not work. My

[jira] [Commented] (LOG4J2-314) Multiple thread creation problem with AsyncAppender

[ https://issues.apache.org/jira/browse/LOG4J2-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13716273#comment-13716273 ] Remko Popma commented on LOG4J2-314: Oops... I see. If a route does not have a key is

[jira] [Comment Edited] (LOG4J2-314) Multiple thread creation problem with AsyncAppender

[ https://issues.apache.org/jira/browse/LOG4J2-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13716273#comment-13716273 ] Remko Popma edited comment on LOG4J2-314 at 7/23/13 9:59 AM: -

[jira] [Updated] (LOG4J2-314) How to create multiple appenders at runtime, sharing an AsyncAppender?

[ https://issues.apache.org/jira/browse/LOG4J2-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-314: --- Summary: How to create multiple appenders at runtime, sharing an AsyncAppender? (was: Multiple

[jira] [Commented] (LOG4J2-314) How to create multiple appenders at runtime, sharing an AsyncAppender?

[ https://issues.apache.org/jira/browse/LOG4J2-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13716297#comment-13716297 ] Remko Popma commented on LOG4J2-314: I see... If you don't call

[jira] [Resolved] (LOG4J2-314) How to create multiple appenders at runtime, sharing an AsyncAppender?

[ https://issues.apache.org/jira/browse/LOG4J2-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-314. Resolution: Fixed OK, I will mark this Jira ticket as resolved. Please remember, if you need

[jira] [Resolved] (LOG4J2-280) AsynchAppender's AsynchThread blocks Tomcat shutdown

[ https://issues.apache.org/jira/browse/LOG4J2-280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-280. Resolution: Fixed Fix Version/s: 2.0-beta9 Committed revision 1506290: Additional fix to

[jira] [Created] (LOG4J2-321) Provide configuration alternative to system properties

Remko Popma created LOG4J2-321: -- Summary: Provide configuration alternative to system properties Key: LOG4J2-321 URL: https://issues.apache.org/jira/browse/LOG4J2-321 Project: Log4j 2 Issue

[jira] [Commented] (LOG4J2-321) Provide configuration alternative to system properties

[ https://issues.apache.org/jira/browse/LOG4J2-321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13721797#comment-13721797 ] Remko Popma commented on LOG4J2-321: From: Ralph Goers To: Log4J Developers List

[jira] [Commented] (LOG4J2-321) Provide configuration alternative to system properties

[ https://issues.apache.org/jira/browse/LOG4J2-321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13721799#comment-13721799 ] Remko Popma commented on LOG4J2-321: Proposed sample configuration: {code}

[jira] [Commented] (LOG4J2-321) Provide configuration alternative to system properties

[ https://issues.apache.org/jira/browse/LOG4J2-321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13722059#comment-13722059 ] Remko Popma commented on LOG4J2-321: I don't like the additional element. At the

[jira] [Created] (LOG4J2-324) Potential performance improvement for StatusLogger

Remko Popma created LOG4J2-324: -- Summary: Potential performance improvement for StatusLogger Key: LOG4J2-324 URL: https://issues.apache.org/jira/browse/LOG4J2-324 Project: Log4j 2 Issue Type:

[jira] [Commented] (LOG4J2-324) Potential performance improvement for StatusLogger

[ https://issues.apache.org/jira/browse/LOG4J2-324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13722118#comment-13722118 ] Remko Popma commented on LOG4J2-324: When you say will impact performance, what do you

[jira] [Commented] (LOG4J2-324) Potential performance improvement for StatusLogger

[ https://issues.apache.org/jira/browse/LOG4J2-324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13722151#comment-13722151 ] Remko Popma commented on LOG4J2-324: The drawback of keeping StatusData objects in the

[jira] [Commented] (LOG4J2-324) Potential performance improvement for StatusLogger

[ https://issues.apache.org/jira/browse/LOG4J2-324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=1371#comment-1371 ] Remko Popma commented on LOG4J2-324: I see. In that case the statusLevel idea is still

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