Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 25708 invoked from network); 30 Oct 2008 16:03:03 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 30 Oct 2008 16:03:03 -0000 Received: (qmail 20040 invoked by uid 500); 30 Oct 2008 16:03:08 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 19649 invoked by uid 500); 30 Oct 2008 16:03:07 -0000 Mailing-List: contact users-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@activemq.apache.org Delivered-To: mailing list users@activemq.apache.org Received: (qmail 19638 invoked by uid 99); 30 Oct 2008 16:03:07 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 30 Oct 2008 09:03:07 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of bruce.snyder@gmail.com designates 74.125.46.157 as permitted sender) Received: from [74.125.46.157] (HELO yw-out-1718.google.com) (74.125.46.157) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 30 Oct 2008 16:01:49 +0000 Received: by yw-out-1718.google.com with SMTP id 6so242536ywa.86 for ; Thu, 30 Oct 2008 09:02:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=bGK4ee8OvqdAX/N0XRq+aL87gLTjkPlyCf5em8DsA3Y=; b=AmYnfen1BarLwIFxREuRN2ae5jmBhAV8FXg5HZjDTpkBWOCWBIEBWfQEA9HpOoYaL8 SpUUDt4r10uR4gK0yrAVe2VKaq3XUvGERXkOyZ8G9cgNewQg/tStetQ+va6lLlEifqPF mFti3FukSlSwoyUZNthRNslehNvagqPDCqNP0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=Iye89r8QLjZVSgy4GoCwsDFad0u67yV6ffPFzbVnxsi1jzhF+vi2oBGb1BPrZ6iuwm GMDYtvcQvGaDaiuvH6TSROFawBpOa8n5D/Jq/S0DmR9ynQZ82SXf1CMfzanI49Z3LsKH Re63GncPVURzD03gPvJjSj443M68enNd5/g4M= Received: by 10.100.128.2 with SMTP id a2mr936825and.158.1225382539799; Thu, 30 Oct 2008 09:02:19 -0700 (PDT) Received: by 10.100.44.19 with HTTP; Thu, 30 Oct 2008 09:02:19 -0700 (PDT) Message-ID: <7b3355cb0810300902q55532215ma5e450044a61e3e6@mail.gmail.com> Date: Thu, 30 Oct 2008 10:02:19 -0600 From: "Bruce Snyder" To: users@activemq.apache.org Subject: Re: JBoss Integration with Multiple ActiveMQ Instances In-Reply-To: <20249617.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20249617.post@talk.nabble.com> X-Virus-Checked: Checked by ClamAV on apache.org On Thu, Oct 30, 2008 at 9:46 AM, wconroy wrote: > > I have the requirement to run 2 activeMQ instances that look identical as far > as queue names go, but are different in that distinct applications will talk > to each of them. > > I am using JBoss to create MDBs that listen to the applications and respond > with a message back to the activeMQ instance that the MDB is reading from. > > I have it working with a single instance of activeMQ running. I don't know > how I can get a second MDB up and running now and have it connect to the > second activeMQ. In the ra.xml file, it seems like the resource can only be > configured to talk to 1 activeMQ. > > Is there a suggested solution for this? The only thing I have thought of is > creating 2 different rar's each configured to talk to a single activeMQ, but > this seems like it is not the right thing to do. If you definitely want to speak with a different broker, then I believe that's exactly what you must do. Each JCA resource adapter is designed to communicate with only one enterprise information system. I have zero detail on the design of your system, but have you considered just letting the applications communicate with a single broker and then just network two brokers together? ActiveMQ supports what is known as a network of brokers, i.e., multiple brokers working together in a federated manner. See the following page for more info: http://activemq.apache.org/networks-of-brokers.html A network of brokers forwards messages between the brokers the brokers based on configuration and demand for messages. This results in what some folks call distributed destinations. Bruce -- perl -e 'print unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E