With a normal disconnect from a java client those reader threads should disappear. With an abnormal disconnect, where the socket is not fully closed, it can take some time (os tcp config dependent) for the broker to identify the connection as closed.
What does netstat tell you about the active connections to the brokers listen port. Are there a bunch of sockets in timed wait state? 2010/1/12 marcin80 <mtros...@gmail.com> > > Hi, > > I'm using ActiveMQ 5.2 and I've noticed thad ActiveMQ create new thread for > every connection but even the client will disconnect its thread still alive > (state RUNNABLE). It is ActiveMQ normal behavior? > Can I change this? I would like to finalize thread if client will > dissconnect. > > Cheers, > Marcin > -- > View this message in context: > http://old.nabble.com/Thread-for-each-client-tp27126558p27126558.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > > -- http://blog.garytully.com Open Source Integration http://fusesource.com
