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/
