In your case you want to use OR though rather than AND :)
On 8/23/06, James Strachan <[EMAIL PROTECTED]> wrote:
I just meant you can replace
MD1 = true and MD2 = true
with just
MD1 and MD2
On 8/23/06, Venkatg <[EMAIL PROTECTED]> wrote:
>
> James,
>
> I didn't really followed your reply.
>
> >and MD3 topics which would be slower than
> using 1 message on 1 topic with selectors.
>
> >Generally speaking using more topics tends to be a little faster,
>
> What I am doing I have listed here
>
> on the publisher side if the any message belong to more that one
> Manangement Domain(MD) MD1 and MD2 then
>
> msg.setBooleanProperty("MD1", true);
> msg.setBooleanProperty("MD2", true);
>
> else if it belong to only MD1 then
> msg.setBooleanProperty("MD1", true);
>
>
> Let us say on the Consumer side if it is interested in both MD1 and MD2
> then the selector will be
> "MD1=TRUE OR MD2=TURE"
>
> for other case it will be MD1=TRUE
>
> Thanks a lot
>
> -Venkat
>
>
>
> James.Strachan wrote:
> >
> > Note a message can be on one topic only, so you'd have to send 3
> > messages to the MD1, MD2 and MD3 topics which would be slower than
> > using 1 message on 1 topic with selectors.
> >
> > Generally speaking using more topics tends to be a little faster, but
> > like all things in IT it completely depends exactly what you are
> > doing. If in doubt try both approaches and see which one works best
> > for you
> >
> >
> > On 8/23/06, Venkatg <[EMAIL PROTECTED]> wrote:
> >>
> >>
> >> Yes. I am creating boolean property at the publisher for each of the
> >> MD's.
> >> Then on the consumer side OR conditions are added to the selector. One
> >> more
> >> query,
> >> which of the approach is faster(better) using selector or having many
> >> topics(~65000)?
> >>
> >> -Venkat
> >>
> >> James.Strachan wrote:
> >> >
> >> > Actually for boolean properties you can just use the selector
> >> >
> >> > MD1 and MD2 and MD3
> >> >
> >> > On 8/23/06, Venkatg <[EMAIL PROTECTED]> wrote:
> >> >>
> >> >>
> >> >> Hi James,
> >> >>
> >> >> Thanks a lot. I can use boolean condition which solved the problem.
> >> >>
> >> >> -Venkat
> >> >>
> >> >>
> >> >> James.Strachan wrote:
> >> >> >
> >> >> > There's no limit on destinations though it does use up RAM on
> >> brokers.
> >> >> >
> >> >> > A work around for your problem is to use a header for each domain
> >> then
> >> >> > you can do something like
> >> >> >
> >> >> > MD1 = true and MD2 = true and MD3 = true
> >> >> >
> >> >> > etc
> >> >> >
> >> >> >
> >> >> > On 8/23/06, Venkatg <[EMAIL PROTECTED]> wrote:
> >> >> >>
> >> >> >> Hi All,
> >> >> >>
> >> >> >> In my application I started using selector and everything working
> >> >> fine.
> >> >> >> But during the developement I found that to set some specific
> >> filter
> >> >> >> selector is not enough.Here is my problem look at the selector
> >> string
> >> >> >> below
> >> >> >>
> >> >> >> MGMTID IN ('MD1','MD2', 'MD3')
> >> >> >>
> >> >> >> Here "MGMTID" is a string property which gets set on the server
> >> side
> >> >> when
> >> >> >> ever message is published. But when a node is participating in
> >> >> multiple
> >> >> >> admin domains for example node N1 in "MD1,MD2" then property
> >> "MGMTID"
> >> >> >> will
> >> >> >> have multiple values so "IN" condition will fail. To solve this
> >> >> problem
> >> >> >> we
> >> >> >> thought of using Wildcards
> >> >> >>
> >> >> >> MD1.*
> >> >> >> MD2.*
> >> >> >>
> >> >> >> But the problem(?) with this approach is we will end up in creating
> >> >> 65000
> >> >> >> topics both on publisher side and Consumer side. Are any know limit
> >> on
> >> >> >> the
> >> >> >> number of topics? If not any idea on memory requirement?
> >> >> >>
> >> >> >> Thanks
> >> >> >> Venkat
> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >> --
> >> >> >> View this message in context:
> >> >> >> http://www.nabble.com/Number-of-Topics-tf2151480.html#a5941433
> >> >> >> Sent from the ActiveMQ - User forum at Nabble.com.
> >> >> >>
> >> >> >>
> >> >> >
> >> >> >
> >> >> > --
> >> >> >
> >> >> > James
> >> >> > -------
> >> >> > http://radio.weblogs.com/0112098/
> >> >> >
> >> >> >
> >> >>
> >> >> --
> >> >> View this message in context:
> >> >> http://www.nabble.com/Number-of-Topics-tf2151480.html#a5943361
> >> >> Sent from the ActiveMQ - User forum at Nabble.com.
> >> >>
> >> >>
> >> >
> >> >
> >> > --
> >> >
> >> > James
> >> > -------
> >> > http://radio.weblogs.com/0112098/
> >> >
> >> >
> >>
> >> --
> >> View this message in context:
> >> http://www.nabble.com/Number-of-Topics-tf2151480.html#a5943604
> >> Sent from the ActiveMQ - User forum at Nabble.com.
> >>
> >>
> >
> >
> > --
> >
> > James
> > -------
> > http://radio.weblogs.com/0112098/
> >
> >
>
> --
> View this message in context:
http://www.nabble.com/Number-of-Topics-tf2151480.html#a5943946
> Sent from the ActiveMQ - User forum at Nabble.com.
>
>
--
James
-------
http://radio.weblogs.com/0112098/
--
James
-------
http://radio.weblogs.com/0112098/
