What is the stack trace of Thread-123?
I looked for this and came across what could be the problem. The MDB's that handle communication in the app spawn threads for specific actions. These are the threads not getting cleaned up.
Specifically, an MDB spawns a java process (extends Thread) which after doing some stuff spawns an action (which also extends Thread). This last thread calls some CMP beans. The beans are cleaned up fine, the first thread is too, but the second one is not.
I'm thinking that I'm going to try turning these threads (which might be somehow outside the jboss domain) into Session Beans. I'll let you know if this cleans up the process.
Thanks for the quick reply.
Ok, I redid the Threads to make them Sessions, and we're making progress. However, I have a server on the front of the application that needs to spawn a new thread for each incoming socket. This one was still giving me a problem (not cleaning up) after it exited its run method.
So, I changed it to implement Runnable instead. Still not cleaning up.
Finally, I set the bloody thing to null after taking it out of the hashtable that was storing it.
That seems to do the trick. So I'm going to run with that ;)
Wanted to post this in case you guys are looking at Threads spawned inside the jboss server in the future. I still don't really understand why it fails and works when it does.