Thanks, that is a helpful link. FWIW, I've managed to sweep my issues
under the carpet for the moment by reducing the stack size of a thread
via ulimit... now my test program can have thousands of threads without
issue.
Timothy Bish wrote:
I think you may want to go read Sun's JMS tutorial
ht
I think you may want to go read Sun's JMS tutorial
http://java.sun.com/products/jms/tutorial/
Every session as per the JMS spec has its own thread, but every session
can have multiple consumers listening to different destinations. So
there should be no need to create 300 sessions. Just create
I don't know if it applies to your problem but you could setup a Camel
routing on the broker so that the 10'000 queues are forwarded into a
few, so that each client would only have to listen to 10 or so queues
(like one per broker).
Mario
On 2/19/08, Ben Chobot <[EMAIL PROTECTED]> wrote:
> Hey ev
Hey everybody. I'm playing around with the CMS client for ActiveMQ 5,
and I'm having some threading issues. It seems that every time I start a
session, I get a new thread to handle that session. Clearly, this won't
scale to lots of sessions, and in fact my OS won't let me create more
than 300 t
