Return-Path: Delivered-To: apmail-geronimo-activemq-users-archive@www.apache.org Received: (qmail 78177 invoked from network); 26 Oct 2006 06:51:50 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 26 Oct 2006 06:51:49 -0000 Received: (qmail 146 invoked by uid 500); 25 Oct 2006 14:40:32 -0000 Delivered-To: apmail-geronimo-activemq-users-archive@geronimo.apache.org Received: (qmail 131 invoked by uid 500); 25 Oct 2006 14:40:32 -0000 Mailing-List: contact activemq-users-help@geronimo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: activemq-users@geronimo.apache.org Delivered-To: mailing list activemq-users@geronimo.apache.org Received: (qmail 114 invoked by uid 99); 25 Oct 2006 14:40:32 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Oct 2006 07:40:32 -0700 X-ASF-Spam-Status: No, hits=2.5 required=10.0 tests=DNS_FROM_RFC_ABUSE,HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of chirino@gmail.com designates 64.233.184.236 as permitted sender) Received: from [64.233.184.236] (HELO wr-out-0506.google.com) (64.233.184.236) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Oct 2006 07:40:17 -0700 Received: by wr-out-0506.google.com with SMTP id 58so12147wri for ; Wed, 25 Oct 2006 07:39:56 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:references:x-google-sender-auth; b=ualvBVHamlk5FCJ4X3IODyyLJwj1nyc18Sz599D8K9I488XwVHO+j2SOTIJlCkKqyKa/fTq5BCu4viL8oAlfMFK6rLP9PSEHxnIpOXVLxIAIVEqpfXO5Pp1HYGiUf8yTO9hDeiz2aVBiUum3AUDOMpakohHWIPFdZGgYtFUVj2M= Received: by 10.78.203.13 with SMTP id a13mr921521hug; Wed, 25 Oct 2006 07:39:55 -0700 (PDT) Received: by 10.78.148.15 with HTTP; Wed, 25 Oct 2006 07:39:55 -0700 (PDT) Message-ID: Date: Wed, 25 Oct 2006 10:39:55 -0400 From: "Hiram Chirino" Sender: chirino@gmail.com To: activemq-users@geronimo.apache.org Subject: Re: Self configuring network of brokers In-Reply-To: <6988430.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_20246_6568697.1161787195241" References: <6895670.post@talk.nabble.com> <6988430.post@talk.nabble.com> X-Google-Sender-Auth: e72946a5e8509f9e X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_20246_6568697.1161787195241 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline change all the occurrences of "multicast://default" to "multicast://default?keepAliveInterval=100000" where the keepAliveInterval is how often to send a heartbeat out in ms. On 10/25/06, kristoffer wrote: > > > Hi, > > Ok. Because there were some log statements before doing each send, saying > somethin that my current broker has been added to the list of brokers? > > I browsed through the documentation but i could not find any information > on > how to change this heartbeat packets? > > regards, > -Kristoffer > > > Hiram Chirino wrote: > > > > On 10/19/06, kristoffer wrote: > >> > >> > >> Hi, > >> > >> Just got my client to connect to brokers using multicast properly, yea! > >> But > >> (comparing with a static tcp connection) performance is so much worse > >> when > >> using discovery:(multicast://default) at the client side. It looks like > >> (correct me if im wrong) every message sent from the client to the > >> broker, > >> causing a multicast discovery in order to find a broker. Why is this > > > > > > no. but the client is getting every broker heartbeat which defaults to > > about 1 every 500 ms. So if you have alot of brokers and a slow client > > connection that could be alot of traffic that the client is getting. > > > > behaviour? Is because of loadbalancing? Is there some way that the > > discovery > >> could be made only when the connection is broken? > >> > >> What i want is to have a loadbalanced system which is easy > configurable. > >> I > >> dont want to update all my traffic servers configuration with new tcp > >> urls > >> if I decide to add a new broker. At the same time i dont want any > >> overhead > >> of running multicast, except when a connection failure occurs. > > > > > > > > The overhead of multicast is only that each broker is sending out > > heartbeat > > messages. You can change the time interval to make that overhead be > much > > less. > > > > Please help me understand if this is feasible or not, if not, what are a > >> common setup? What are my options in terms of performance vs > >> ease-of-configuration? > >> > >> Thank you, > >> -Kristoffer > >> -- > >> View this message in context: > >> > http://www.nabble.com/Self-configuring-network-of-brokers-tf2473032.html#a6895670 > >> Sent from the ActiveMQ - User mailing list archive at Nabble.com. > >> > >> > > > > > > -- > > Regards, > > Hiram > > > > Blog: http://hiramchirino.com > > > > > > -- > View this message in context: > http://www.nabble.com/Self-configuring-network-of-brokers-tf2473032.html#a6988430 > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > > -- Regards, Hiram Blog: http://hiramchirino.com ------=_Part_20246_6568697.1161787195241--