Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (athena.apache.org: domain of christian.posta@gmail.com
 designates 209.85.217.171 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1404990051716-4683066.post@n4.nabble.com>
References: <1404990051716-4683066.post@n4.nabble.com>
Date: Thu, 10 Jul 2014 07:14:34 -0700
Message-ID: 
 <CAKS7T5Moh+OXSNVhBipfi6_2qkLShbqc97jcNSr14xOyFkv5wA@mail.gmail.com>
Subject: Re: Activating consumer for each message groups
From: Christian Posta <christian.posta@gmail.com>
To: "users@activemq.apache.org" <users@activemq.apache.org>
Content-Type: multipart/alternative; boundary=089e01161ab2bcf44204fdd7715e

--089e01161ab2bcf44204fdd7715e
Content-Type: text/plain; charset=UTF-8

Can you verify (JMX) that your consumer (are you using Camel? or straight
DMLC from spring?) is actually creating the requisite number of consumers
you're expecting?


On Thu, Jul 10, 2014 at 4:00 AM, UcayaliFish <ucayalyfish@gmail.com> wrote:

> Hi,
> I need some advice with message groups and I've failed to find a solution
> in
> the net.
> What I'm doing is accepting RTP audio from several sources and converting
> each RTP frame to JMS BytesMessage and sending it to ActiveMQ queue setting
> JMSXGroupID property according to audio origin. I use Spring
> MessageListenerContainer and MessageListener at the consumer side. I set
> concurrentConsumers of the container to the supposed number of audio
> sources. I expected that a separate consumer would be created/used for each
> message group thus allowing to accumulate the audio data into larger
> chunks,
> process it and send further. Internal structure required for processing
> would be bound to MessageListener instance.
> Unfortunately, the container starts a single consumer that receives all
> messages from all groups. I.e. the promise is kept - all messages in a
> group
> arrive to the same consumer instance. Actually, I just implement direct
> mapping of incoming messages with the same JMSXGroupID to a separate
> internal processor (through vm: queues) in a single MessageListener and it
> works as expected. It just consumes quite a lot of CPU/memory and I'm not
> sure it is an optimal solution whatsoever.
> I'm afraid that there is a misunderstanding from my part. Is it a viable
> idea to implement this kind of message routing with message groups? What
> would community suggest for this type of problem?
>
> TIA
>
> Sergey
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Activating-consumer-for-each-message-groups-tp4683066.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>


-- 
*Christian Posta*
http://www.christianposta.com/blog
http://fabric8.io
twitter: @christianposta

--089e01161ab2bcf44204fdd7715e--