[jira] [Resolved] (LOG4J2-327) Log4j 2 drastical performance loss

[ https://issues.apache.org/jira/browse/LOG4J2-327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-327. Resolution: Not A Problem Fix Version/s: 2.0-beta9 Resolving this issue as not a problem

[jira] [Closed] (LOG4J2-327) Log4j 2 drastical performance loss

[ https://issues.apache.org/jira/browse/LOG4J2-327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma closed LOG4J2-327. -- Thanks for the feedback, Sebastian. Closing this issue. Log4j 2 drastical performance

[jira] [Updated] (LOG4J2-336) AsyncLogger.log fail with NullPointerException after double reconfigure

[ https://issues.apache.org/jira/browse/LOG4J2-336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-336: --- Description: Using reconfigure() to select log files at runtime. After the second reconfigure, the

[jira] [Commented] (LOG4J2-336) AsyncLogger.log fail with NullPointerException after double reconfigure

[ https://issues.apache.org/jira/browse/LOG4J2-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13733030#comment-13733030 ] Remko Popma commented on LOG4J2-336: Thanks for finding this. On reconfiguration, a

[jira] [Commented] (LOG4J2-336) AsyncLogger.log fail with NullPointerException after double reconfigure

[ https://issues.apache.org/jira/browse/LOG4J2-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13733291#comment-13733291 ] Remko Popma commented on LOG4J2-336: Yes, this will be fixed with beta9. Not sure when

[jira] [Commented] (LOG4J2-344) Log4j2 doesnt work with Weblogic 12c

[ https://issues.apache.org/jira/browse/LOG4J2-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13736768#comment-13736768 ] Remko Popma commented on LOG4J2-344: Could you post a full stack trace, your log4j

[jira] [Commented] (LOG4J2-346) Cyclic dependency in OSGi-context. Apache Log4j SLF4J Binding - slf4j-api

[ https://issues.apache.org/jira/browse/LOG4J2-346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13738064#comment-13738064 ] Remko Popma commented on LOG4J2-346: Roland, we are all volunteers working on log4j in

[jira] [Commented] (LOG4J2-336) AsyncLogger.log fail with NullPointerException after double reconfigure

[ https://issues.apache.org/jira/browse/LOG4J2-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13739082#comment-13739082 ] Remko Popma commented on LOG4J2-336: I was finally able to track this down to an

[jira] [Assigned] (LOG4J2-347) Name the AsyncThread

[ https://issues.apache.org/jira/browse/LOG4J2-347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma reassigned LOG4J2-347: -- Assignee: Remko Popma Name the AsyncThread Key:

[jira] [Resolved] (LOG4J2-347) Name the AsyncThread

[ https://issues.apache.org/jira/browse/LOG4J2-347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-347. Resolution: Fixed Fix Version/s: 2.0-beta9 Fixed in revision 1513710. Please verify and

[jira] [Commented] (LOG4J2-333) match artifact ids with Maven module names

[ https://issues.apache.org/jira/browse/LOG4J2-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13739150#comment-13739150 ] Remko Popma commented on LOG4J2-333: Is Blocker the correct priority for this issue?

[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=13739399#comment-13739399 ] Remko Popma commented on LOG4J2-315: Yes. I'm still off work the rest of this week I

[jira] [Commented] (LOG4J2-336) AsyncLogger.log fail with NullPointerException after double reconfigure

[ https://issues.apache.org/jira/browse/LOG4J2-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13739580#comment-13739580 ] Remko Popma commented on LOG4J2-336: Andre, during a reconfigure, new Appenders and

[jira] [Resolved] (LOG4J2-336) AsyncLogger.log fail with NullPointerException after double reconfigure

[ https://issues.apache.org/jira/browse/LOG4J2-336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-336. Resolution: Fixed Fix Version/s: 2.0-beta9 Fixed in revision 1513832. Please verify and

[jira] [Commented] (LOG4J2-336) AsyncLogger.log fail with NullPointerException after double reconfigure

[ https://issues.apache.org/jira/browse/LOG4J2-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13739604#comment-13739604 ] Remko Popma commented on LOG4J2-336: Andre, one reason I can see is that it is

[jira] [Created] (LOG4J2-351) [OSGi] wrong Fragment-Host in manifest files

Remko Popma created LOG4J2-351: -- Summary: [OSGi] wrong Fragment-Host in manifest files Key: LOG4J2-351 URL: https://issues.apache.org/jira/browse/LOG4J2-351 Project: Log4j 2 Issue Type: Bug

[jira] [Resolved] (LOG4J2-351) [OSGi] wrong Fragment-Host in manifest files

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

[jira] [Commented] (LOG4J2-351) [OSGi] wrong Fragment-Host in manifest files

[ https://issues.apache.org/jira/browse/LOG4J2-351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13739668#comment-13739668 ] Remko Popma commented on LOG4J2-351: Listing affected files for reference: commit -m

[jira] [Comment Edited] (LOG4J2-351) [OSGi] wrong Fragment-Host in manifest files

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

[jira] [Comment Edited] (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=13739726#comment-13739726 ] Remko Popma edited comment on LOG4J2-321 at 8/14/13 2:41 PM: -

[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=13739726#comment-13739726 ] Remko Popma commented on LOG4J2-321: About the Log4jContextSelector, is it possible to

[jira] [Comment Edited] (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=13739726#comment-13739726 ] Remko Popma edited comment on LOG4J2-321 at 8/14/13 2:51 PM: -

[jira] [Updated] (LOG4J2-343) Remove the Generics from Appender

[ https://issues.apache.org/jira/browse/LOG4J2-343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-343: --- Attachment: LOG4J2-343_20130815-1117+0900.patch Attached LOG4J2-343_20130815-1117+0900.patch

[jira] [Resolved] (LOG4J2-343) Remove the Generics from Appender

[ https://issues.apache.org/jira/browse/LOG4J2-343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-343. Resolution: Fixed Fix Version/s: 2.0-beta9 Committed in revision 1514231. Please verify and

[jira] [Assigned] (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:all-tabpanel ] Remko Popma reassigned LOG4J2-315: -- Assignee: Remko Popma Multiple threads logging to same AsyncAppender- Data Loss

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

Remko Popma created LOG4J2-354: -- Summary: log4j2 + FastFileAppender + Tomcat logrotate problem Key: LOG4J2-354 URL: https://issues.apache.org/jira/browse/LOG4J2-354 Project: Log4j 2 Issue Type:

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

[ https://issues.apache.org/jira/browse/LOG4J2-354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13741924#comment-13741924 ] Remko Popma commented on LOG4J2-354: (quick heads-up: FastFileAppender will be renamed

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

[ https://issues.apache.org/jira/browse/LOG4J2-354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13741924#comment-13741924 ] Remko Popma edited comment on LOG4J2-354 at 8/16/13 5:15 AM: -

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

[ https://issues.apache.org/jira/browse/LOG4J2-321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma reassigned LOG4J2-321: -- Assignee: Remko Popma Provide configuration alternative to system properties

[jira] [Commented] (LOG4J2-344) Log4j2 doesnt work with Weblogic 12c

[ https://issues.apache.org/jira/browse/LOG4J2-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13741934#comment-13741934 ] Remko Popma commented on LOG4J2-344: Keir, do you have any additional information?

[jira] [Commented] (LOG4J2-344) Log4j2 doesnt work with Weblogic 12c

[ https://issues.apache.org/jira/browse/LOG4J2-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13742664#comment-13742664 ] Remko Popma commented on LOG4J2-344: Keir, Your stacktrace says Truncated. see log

[jira] [Commented] (LOG4J2-344) Log4j2 doesnt work with Weblogic 12c

[ https://issues.apache.org/jira/browse/LOG4J2-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13742690#comment-13742690 ] Remko Popma commented on LOG4J2-344: Keir, it would also be good to know if your log

[jira] [Updated] (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:all-tabpanel ] Remko Popma updated LOG4J2-315: --- Attachment: log4j2.xml ResultStats.java Still struggling with this. Not sure if the

[jira] [Created] (LOG4J2-362) Add a diagram to the site that explains when to use which jar

Remko Popma created LOG4J2-362: -- Summary: Add a diagram to the site that explains when to use which jar Key: LOG4J2-362 URL: https://issues.apache.org/jira/browse/LOG4J2-362 Project: Log4j 2

[jira] [Updated] (LOG4J2-253) Add a FAQ/Troubleshooting page to the site?

[ https://issues.apache.org/jira/browse/LOG4J2-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-253: --- Attachment: whichjar.png attached whichjar.png initial version Add a

[jira] [Updated] (LOG4J2-253) Add a FAQ/Troubleshooting page to the site?

[ https://issues.apache.org/jira/browse/LOG4J2-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-253: --- Attachment: (was: whichjar.png) Add a FAQ/Troubleshooting page to the site?

[jira] [Issue Comment Deleted] (LOG4J2-253) Add a FAQ/Troubleshooting page to the site?

[ https://issues.apache.org/jira/browse/LOG4J2-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-253: --- Comment: was deleted (was: attached whichjar.png initial version) Add a FAQ/Troubleshooting

[jira] [Updated] (LOG4J2-362) Add a diagram to the site that explains when to use which jar

[ https://issues.apache.org/jira/browse/LOG4J2-362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-362: --- Attachment: whichjar.png attached whichjar.png initial version Add a diagram to

[jira] [Commented] (LOG4J2-362) Add a diagram to the site that explains when to use which jar

[ https://issues.apache.org/jira/browse/LOG4J2-362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13742939#comment-13742939 ] Remko Popma commented on LOG4J2-362: Ah, thanks Nick! I'll update in a few minutes.

[jira] [Updated] (LOG4J2-362) Add a diagram to the site that explains when to use which jar

[ https://issues.apache.org/jira/browse/LOG4J2-362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-362: --- Attachment: whichjar-slf4j.png attached whichjar-slf4j.png initial version Add a

[jira] [Updated] (LOG4J2-362) Add a diagram to the site that explains when to use which jar

[ https://issues.apache.org/jira/browse/LOG4J2-362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-362: --- Attachment: whichjar-slf4j-1.png whichjar-1.png attached whichjar-1.jar and

[jira] [Comment Edited] (LOG4J2-362) Add a diagram to the site that explains when to use which jar

[ https://issues.apache.org/jira/browse/LOG4J2-362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13742949#comment-13742949 ] Remko Popma edited comment on LOG4J2-362 at 8/17/13 3:07 PM: -

[jira] [Commented] (LOG4J2-362) Add a diagram to the site that explains when to use which jar

[ https://issues.apache.org/jira/browse/LOG4J2-362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13742950#comment-13742950 ] Remko Popma commented on LOG4J2-362: Nick, I only see Delete as possible action for

[jira] [Commented] (LOG4J2-363) change dependency from commons logging impl to commons logging API

[ https://issues.apache.org/jira/browse/LOG4J2-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13743892#comment-13743892 ] Remko Popma commented on LOG4J2-363: Gary, not sure what you mean. Currently

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

[ https://issues.apache.org/jira/browse/LOG4J2-365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13744817#comment-13744817 ] Remko Popma commented on LOG4J2-365: * should your classpath not be: -cp

[jira] [Comment Edited] (LOG4J2-365) ERROR StatusLogger Unable to locate a logging implementation, using SimpleLogge

[ https://issues.apache.org/jira/browse/LOG4J2-365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13744817#comment-13744817 ] Remko Popma edited comment on LOG4J2-365 at 8/20/13 9:43 AM: -

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

[ https://issues.apache.org/jira/browse/LOG4J2-365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13744856#comment-13744856 ] Remko Popma commented on LOG4J2-365: I guess it depends on what your launcher thing

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

[ https://issues.apache.org/jira/browse/LOG4J2-365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13745639#comment-13745639 ] Remko Popma commented on LOG4J2-365: You're using launcher to start a child process.

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

[ https://issues.apache.org/jira/browse/LOG4J2-365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13745672#comment-13745672 ] Remko Popma commented on LOG4J2-365: Here is an example launcher that makes sure the

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

[ https://issues.apache.org/jira/browse/LOG4J2-365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13745837#comment-13745837 ] Remko Popma commented on LOG4J2-365: Somewhere in your child process, can you print

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

[ https://issues.apache.org/jira/browse/LOG4J2-365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13745927#comment-13745927 ] Remko Popma commented on LOG4J2-365: if the log4j2.xml file is inside a jar, you could

[jira] [Reopened] (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 reopened LOG4J2-307: re-open to update version number Upgrade LMAX disruptor library from 3.0.1 to 3.1.1

[jira] [Resolved] (LOG4J2-307) Upgrade LMAX disruptor library from 3.0.1 to 3.2.0 (was 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 Updated to disruptor 3.2.0 in revision 1517552. Upgrade LMAX

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

[ https://issues.apache.org/jira/browse/LOG4J2-307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-307: --- Description: Upgrade LMAX Disruptor library from 3.0.1 to 3.1.1. Edit 2013-8-26: the latest version

[jira] [Comment Edited] (LOG4J2-372) Build-path-issue. Invalid file or path...

[ https://issues.apache.org/jira/browse/LOG4J2-372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13750166#comment-13750166 ] Remko Popma edited comment on LOG4J2-372 at 8/26/13 3:57 PM: -

[jira] [Commented] (LOG4J2-310) SMTPAppender does not send mails with error or fatal level without prior info event

[ https://issues.apache.org/jira/browse/LOG4J2-310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13751316#comment-13751316 ] Remko Popma commented on LOG4J2-310: The three lines you propose to remove were added

[jira] [Commented] (LOG4J2-376) FastRollingFile has been replaced

[ https://issues.apache.org/jira/browse/LOG4J2-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13751322#comment-13751322 ] Remko Popma commented on LOG4J2-376: I thought Gary updated the docs as well when he

[jira] [Comment Edited] (LOG4J2-376) FastRollingFile has been replaced

[ https://issues.apache.org/jira/browse/LOG4J2-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13751322#comment-13751322 ] Remko Popma edited comment on LOG4J2-376 at 8/27/13 2:47 PM: -

[jira] [Commented] (LOG4J2-310) SMTPAppender does not send mails with error or fatal level without prior info event

[ https://issues.apache.org/jira/browse/LOG4J2-310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13751769#comment-13751769 ] Remko Popma commented on LOG4J2-310: Well, you're both right. I obviously should have

[jira] [Resolved] (LOG4J2-310) SMTPAppender does not send mails with error or fatal level without prior info event

[ https://issues.apache.org/jira/browse/LOG4J2-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-310. Resolution: Fixed Fix Version/s: 2.0-beta9 Assignee: Remko Popma Committed in

[jira] [Resolved] (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:all-tabpanel ] Remko Popma resolved LOG4J2-315. Resolution: Not A Problem I finally found the answer to why this is happening: it's the spec. By

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

[ https://issues.apache.org/jira/browse/LOG4J2-354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13755668#comment-13755668 ] Remko Popma commented on LOG4J2-354: Kamil, You seem to rotate logs fairly quickly so

[jira] [Created] (LOG4J2-379) Problem using log4j2 in Google App Engine

Remko Popma created LOG4J2-379: -- Summary: Problem using log4j2 in Google App Engine Key: LOG4J2-379 URL: https://issues.apache.org/jira/browse/LOG4J2-379 Project: Log4j 2 Issue Type:

[jira] [Closed] (LOG4J2-253) Add a FAQ/Troubleshooting page to the site?

[ https://issues.apache.org/jira/browse/LOG4J2-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma closed LOG4J2-253. -- Add a FAQ/Troubleshooting page to the site? ---

[jira] [Resolved] (LOG4J2-253) Add a FAQ/Troubleshooting page to the site?

[ https://issues.apache.org/jira/browse/LOG4J2-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-253. Resolution: Fixed Fix Version/s: 2.0-beta9 Assignee: Remko Popma Added for beta9.

[jira] [Resolved] (LOG4J2-362) Add a diagram to the site that explains when to use which jar

[ https://issues.apache.org/jira/browse/LOG4J2-362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-362. Resolution: Fixed Assignee: Remko Popma Added diagrams to the new FAQ page. Committed in

[jira] [Closed] (LOG4J2-362) Add a diagram to the site that explains when to use which jar

[ https://issues.apache.org/jira/browse/LOG4J2-362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma closed LOG4J2-362. -- Add a diagram to the site that explains when to use which jar

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

[ https://issues.apache.org/jira/browse/LOG4J2-396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13759621#comment-13759621 ] Remko Popma commented on LOG4J2-396: Is your application running in a

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

[ https://issues.apache.org/jira/browse/LOG4J2-396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13759699#comment-13759699 ] Remko Popma commented on LOG4J2-396: Thanks for showing the sample program. This looks

[jira] [Commented] (LOG4J2-379) Problem using log4j2 in Google App Engine

[ https://issues.apache.org/jira/browse/LOG4J2-379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13770150#comment-13770150 ] Remko Popma commented on LOG4J2-379: Michael, can you also post your log4j2.xml

[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=13772489#comment-13772489 ] Remko Popma commented on LOG4J2-406: Nick, I did't have much time to work on this but

[jira] [Assigned] (LOG4J2-379) Problem using log4j2 in Google App Engine

[ https://issues.apache.org/jira/browse/LOG4J2-379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma reassigned LOG4J2-379: -- Assignee: Remko Popma Problem using log4j2 in Google App Engine

[jira] [Commented] (LOG4J2-379) Problem using log4j2 in Google App Engine

[ https://issues.apache.org/jira/browse/LOG4J2-379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13774222#comment-13774222 ] Remko Popma commented on LOG4J2-379: On closer inspection it seems that the error

[jira] [Resolved] (LOG4J2-379) Problem using log4j2 in Google App Engine

[ https://issues.apache.org/jira/browse/LOG4J2-379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-379. Resolution: Fixed Fix Version/s: 2.0-rc1 I went ahead and made this change; it may not be

[jira] [Closed] (LOG4J2-376) FastRollingFile has been replaced

[ https://issues.apache.org/jira/browse/LOG4J2-376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma closed LOG4J2-376. -- FastRollingFile has been replaced - Key:

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

[ https://issues.apache.org/jira/browse/LOG4J2-354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13774271#comment-13774271 ] Remko Popma commented on LOG4J2-354: Kamil, Did you have a chance to try the log4j2

[jira] [Commented] (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:comment-tabpanelfocusedCommentId=13783053#comment-13783053 ] Remko Popma commented on LOG4J2-414: Thanks for the detailed report. I'm not sure what

[jira] [Commented] (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:comment-tabpanelfocusedCommentId=13783068#comment-13783068 ] Remko Popma commented on LOG4J2-414: Just FYI, with the default size I calculate that

[jira] [Commented] (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:comment-tabpanelfocusedCommentId=13783084#comment-13783084 ] Remko Popma commented on LOG4J2-414: One more question: does the problem happen at

[jira] [Commented] (LOG4J2-415) Format log event time as UNIX time.

[ https://issues.apache.org/jira/browse/LOG4J2-415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13783470#comment-13783470 ] Remko Popma commented on LOG4J2-415: I would prefer the separate

[jira] [Commented] (LOG4J2-415) Format log event time as UNIX time.

[ https://issues.apache.org/jira/browse/LOG4J2-415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13783520#comment-13783520 ] Remko Popma commented on LOG4J2-415: I see... Would it be possible to instantiate a

[jira] [Commented] (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:comment-tabpanelfocusedCommentId=13783890#comment-13783890 ] Remko Popma commented on LOG4J2-414: Ok. I would recommend the RandomAccessFile

[jira] [Updated] (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 updated LOG4J2-414: --- Description: 1. Problem description: The main function of my company's system is to read a file and

[jira] [Comment Edited] (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:comment-tabpanelfocusedCommentId=13784042#comment-13784042 ] Remko Popma edited comment on LOG4J2-414 at 10/2/13 2:59 PM: -

[jira] [Comment Edited] (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:comment-tabpanelfocusedCommentId=13784042#comment-13784042 ] Remko Popma edited comment on LOG4J2-414 at 10/2/13 3:00 PM: -

[jira] [Commented] (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:comment-tabpanelfocusedCommentId=13784042#comment-13784042 ] Remko Popma commented on LOG4J2-414: If the ring buffer is very small, and the

[jira] [Comment Edited] (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:comment-tabpanelfocusedCommentId=13784042#comment-13784042 ] Remko Popma edited comment on LOG4J2-414 at 10/2/13 3:05 PM: -

[jira] [Comment Edited] (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:comment-tabpanelfocusedCommentId=13784042#comment-13784042 ] Remko Popma edited comment on LOG4J2-414 at 10/2/13 3:04 PM: -

[jira] [Commented] (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:comment-tabpanelfocusedCommentId=13784084#comment-13784084 ] Remko Popma commented on LOG4J2-414: I just thought of something else: it could be

[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=13784947#comment-13784947 ] Remko Popma commented on LOG4J2-416: I'm not sure if it is possible to do this in a

[jira] [Comment Edited] (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=13784947#comment-13784947 ] Remko Popma edited comment on LOG4J2-416 at 10/3/13 9:41 AM: -

[jira] [Commented] (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:comment-tabpanelfocusedCommentId=13785231#comment-13785231 ] Remko Popma commented on LOG4J2-414: Good point. I've done some back-of-the-napkin

[jira] [Commented] (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:comment-tabpanelfocusedCommentId=13787439#comment-13787439 ] Remko Popma commented on LOG4J2-414: Yiru, did you have any luck finding out where the

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

Remko Popma created LOG4J2-423: -- Summary: Provide a means to inspect queue usage for Async Loggers and Async Appender Key: LOG4J2-423 URL: https://issues.apache.org/jira/browse/LOG4J2-423 Project: Log4j

[jira] [Commented] (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:comment-tabpanelfocusedCommentId=13793572#comment-13793572 ] Remko Popma commented on LOG4J2-414: Yiru, any update? Anything I can do to help?

[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=13793573#comment-13793573 ] Remko Popma commented on LOG4J2-416: Dimitry, anyone else, what is your thinking on

[jira] [Updated] (LOG4J2-412) RollingRandomAccessFile appender loses output when fileName/filePattern accesses ${sys:property}

[ https://issues.apache.org/jira/browse/LOG4J2-412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-412: --- Description: Using sample config for RollingRandomAccessFile, with log name retrieved from

[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=13793674#comment-13793674 ] Remko Popma commented on LOG4J2-416: I've thought about it some more. The

[jira] [Resolved] (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:all-tabpanel ] Remko Popma resolved LOG4J2-426. Resolution: Duplicate Sergey, thank you for reporting this issue. It turns out this one is already

[jira] [Updated] (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 updated LOG4J2-425: --- Description: Thread local 'currentLogEvent' is not cleaned on shutdown which prevent web

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