NEW FINDING!!!!!
if you set this policy - queue messages are not distributed on a network:
<policyEntry queue=">">
<dispatchPolicy>
<strictOrderDispatchPolicy/>
</dispatchPolicy>
</policyEntry>
Is it a bug?
- C.
cbu wrote:
>
> Try both:
> - publishing 1000 messages on queues and would like to see some consumed
> on client's attached to remote brokers as well (did read the thing about
> preferring the fastest consumer ...)
> - publishing 1000 messages on topic and WANT DEFINITLY to see some
> consumed on client's attached to remote brokers as well (did read the
> thing about preferring the fastest consumer ...)
>
> -- C.
>
>
> Adrian Co wrote:
>>
>> Are you using queues or topics?
>>
>> Are you consuming from all brokers simultaneously? ActiveMQ tends to
>> give preference to local consumers I think.
>>
>> cbu wrote:
>>> Hello,
>>>
>>> I think I've read that quite a few people did have problems to setup a
>>> network of brokers where you can publish on publishing on broker x but
>>> consume the message on broker 1...n.
>>>
>>> As an example:
>>> - publish on broker 2 a message on a topic
>>> - consume the message from broker 1-9
>>>
>>> As additional information:
>>> - I setup such a broker network.
>>> - I can see in the log files the brokers connecting to each other
>>> - I can see in the log file connecting the clients to the assigned
>>> brokers
>>> - I did set on the network connector the prefech=1, dynamiconly=false,
>>> networkTTL=99, bridgeTempDestinations=true, failover=true
>>>
>>> STILL: I can reveice the message JUST on the broker I published the
>>> message.
>>>
>>> Any hint ...
>>>
>>> -- Chris
>>>
>>>
>>
>>
>>
>
>
--
View this message in context:
http://www.nabble.com/Network-of-Brokers---publishing-on-broker-x---consuming-on-broker-1...n-tf3041583.html#a8455211
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
