It is not unreasonable to want to enumerate and find all the objects that can consume system resources-
be it threads, IO, or any GUI/screen hardware( certainly on Windoze I've had a problem figuring out who
is taking all my GDI objects for example).
On J2Se, there is a concept of a ThreadGroup, but some of the "obvious" features have been deprecated in any case,
http://java.sun.com/j2se/1.5.0/docs/api/java/lang/ThreadGroup.html
The threads you start yourself you need to track. There are only two ways to create threads- Thread ctor and subclasses.
You should be able to grep your code for threads and store your objects in a vector or other container for later interrogation.
I suppose you could be launching other people's code ( system or library things ) that create private threads but you can probably
find a short list of suspects if this is the case.
So far in the one app I have, I have many places where I launch threads and haven't run into a limit on the 7130. When you write your own, you end up with something like
void run ()
{
while ( something)
{
}
}
You need to make sure that "something" has a finite lifetime and that no one in the loop can hang- IO, wait, sleep can hang unless
aborted. Adding an abort flag in "something" helps too. If you see my other post, things like "synchronized" can hang and you need to check for things like deadlock ( do you have synchronized everwhere just to be safe? Brain surgery doesn't become safe just because you do it real slow, LOL).
