Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (nike.apache.org: domain of gary.tully@gmail.com designates
 209.85.218.215 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=eq3AgsqpInDpZZ/Rj/z4TMlpj5u1C8SoeZhaobKaPQJeydXKtAz8RJYtkQJCjxO98o
         jOg6McYVEe49jSmJNv9JCg6/6qTs0wxmyPfpYK1UZhC9k8a2b2g4vFJAnPOZdr+Lg65v
         dGlDy/d2+s4hxmSQKQxYPYKUMBZ8R4B6+2wDA=
MIME-Version: 1.0
In-Reply-To: <26337157.post@talk.nabble.com>
References: <26335357.post@talk.nabble.com>
	 <36e91d9d0911130420o5b969f5fj965dfaaa3cc524f6@mail.gmail.com>
	 <26336737.post@talk.nabble.com> <26337157.post@talk.nabble.com>
Date: Fri, 13 Nov 2009 15:46:13 +0000
Message-ID: <3a73c17c0911130746n5fad5bf3h7a223ae3ed722eb8@mail.gmail.com>
Subject: Re: network of brokers forward problem
From: Gary Tully <gary.tully@gmail.com>
To: users@activemq.apache.org
Content-Type: multipart/alternative; boundary=000325556f5a4366820478428f7c

--000325556f5a4366820478428f7c
Content-Type: text/plain; charset=ISO-8859-1

If strict order delivery is a requirement then this is true.
Otherwise, from a producer point of view, any broker in the network will
work so availability improves the more brokers you add.
yes, messages can be stuck for a period, but a consumer that randomly
connects to a broker in the network and assuming brokers eventually restart,
all messages will get consumed.
For example, if you add a third broker (broker3) and consumer from that,
when broker 2 restarts, messages can flow to broker 3 (just not back to
their origin atm) so they are available from two locations.

Having said all that, we do need to fix AMQ-2324.

2009/11/13 nehehe <hakon@teletopia.no>

>
> I found an answer to my own question :)
>
> https://issues.apache.org/activemq/browse/AMQ-2324
>
> What I am trying to do is not possible, at least not in version 5.3.0?
>
> If I understand correctly the network of brokers is not a solution for high
> availability as it could result in less reliable than just one broker.  It
> is designed more for high-traffic but low-availability scenarios.
>
>
> Regards,
> Haakon
>
>
>
> nehehe wrote:
> >
> > Hi,
> >
> > Thank you for the response.
> >
> > Wouldnt this just tweak it to behave a bit better for my exact test-case,
> > but not solve the problem?
> >
> > Is what I am trying to do, doable?
> >
> > Regards,
> > Haakon
> >
> >
> >
> >
> >
> >
> >
> > Dejan Bosanac wrote:
> >>
> >> Hi,
> >>
> >> try setting lower prefetch size to match your use case
> >> http://activemq.apache.org/what-is-the-prefetch-limit-for.html
> >>
> >> Cheers
> >> --
> >> Dejan Bosanac - http://twitter.com/dejanb
> >>
> >> Open Source Integration - http://fusesource.com/
> >> ActiveMQ in Action - http://www.manning.com/snyder/
> >> Blog - http://www.nighttale.net
> >>
> >>
> >> On Fri, Nov 13, 2009 at 12:43 PM, nehehe <hakon@teletopia.no> wrote:
> >>
> >>>
> >>> Hi,
> >>>
> >>> I'm trying to configure a network of brokers, and it works somewhat but
> >>> not
> >>> the way I expect.
> >>>
> >>> Two brokers A and B.
> >>>
> >>> 1000 messages are added to broker A
> >>> 10 messages are consumed from broker B, then disconnects (or plugged)
> >>>  (messages are transferred from A->B so thats good)
> >>> Client connects to broker A and try to consume messages.
> >>>
> >>> Now broker B has 990 messages, while the only consumer is connected to
> >>> A,
> >>> and nothing more happens
> >>>
> >>> My question, is this supposed to work as I expect?
> >>>
> >>>
> >>>
> >>> Im running activemq 5.3.0
> >>>
> >>> The configuration:
> >>>
> >>> transport is configured with keepAlive and soTimeout
> >>>
> >>> <networkConnector
> >>>  name="aaaa"
> >>>  dynamicOnly="true"
> >>>  networkTTL="10"
> >>>  conduitSubscriptions="false"
> >>>  uri="static://(tcp://192.168.20.12:61616)"
> >>> />
> >>>
> >>> Regards,
> >>> Haakon
> >>> --
> >>> View this message in context:
> >>>
> http://old.nabble.com/network-of-brokers-forward-problem-tp26335357p26335357.html
> >>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
> >>>
> >>>
> >>
> >>
> >> -----
> >> Dejan Bosanac
> >>
> >> Open Source Integration - http://fusesource.com/
> >> ActiveMQ in Action - http://www.manning.com/snyder/
> >> Blog - http://www.nighttale.net
> >>
> >
> >
>
> --
> View this message in context:
> http://old.nabble.com/network-of-brokers-forward-problem-tp26335357p26337157.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>


-- 
http://blog.garytully.com

Open Source Integration
http://fusesource.com

--000325556f5a4366820478428f7c--