Return-Path: Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: (qmail 56475 invoked from network); 14 Nov 2007 20:09:09 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 14 Nov 2007 20:09:09 -0000 Received: (qmail 41618 invoked by uid 500); 14 Nov 2007 20:08:56 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 41592 invoked by uid 500); 14 Nov 2007 20:08:56 -0000 Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list dev@activemq.apache.org Received: (qmail 41583 invoked by uid 99); 14 Nov 2007 20:08:56 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 14 Nov 2007 12:08:56 -0800 X-ASF-Spam-Status: No, hits=0.2 required=10.0 tests=SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of chirino@gmail.com designates 209.85.146.183 as permitted sender) Received: from [209.85.146.183] (HELO wa-out-1112.google.com) (209.85.146.183) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 14 Nov 2007 20:08:44 +0000 Received: by wa-out-1112.google.com with SMTP id k22so329516waf for ; Wed, 14 Nov 2007 12:08:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; bh=inCWn8ORO9tIWknEgmvL67uwR+N/T1Q8f5XJF7wf7Bg=; b=HLxNc49NUdL7T69eXyYGtrS/kZUpiEu5tncrwJSBVXQhX/YGx9Z/POpuNtSSPHgAEdaIOXS7k18af13sDAxk0YiC8zB9TvkOH1vCt9TO8naHLT6zLbs7Kl+C4yo58l9OXOGNnO5ke5ZfqiRy2Nz2UsDT5dipmOrl63LEOJdwAG8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=p1U8ImMdGinIB371iOjy/i5ybrcFQWobkMUaClITBBWIc5nuf0UHl/w2EmgqFa/Q5Zed8raaclbcDXT25K/OnzOt+4F+b7R/JqN/JMD3mBmcBjPgK21oZvCV9I+IUo5dMoJ05E4zOP/1arD4SUHoyLWr6ZzgxlfANN2/LQ7eIu8= Received: by 10.114.160.1 with SMTP id i1mr514068wae.1195070917245; Wed, 14 Nov 2007 12:08:37 -0800 (PST) Received: by 10.115.23.20 with HTTP; Wed, 14 Nov 2007 12:08:37 -0800 (PST) Message-ID: Date: Wed, 14 Nov 2007 15:08:37 -0500 From: "Hiram Chirino" Sender: chirino@gmail.com To: dev@activemq.apache.org Subject: Re: Clarification Required: One message broker per machine or...? In-Reply-To: <13751450.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <13751450.post@talk.nabble.com> X-Google-Sender-Auth: 072a404eb03e7774 X-Virus-Checked: Checked by ClamAV on apache.org Normally you only use 1 broker unless you have network/load/saleability/high-availability issues to address. On Nov 14, 2007 11:55 AM, EyeOnCode wrote: > > > After reading AMQ's documents, I am still unclear on when a separate message > broker is required. The documentation should give diagrams of different > configuration possibilities to make more clear. > > I have a distributed application with 4 separate machines (separate boxes) > connected by network. Do I need to install a message broker on each > machine (box)? Is there a way to use only one message broker for 4 > separate machines? I am very unclear about this. > > -- > View this message in context: http://www.nabble.com/Clarification-Required%3A--One-message-broker-per-machine-or...--tf4806558s2354.html#a13751450 > Sent from the ActiveMQ - Dev mailing list archive at Nabble.com. > > -- Regards, Hiram Blog: http://hiramchirino.com Open Source SOA http://open.iona.com