Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Message-ID: <1826031396.1127059734410.JavaMail.jira@ajax.apache.org>
Date: Sun, 18 Sep 2005 18:08:54 +0200 (CEST)
From: "Kevan Miller (JIRA)" <dev@geronimo.apache.org>
To: dev@geronimo.apache.org
Subject: [jira] Commented: (GERONIMO-983) Memory used by proxies isn't
 released by dereferencing the proxy (I speculate)
In-Reply-To: <1616327462.1126156650592.JavaMail.jira@ajax.apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

    [ http://issues.apache.org/jira/browse/GERONIMO-983?page=comments#action_12329687 ] 

Kevan Miller commented on GERONIMO-983:
---------------------------------------

I certainly didn't intend to imply that GC'able proxies wasn't a good thing (although I can't vouch for it, yet, either). I'd just be hesitant to make that kind of change to the kernel at this point of time. 

Another option (with similar behavior to Gianny's proposal) is to use a map with WeakReferences -- Jakarta Commons Collections has a ReferenceIdentityMap (http://jakarta.apache.org/commons/collections/apidocs-COLLECTIONS_3_1/org/apache/commons/collections/map/ReferenceIdentityMap.html) which should fill the bill.

In either case, I have not yet convinced myself that either proposal works (or doesn't work). I note that Gianny has maintained the destroyProxy method. Is that to ease migration? Or are there instances where destroyProxy() must be invoked?

> Memory used by proxies isn't released by dereferencing the proxy (I speculate)
> ------------------------------------------------------------------------------
>
>          Key: GERONIMO-983
>          URL: http://issues.apache.org/jira/browse/GERONIMO-983
>      Project: Geronimo
>         Type: Bug
>   Components: console, kernel
>     Versions: 1.0-M5
>     Reporter: Aaron Mulder
>     Priority: Critical
>      Fix For: 1.0-M5
>  Attachments: ConsoleFix.txt, basicProxyManager.patch
>
> On Wed, 7 Sep 2005, Neal Sanche wrote:
> > I compiled up a new Geronimo, and then I left it running with the Server 
> > Info page displayed so I could see the cool AJX work there... and then I 
> > forgot about it for a day or so. When I got back it was saying:
> > 
> > 20:56:53,219 WARN  [ThreadedServer] EXCEPTION
> > java.lang.OutOfMemoryError: Java heap space                                     
> On Wed, 7 Sep 2005, Neal Sanche wrote:
> > Well, I did some profiling, and found that the predominant object that 
> > was being retained was:
> > 
> > org.apache.geronimo.kernel.basic.RawGetAttributeInvoker
> > 
> > There are also another slowly growing group of geronimo classes that
> > seem to pile up, and they aren't getting garbage collected either:
> > 
> > org.apache.geronimo.kernel.basic.ProxyMethodInterceptor and many 
> > internal classes of this class.
> The console uses lots of proxies and doesn't manually close them, just releases the references.  Seems like this leaks memory.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira