with only
activemq related threads in them. It would appear that these threads
aren't quiting when they receive the interrupt exception :(
Xavier Toth wrote:
On further inspection I see that there are a number of threads started
on behalf of ActiveMQ and I'm wondering if and how these ever get
org.jcdx.jwss.ws.ChannelThread.visit(ChannelThread.java:76)
thread pool-4-thread-1 Thread[pool-4-thread-1,5,jcdxws1.1174684587669]
)
On 3/23/07, Xavier Toth [EMAIL PROTECTED] wrote:
For instance the run method in TcpTransport doesn't check for
isInterrupted on the thead. I tried added it myself but I
for these to work on another system). The run
script will generate a hprof dump on exit (Ctrl-C) that can be
inspected with 'hat'.
On 3/20/07, Xavier Toth [EMAIL PROTECTED] wrote:
I'm using Spring, Lingo and ActiveMQ. My processes routinely create
new queues use them for awhile and then hopefully
I'm using Spring, Lingo and ActiveMQ. My processes routinely create
new queues use them for awhile and then hopefully destroy them. But
it's the last part that's got me concerned. I close the Spring context
from which were created beans of class ActiveMQConnectionFactory,
ActiveMQQueue,
