its
entire lifetime.
We're also looking at fixing the thread leak issue in the native library.
Thanks for the responses.
cheers
jesse c
--
>>>>>>>>>> Read the docs: http://akka.io/docs/
>>>>>>>>>> Check the FAQ:
>>&g
the 600 threads do not show up in JStack. JStack shows the expected number
of threads. However, looking in the 'task' folder for the process in the
'/proc' directory shows all 600 or so, which is why this feels like some
sort of leak. The thread is being cleaned up in Java, but not at the OS
stem that is actually spawning new threads. Which would seem
to indicate to me that this the most likely source of the thread leak. And
that number after the thread, which I'm pretty sure is basically a running
count of the total number of threads that have been made in the process,
keeps go
