[ mx4j-Bugs-1267353 ] OutOfMemory exception caused by RMIMarshaller

Bugs item #1267353, was opened at 2005-08-23 18:33
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=450647&aid=1267353&group_id=47745

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: Release 3.0.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Olivier Derveau (olivierderveau)
Assigned to: Nobody/Anonymous (nobody)
Summary: OutOfMemory exception caused by RMIMarshaller

Initial Comment:
RMIMarshaller creates ClassLoaders in the unmarshal method.
But theses classloaders are never garbage collected.
This leads to a JVM memory saturation and so an out of
memory exception... a caching (via a simple hash map) 
of the classloaders (I used a concatenation of the
mbeanLoader and defaultLoader class name as key to
identified the loaders...) solve this problem : the
number of class loader instances are limited.

This problem occured on Windows 2000 and JDK 1.4.2.

I can provide the test program that lead to this
exception if needed...
I used JDeveloper memory profiler to identify this
memory problem.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=450647&aid=1267353&group_id=47745


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf