[logback-dev] [JIRA] Commented: (LBCLASSIC-33) unregistering in the jmx plugin
Joern Huxhorn (JIRA)
noreply-jira at qos.ch
Tue Oct 28 17:27:21 CET 2008
[ http://jira.qos.ch/browse/LBCLASSIC-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10824#action_10824 ]
Joern Huxhorn commented on LBCLASSIC-33:
I just checked this with a simple hello-world-webapp using tomcat 6.0.18.
With <jmxConfigurator/> contained in logback.xml the classloader of the webapp will never be garbage-collected on re- or undeploy. All classes of the webapp remain in the heap dump.
If I remove <jmxConfigurator/> the webapp is unloaded properly.
This is quite bad...
> unregistering in the jmx plugin
> Key: LBCLASSIC-33
> URL: http://jira.qos.ch/browse/LBCLASSIC-33
> Project: logback-classic
> Issue Type: Bug
> Components: Other
> Affects Versions: unspecified
> Environment: Operating System: All
> Platform: All
> Reporter: Hontvári József
> Assignee: Logback dev list
> I started using the JMX plugin of login, and I wondered how should I
> shut it down when a web application is restarted. I haven't found a
> function which unregisters the Configurator MBean. This object holds a
> reference (through ContextAwareBase) to a Context. I am afraid that not
> unregistering it causes a memory leak when a web application is restarted.
> There should be a way to shutdown the JMX plugin. Or more generally an API to shut down the Logback system in its entirety: flush buffers, close files etc. It must be decided what to do if a log request arrives when or after logback is shutting down.
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the logback-dev