[logback-dev] [JIRA] Commented: (LBCLASSIC-33) unregistering in the jmx plugin

Joern Huxhorn (JIRA) noreply-jira at qos.ch
Tue Nov 11 15:24:21 CET 2008

    [ http://jira.qos.ch/browse/LBCLASSIC-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10893#action_10893 ] 

Joern Huxhorn commented on LBCLASSIC-33:

For the record:

I was using

java version "1.6.0_10"
Java(TM) SE Runtime Environment (build 1.6.0_10-b33)
Java HotSpot(TM) Client VM (build 11.0-b15, mixed mode, sharing)

with tomcat 6.0.18
running on Win XP.

> 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 mailing list