One other note, this happens whether I use HyperSQL or MySQL for JMS persistence.
This is the new scheduled delivery processing.
It instatiates an object of SimpleTimer per subscription
which extends java.lang.Thread
The thread isn't actually running so it is state "Unknown".
The JVM just counts the number of java.lang.Thread
objects rather than the real system threads.
Thanks for pointing me at this code. It is crying out
for a ThreadPool.
Ok. Phew! I thought there might be some massive thread leak and I was starting to get nervous. Do these threads ever start? It also appears that the objects never get cleaned up, even after the connection has closed.
They are not part of the connection, they are part of the
They do start if you schedule a message for delivery.
Which is why I said it should use a thread pool
with one thread waking up when the next delivery is
Hi, I am having the same problem with Jboss 4.0.1, the msg is sent to the Queue, the msg is executed, but It create some kind of thread zombies even if the msg is processed with success.
And the threads never desapear until we reboot the server.
What should I do?