Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <28c3c9290802191236x2ef82b86tce2d115d3db93e67@mail.gmail.com>
Date: Tue, 19 Feb 2008 21:36:30 +0100
From: "Mario Siegenthaler" <msiegenthaler@inventsoft.ch>
To: users@activemq.apache.org
Subject: Re: Thread pooling in ActiveMQ 5 cms
In-Reply-To: <47BB3B26.4050507@vigilos.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <47BB3B26.4050507@vigilos.com>

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 <bchobot@vigilos.com> 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?)
>