> Sir/madam
>
> What is thread leak?
Thread leak is when application does not close threads properly. Threads
do not exit and the number of unused threads grow with time.
> How can I trace where the application has thread leak?
If you have thread leak then with time you'll get lots of unused
threads. Try to find out what kind of threads is leaking out (give
descriptive names, log entry/exit to/from run(), whatever). When you
find the class that is leaking out threads check how new threads are
instantiated and how they're closed. Is it quaranteed that the thread
will close properly regardless of what happens? No, it's not, otherwise
you wouldn't have leaks.
Regards,
Leonard

Signature
It is wrong always, everywhere, and for anyone, to believe anything
upon insufficient evidence.
-- William Kingdon Clifford
Roedy Green - 03 Nov 2007 19:34 GMT
On Tue, 30 Oct 2007 14:06:33 +0100, Leonard Milcin
<leonard@wytnij.milcin.pl> wrote, quoted or indirectly quoted someone
who said :
>Thread leak is when application does not close threads properly.
A leak implies a bug in the memory management system. When you don't
close a thread, there is no problem with memory management. It is
just you are not going to use it again. You potentially could, so it
is not a bug in the sense of memory leaks with C++.
I use the term "packratting" for holding onto something you did not
really need to. It can cause just as much trouble as a leak.

Signature
Roedy Green Canadian Mind Products
The Java Glossary
http://mindprod.com
On Tue, 30 Oct 2007 03:30:28 GMT, "timothy ma and constance lee"
<timcons1@shaw.ca> wrote, quoted or indirectly quoted someone who said
>What is thread leak?
see http://mindprod.com/jgloss/leak.html
http://mindprod.com/jgloss/packratting.html

Signature
Roedy Green Canadian Mind Products
The Java Glossary
http://mindprod.com