[jira] [Resolved] (ZOOKEEPER-1668) “Memory leak” about permgen

["Patrick Hunt (JIRA)" <ji...@apache.org>]

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

Patrick Hunt resolved ZOOKEEPER-1668.
-------------------------------------

    Resolution: Not A Problem

> “Memory leak” about permgen
> ---------------------------
>
>                 Key: ZOOKEEPER-1668
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1668
>             Project: ZooKeeper
>          Issue Type: Improvement
>          Components: jmx, server
>    Affects Versions: 3.3.5
>            Reporter: tokoot
>
> For each connection, a ConnectionBean will be created to represent this connection at finishSessionInit:
>   | ... 
>   | jmxConnectionBean = new ConnectionBean(this, zk);
>   | MBeanRegistry.getInstance().register(jmxConnectionBean, zk.jmxServerBean);
>   || ...
>   || ObjectName oname = makeObjectName(path, bean);
>   ||| ...
>   |||  return new ObjectName(beanName.toString());
>   |||| ...
>   |||| _canonicalName = (new String(canonical_chars, 0, prop_index)).intern();
> So, for every connection, it takes dozens of bytes at permgen. With connection established constantly, the usage of permgen will increase continuously.
> Is it reasonable or necessary to manage each connection with ConnectionBean?



--
This message was sent by Atlassian JIRA
(v6.1#6144)