Hi moreno,
can you take a stack trace of the broker ? - the threads should be
getting garbage collected
thanks,
Rob
On 19 Jan 2010, at 10:37, moreno9000 wrote:
I confirm Marcin's problem (with AMQ 5.3).
One producer (java application with transport=openwire)
For each message producer open a Connection, send a msg, close the
Connection.
Server side no problem for what concern file descriptors opened,
memory usage, socket opened (with netstat I see all conn=ESTABLISHED).
Problems with threads.
A new thread is created (inside AMQ) for every producer's open-send-
close.
Threads don't disappear even if producer call connection.close()
(they disappear after 20-30 seconds from producer's death).
In activemq.xml I set producerFlowControl=false,
transport.closeAsync=false.
AMQ run with these options:
-Xmx1024M, -Dorg.apache.activemq.UseDedicatedTaskRunner=false.
Producer set jms.useAsyncSend=false.
Are there other configurations I can try to stop thread's increment?
Many thanks
Moreno
marcin80 wrote:
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-tp27126558p27223897.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Rob Davies
http://twitter.com/rajdavies
I work here: http://fusesource.com
My Blog: http://rajdavies.blogspot.com/
I'm writing this: http://www.manning.com/snyder/
