[logback-dev] [JIRA] Commented: (LBCLASSIC-33) unregistering in the jmx plugin
Ceki Gulcu (JIRA)
noreply-jira at qos.ch
Thu Nov 6 18:30:21 CET 2008
[ http://jira.qos.ch/browse/LBCLASSIC-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10885#action_10885 ]
Ceki Gulcu commented on LBCLASSIC-33:
With revision 1945, whenever the LoggerContext is reset, any associated JMXConfigurator instances are unregistered from the MBeanServer.
However, applying the techniques outlined in Frank Kieviet's blog (Thanks Joern), I don't seem to be able to have JMXConfigurator garbage collected when the web-app is stopped. (However, when the web-application is stopped and restarted, there is no accrual of LoggerCcontext objects. I am still investigating the issue and will keep you posted.
> 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: Ceki Gulcu
> 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