OutOfMemory exception caused by RMIMarshaller
Brought to you by:
simonebordet,
tibu
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.