[ mx4j-Bugs-985335 ] HTTP Adaptor classes are not garbage collected.

Bugs item #985335, was opened at 2004-07-05 14:02
Message generated for change (Comment added) made by biorn_steedom
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=450647&aid=985335&group_id=47745

Category: HTTP Adaptor
Group: Release 2.0.1
Status: Open
Resolution: None
Priority: 5
Submitted By: Trustin Lee (anoripi)
Assigned to: Nobody/Anonymous (nobody)
Summary: HTTP Adaptor classes are not garbage collected.

Initial Comment:
I made a small JMX microkernel which provides dynamic 
class reloading feature.

I registered HTTPAdaptor MBean and unregistered it, 
and then created a new class loader and registered it 
again, ...., and then I gets OutOfMemoryError.

At first, I thought it is my classloader's problem, but it 
seems to be working very fine with other MBean JARs.

I ran MX4J with debugger, and some WeakHashMap is 
holding already unregistered MBeans' classes.  I think 
HTTPAdaptor MBean has some coupling with MX4J core.

Any ideas?


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

>Comment By: Simone Bordet (biorn_steedom)
Date: 2004-07-05 15:29

Message:
Logged In: YES 
user_id=128193

The HTTPAdaptor can be run inside JMXRI, so there is no
coupling with MX4J core.

Can you be more precise when you say that "some WeakHashMap
is holding already unregistered MBeans' classes" ?
Where in the MX4J code ?

Thanks

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

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


-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com