activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mario Siegenthaler" <>
Subject Re: Thread pooling in ActiveMQ 5 cms
Date Tue, 19 Feb 2008 20:36:30 GMT
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).


On 2/19/08, Ben Chobot <> wrote:
> 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 threads. I'm wondering if there's any way to get around this?
> Can a single session asynchronously listen to more than one destination?
> Even better, it looks like the CMS client has code for thread pools in
> it, but C++ isn't my strong suite and it's not clear to me how I would
> use it....
> Any suggestions?
> (As an aside, we're trying to figure out how reasonable it will be to
> have a single client listen to 10,000 mostly-inactive queues, probably
> mostly on separate brokers. Is that just flat-out not going to happen?)

View raw message