james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Phillip Odam (JIRA)" <server-...@james.apache.org>
Subject [jira] [Updated] (JAMES-1534) JMX connections not being closed
Date Fri, 27 Dec 2013 20:53:51 GMT

     [ https://issues.apache.org/jira/browse/JAMES-1534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Phillip Odam updated JAMES-1534:

    Attachment: dangling-jmx-connections.patch

> JMX connections not being closed
> --------------------------------
>                 Key: JAMES-1534
>                 URL: https://issues.apache.org/jira/browse/JAMES-1534
>             Project: James Server
>          Issue Type: Bug
>          Components: CLI
>    Affects Versions: Trunk
>         Environment: Linux
>            Reporter: Phillip Odam
>              Labels: easyfix
>         Attachments: dangling-jmx-connections.patch
>   Original Estimate: 1h
>  Remaining Estimate: 1h
> The JmxServerProbe class doesn't offer any way to close the JMX connection. This doesn't
present itself as a problem in how Apache JAMES code uses this class. However in the case
where long running apps use this class, out of memory errors can occur since objects aren't
GC'd due to the dangling connection.
> To address this I'd suggest making the following changes
>  - have the interface ServerProbe extend java.io.Closeable class
>  - make locally declared JMXConnector jmxc variable (in JmxServerProbe's connect method)
to be a private member
>  - make the private member MBeanServerConnection mbeanServerConn be local to the connect
method (clean up)
>  - implement close method in JmxServerProbe class that calls JMXConnector's close method

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org

View raw message