[jira] [Created] (LOG4J2-405) Log4jConfigListener is starting LoggerContext twice

2013-09-19 Thread Poorna Subhash P (JIRA)
Poorna Subhash P created LOG4J2-405: --- Summary: Log4jConfigListener is starting LoggerContext twice Key: LOG4J2-405 URL: https://issues.apache.org/jira/browse/LOG4J2-405 Project: Log4j 2

[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.

2013-09-19 Thread Nick Williams (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13772120#comment-13772120 ] Nick Williams commented on LOG4J2-406: -- The {{ServletContextListener}} correctly

[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.

2013-09-19 Thread Kerrigan Joseph (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13772132#comment-13772132 ] Kerrigan Joseph edited comment on LOG4J2-406 at 9/19/13 6:15 PM:

[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.

2013-09-19 Thread Kerrigan Joseph (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13772132#comment-13772132 ] Kerrigan Joseph edited comment on LOG4J2-406 at 9/19/13 6:15 PM:

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

2013-09-19 Thread Kerrigan Joseph (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kerrigan Joseph updated LOG4J2-406: --- Attachment: PermGen.zip A sample netbeans project illustrating the issue

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

2013-09-19 Thread Kerrigan Joseph (JIRA)
Kerrigan Joseph created LOG4J2-406: -- Summary: JMX MBeans are not being unregistered when a tomcat web application that uses log4j is undeployed, leading to a permgen memory leak. Key: LOG4J2-406 URL:

[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.

2013-09-19 Thread Remko Popma (JIRA)
[ 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

Re: [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.

2013-09-19 Thread Nick Williams
Thanks, Remko. Team: should this method Remko added be called automatically from LoggerContext#stop()? N On Sep 19, 2013, at 6:51 PM, Remko Popma (JIRA) wrote: [

Re: [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.

2013-09-19 Thread Ralph Goers
I need a chance to review this. I am uncomfortable with hardwiring this. Sent from my iPad On Sep 19, 2013, at 5:02 PM, Nick Williams nicho...@nicholaswilliams.net wrote: Thanks, Remko. Team: should this method Remko added be called automatically from LoggerContext#stop()? N On Sep