On 8/8/06, Anders Bengtsson <[EMAIL PROTECTED]> wrote:
James.Strachan wrote: > > >> The brokers will create points of failure on the way to the consumers in >> B, >> so I'll need redundant brokers. How would I configure multiple redundant >> brokers in both networks, but still minimizing the number of messages >> between A and B? > > Just run 2 brokers on each side of the slow link so that things will > failover if one of the dies? > Yes, that's what we tried. We ran into issues with the brokers not re-starting as they should, which I've now reported as AMQ-870. On a related issue, should AMQ detect message loops? Some documentation says that it does, by keeping a list of all visited brokers in each message,
Yes it does.
while other documentation (for network TTL) warns about the risk of loops with a high network TTL. We experienced a few message loops when trying out some more complex broker network topologies.
If you can create a test case that can reproduce a loop it'd be most helpful. -- James ------- http://radio.weblogs.com/0112098/
