activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From marcin80 <mtros...@gmail.com>
Subject Re: Thread for each client
Date Tue, 12 Jan 2010 12:54:11 GMT

Hi,

Thanks for your replay.
Netstat returns following (for 61616 port):

C:\>netstat -an | find "61616"
  TCP    127.0.0.1:1975         127.0.0.1:61616        ESTABLISHED
  TCP    127.0.0.1:1979         127.0.0.1:61616        ESTABLISHED
  TCP    127.0.0.1:1980         127.0.0.1:61616        ESTABLISHED
  TCP    127.0.0.1:2037         127.0.0.1:61616        ESTABLISHED
  TCP    127.0.0.1:2038         127.0.0.1:61616        ESTABLISHED
  TCP    127.0.0.1:2039         127.0.0.1:61616        ESTABLISHED
  TCP    127.0.0.1:2040         127.0.0.1:61616        ESTABLISHED
  TCP    127.0.0.1:2041         127.0.0.1:61616        ESTABLISHED
  TCP    127.0.0.1:2042         127.0.0.1:61616        ESTABLISHED
  TCP    127.0.0.1:2043         127.0.0.1:61616        ESTABLISHED
  TCP    127.0.0.1:2044         127.0.0.1:61616        ESTABLISHED
  TCP    127.0.0.1:61616        0.0.0.0:0              LISTENING
  TCP    127.0.0.1:61616        127.0.0.1:1975         ESTABLISHED
  TCP    127.0.0.1:61616        127.0.0.1:1979         ESTABLISHED
  TCP    127.0.0.1:61616        127.0.0.1:1980         ESTABLISHED
  TCP    127.0.0.1:61616        127.0.0.1:2037         ESTABLISHED
  TCP    127.0.0.1:61616        127.0.0.1:2038         ESTABLISHED
  TCP    127.0.0.1:61616        127.0.0.1:2039         ESTABLISHED
  TCP    127.0.0.1:61616        127.0.0.1:2040         ESTABLISHED
  TCP    127.0.0.1:61616        127.0.0.1:2041         ESTABLISHED
  TCP    127.0.0.1:61616        127.0.0.1:2042         ESTABLISHED
  TCP    127.0.0.1:61616        127.0.0.1:2043         ESTABLISHED
  TCP    127.0.0.1:61616        127.0.0.1:2044         ESTABLISHED

Cheers,
Marcin



Gary Tully wrote:
> 
> 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 <mtroscia@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
> 
> 

-- 
View this message in context: http://old.nabble.com/Thread-for-each-client-tp27126558p27127125.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.


Mime
View raw message