[prev in list] [next in list] [prev in thread] [next in thread] 

List:       activemq-users
Subject:    Re: can we combine message groups and jms selectors
From:       Daniel Guggi <daniel.guggi () gmail ! com>
Date:       2013-03-27 19:55:28
Message-ID: CACq79Tp_4=0Q8uL3Xx5Fo5Zzk1eHTPwajP=ZfrsOMnd4b50-wg () mail ! gmail ! com
[Download RAW message or body]


thanks for clarification!

On Wed, Mar 27, 2013 at 3:15 PM, Yin Wang <suonayi@gmail.com> wrote:

> Yes, you can assume that works.
> It seems you want your message flow to be split into two message flows, one
> for
> the lower priority messages while the other for the higher priority
> messages
> and you want they are stuck on two 'exclusive' consumers respectively.
>
> For the sparse selector In one word , the current architecture of amq is
> not
> good at handling dispatching messages to the consumer with a sparse
> selector.
> There are many discussions about this limit and the following is
> the representative one,
> https://issues.apache.org/jira/browse/AMQ-221
>
> SuoNayi
>
>
> 2013/3/27 Daniel Guggi <daniel.guggi@gmail.com>
>
> > thank your for your info.
> >
> > would i work in theory for my case  (because i ensure that all messages
> > with same JMSXGroupID will have same Priority) or would it work generally
> > (even when messages with same JMSXGroupID have different priorities -
> dont
> > know if that really makes sense tough...)?
> >
> > yes, we also consider using two queues instead of one queue with
> > selectors...
> >
> > Can u please explain whay consumers my get stuck with sparse selector?
> >
> > tia,
> > daniel
> >
> >
> > On Wed, Mar 27, 2013 at 2:59 AM, SuoNayi <suonayi2006@163.com> wrote:
> >
> > > seems work in theory.
> > > Why not using two queues to send the different messages?
> > > It's more easy for problem diagnosis if some trouble is present.
> > > Besides, Do not use sparse selector or your consumers may get stuck.
> > >
> > >
> > >
> > >
> > > At 2013-03-26 22:58:29,"Daniel Guggi" <daniel.guggi@gmail.com> wrote:
> > > >hi,
> > > >
> > > >im curious if it is possible to use message-groups and jms selectors
> > > >together.
> > > >
> > > >example:
> > > >
> > > >i have consumer 'normalPriorityConsumer' for queue "X" with selector
> > > >'JMSProperty >= 4'
> > > >i have consumer 'lowPrioritiyConsumer' for queue "X" with selector
> > > >'JMSProperty < 4'
> > > >
> > > >all messages send to queue "X" will have the JMSXGroupID header set.
> > > >
> > > >would activemq be capable of sending to the appropriate consumer based
> > on
> > > >the priority?
> > > >
> > > >in my scenario this might work, because we ensure that for a given
> > > >jmsxGroupID the priority is always the same for all messages...
> > > >
> > > >ty,
> > > >daniel
> > >
> >
>


[prev in list] [next in list] [prev in thread] [next in thread]