Thanks Filip for response. The OOM Error is not that relevant as is the no of threads that keeps increasing with the no of messages sent to the queue. Most of the threads are in Net I/O or waiting state.
Any idea what we could be doing wrong? Thank you, Mandira Filip Hanik - Dev Lists wrote: > > mandira wrote: >> We are using ActiveMQ for parallel processing - Some of parallelism >> achieved >> through JMS Listeners and some through multiple threads. >> >> While running the application after some time - we were always getting >> "Out >> of Memory" Error >> > yeah, but what kind of OOME? there are many types > > Filp >> On profiling we notice a high number of threads being spawned and the no >> of >> instances only increasing with time. >> >> We commented the code to "send" the message to queue and the thread count >> became kind of steady. On further reading we discovered it is by design >> as >> the transport is async as explained in this URL - >> http://open.iona.com/wiki/display/ProdInfo/Understanding+the+Threads+Allocated+in+ActiveMQ >> http://open.iona.com/wiki/display/ProdInfo/Understanding+the+Threads+Allocated+in+ActiveMQ >> >> >> But this only works for vm protocol. The broker, in our case, would be >> running as a separate instance. What is the best option to reduce the no >> of >> threads. >> >> We tried versions 5 and 5.1 >> thank you, >> Mandira >> > > > -- View this message in context: http://www.nabble.com/Multiple-threads-for-ActiveMQ-Connection-tp17328318s2354p17348259.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
