From users-return-7816-apmail-qpid-users-archive=qpid.apache.org@qpid.apache.org Thu Mar 7 14:40:20 2013 Return-Path: X-Original-To: apmail-qpid-users-archive@www.apache.org Delivered-To: apmail-qpid-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id DDF55D997 for ; Thu, 7 Mar 2013 14:40:19 +0000 (UTC) Received: (qmail 99569 invoked by uid 500); 7 Mar 2013 14:40:19 -0000 Delivered-To: apmail-qpid-users-archive@qpid.apache.org Received: (qmail 99300 invoked by uid 500); 7 Mar 2013 14:40:19 -0000 Mailing-List: contact users-help@qpid.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@qpid.apache.org Delivered-To: mailing list users@qpid.apache.org Received: (qmail 99270 invoked by uid 99); 7 Mar 2013 14:40:18 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Mar 2013 14:40:18 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [209.85.128.41] (HELO mail-qe0-f41.google.com) (209.85.128.41) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Mar 2013 14:40:11 +0000 Received: by mail-qe0-f41.google.com with SMTP id 6so299199qeb.14 for ; Thu, 07 Mar 2013 06:39:49 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:x-originating-ip:in-reply-to:references :date:message-id:subject:from:to:content-type:x-gm-message-state; bh=jRrQAWOeHz8heQzvdO0Lv/GRCy5hbf/zuDwFfQ+6UpQ=; b=JTU2E8nzHghCdXBnnRVs67zH0uf7E6iZWMnYkGTvvewEmAItpN+EDxBsG5qO18CYha ET7fwOOfxy4VZdOD6435GKa9+CsLXZnCIrgOLVkqhwrwRYWnZ27MrkURqeq3KkRauzcK JgFEV8WKssc6bSiUzzhUjsNdZOyvrBh6uegVHgvTtVdMIDyf8RktWHSmvh7TIVnN8p3a InYDRFKo6+RSlQhNnsPdT1Uepx+xkRwVTwersefQMh4+uZc8jmhf5UzDT+/L4cWDcnK9 2My819+nJxsJZviFBkPCxDxNWumP/7T6CkLhhJIgZV9J0y9DykpD0zs3+N3PRziFgPTN M7Sg== MIME-Version: 1.0 X-Received: by 10.224.178.4 with SMTP id bk4mr50441022qab.70.1362667188810; Thu, 07 Mar 2013 06:39:48 -0800 (PST) Received: by 10.49.60.230 with HTTP; Thu, 7 Mar 2013 06:39:48 -0800 (PST) X-Originating-IP: [193.29.76.37] In-Reply-To: References: Date: Thu, 7 Mar 2013 15:39:48 +0100 Message-ID: Subject: Re: how to set static binding (routingkeys) config for Java broker? From: Jakub Scholz To: users@qpid.apache.org Content-Type: multipart/alternative; boundary=20cf302ef94abcb7d904d756ad7d X-Gm-Message-State: ALoCoQlm7tsa0EO02QjF/Dwr7VmA5ehKXQSKSznc7On8WGCnlHfOPF/unINARDq/MwcSjroSr4kS X-Virus-Checked: Checked by ClamAV on apache.org --20cf302ef94abcb7d904d756ad7d Content-Type: text/plain; charset=ISO-8859-1 If you are still using the XML configuration, in the virtualhosts.xml you should be able to add the binding in the queue section ... like this: queue1 exchange1 rtgkey.# true Regards Jakub On Thu, Mar 7, 2013 at 3:26 PM, Tom M wrote: > We are attempting to set the configuration for our qpid broker in > development of a production system. > > It appears that qpid-config does not work for the Java broker. Is this > still correct? > > I see that we can set the config for the exchanges and queue in the > virtualhosts.xml. > But, I can not find any documentation or examples about setting the binding > (routingkeys) in this config file. Is it possible to config the bindings > from this file? If so, can you provide the syntax? > > I have found that setting static bindings for static Direct Exchange to > static queue does work for the Java broker (and we have had success > providing messaging this way with the Java broker). > We can staticly configure the bindings (as well as the exchange and > queues) via the C++ client lib, using session exchangeBind( ), from a > static Direct Exchange and static queue. > Also, can successfully set via Jconsole. > But, we don't want to have to use these methods for our production system > (we are attempting to get away from the C++ client lib, and then I don't > even see this available for the messaging lib.) > > We would prefer to set our mission operational messaging elements via a > config file (or config script or Java app) on broker start up. > > This is primarily driven by our HA requirements. For HA, for these primary > command and responses messages, we need our exchanges, queues and bindings > to be static so that if any of the involved components goes down, we will > not lose any messages. > Also, we need to set bindings such that, in some cases, a single > message into given exchange needs to route to multiple queues. And, also, > some queues need to be bound to multiple exchanges. > > A little broader question.... > If qpid-config does not work for the Java broker, is there some other a way > to provide the config that will work for both the Java and C++ broker? > We would like to have the flexibility to config with either. > > thanks, > Tom Maggio > --20cf302ef94abcb7d904d756ad7d--