[RESOLVED] Forcing a class to "die" ?

Here's the problem - I have a plugin loading mechanism that dynamically loads classes like this:

- Define a variable as the class
- put the variable in an arraylist

The problem now is that when I attempt to unload such a plugin using .remove() with the arraylist, the class instance is still there. I noticed this when one of the plugins (a basic HTTPd) was still listening on a port when it should have been unloaded.

I've already tried using
System.runFinalization();
System.gc();

Thanks for any help!

This is one of two problems:-

1- There still is a dependancy using the object
2- The finalize() method in the class is manipulated so you can never erase the object while your program is still running

Quote:

---

Originally Posted by MalcolmCarmen

I've already tried using
System.runFinalization();
System.gc();

---

Rumors have it that you should call System.gc() twice. Have a go at it and see if it really works.

It is said that the first call marks the class loader and the second cleans it up. Not sure if it's true or if it will even work, but it's worth a try.


Oh, and I don't think you can unload something that's in use ;) See if you can stop it somehow first.

Quote:

---

Originally Posted by System_Error

Rumors have it that you should call System.gc() twice. Have a go at it and see if it really works.

It is said that the first call marks the class loader and the second cleans it up. Not sure if it's true or if it will even work, but it's worth a try.


Oh, and I don't think you can unload something that's in use ;) See if you can stop it somehow first.

---

As far as I know, This problem was fixed in 1.4

I'm not sure of any details about it, or even if it's true. Would be nice to know if it's true, but if the classes are still running then it won't matter. He somehow needs to stop them from running.

It appears my solution is to just load these classes as threads - not only does it speed up execution of my app, but it allows me to at least kill the instances easier. This app is large enough that tracking down object references left over would be a very unfun task!

Quote:

---

Originally Posted by MalcolmCarmen

It appears my solution is to just load these classes as threads - not only does it speed up execution of my app, but it allows me to at least kill the instances easier. This app is large enough that tracking down object references left over would be a very unfun task!

---

You didn't say your classes are already compiled and runnable.

Killing threads is a bad idea.

Just create an interface that all these classes have to implement. Give it a method shutdown() that requires the plug-in to completely shut down all its activity.

Quote:

---

Originally Posted by CornedBee

Killing threads is a bad idea.

Just create an interface that all these classes have to implement. Give it a method shutdown() that requires the plug-in to completely shut down all its activity.

---

He didn't create the classes as I guess (Doesn't have the source)

After playing with threads a lot, I've resigned to using CornedBee's suggestion - the classes is still instanced somewhere in the VM, but it isn't bothering me anymore!