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 90D6418AC2 for ; Fri, 28 Aug 2015 20:30:53 +0000 (UTC) Received: (qmail 92434 invoked by uid 500); 28 Aug 2015 20:30:53 -0000 Delivered-To: apmail-qpid-users-archive@qpid.apache.org Received: (qmail 92399 invoked by uid 500); 28 Aug 2015 20:30:53 -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 92387 invoked by uid 99); 28 Aug 2015 20:30:53 -0000 Received: from Unknown (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Aug 2015 20:30:53 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id A3B3D1AB0D2 for ; Fri, 28 Aug 2015 20:30:52 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.879 X-Spam-Level: ** X-Spam-Status: No, score=2.879 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd2-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-us-west.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id qLTFmzJXL--O for ; Fri, 28 Aug 2015 20:30:51 +0000 (UTC) Received: from mail-ig0-f194.google.com (mail-ig0-f194.google.com [209.85.213.194]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with ESMTPS id 566C32055B for ; Fri, 28 Aug 2015 20:30:51 +0000 (UTC) Received: by igcwe12 with SMTP id we12so3407218igc.3 for ; Fri, 28 Aug 2015 13:30:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=2RCV9/wH7FArQMyPP6kIeIzyoAstpCISsS7vrWztxW8=; b=NLAbtT0tsAn6JhNq0hHPuG/5rmeCtQuo4bKsmlIiwRMBKSUKQaLvKgFfGoYe56h2nY KeiucN+tsxXGZDKRAzKSLjwdJw5pAEhj7GKrekzPT6BiCQGOIZchJ58Cp5+/IT8qbGLH +jbGYfe1gRJRamBJmh+K/q5+nAtkloN1ei4bGXJ+2fAsXdxrlLI+WCMZMGGkdQyT/7Dx E1RKLgrENx6YUtXrgkxyWQcfMNP5nvkT8p7ZJP5uLGQqc1vuAf5MlZxa51XUvE/DX3VL 566bToXHFmsxdo5HFh55/BFGi7i107aXau29oGWQVntOrHHQIykkax1wQoszjNNCxJq+ +Crw== MIME-Version: 1.0 X-Received: by 10.50.136.134 with SMTP id qa6mr5183334igb.13.1440793850719; Fri, 28 Aug 2015 13:30:50 -0700 (PDT) Received: by 10.79.91.5 with HTTP; Fri, 28 Aug 2015 13:30:50 -0700 (PDT) In-Reply-To: <55E0C050.6040801@redhat.com> References: <55E0C050.6040801@redhat.com> Date: Fri, 28 Aug 2015 15:30:50 -0500 Message-ID: Subject: Re: Dispatch Router - why this config doesn't work? From: jjw tectec To: users@qpid.apache.org Content-Type: multipart/alternative; boundary=089e0141a8dcaab36f051e64f53f --089e0141a8dcaab36f051e64f53f Content-Type: text/plain; charset=UTF-8 Hi Ted, My 2nd broker is running on a different port 5670 (command: ./qpidd -p 5670 --data-dir /home/mmos/datadir/). So the scenario I'm trying to test is the following: Client_publisher -> BrokerA (port 5672) -> Router -> BrokerB (port 5670) -> Client_subscriber This is my first step in testing Dispatch Router. Once this is successful, my BrokerB will be replaced by something else. Can you please provide a config file that would make this scenario work? Thank you! jjw On Fri, Aug 28, 2015 at 3:10 PM, Ted Ross wrote: > Hi, > > Thanks for giving Dispatch Router a try. I'm a little unclear as to > exactly what it is you are trying to do. > > It looks to me that you have both BrokerA and the Router listening on port > 5672. This is not going to work as whichever process you start first will > get the port and the other will fail to open its listener. > > However, simply fixing this problem isn't going to make this work. Can > you provide some more detail as to what you want to see? Are there > specific queues or topics on the brokers that you are using? What is the > desired path for messages to flow along? > > Thanks, > > -Ted > > > > On 08/28/2015 03:00 PM, jjw tectec wrote: > >> Hello, >> >> I'm trying to run a quick test using Dispatch Router, and I think I need >> help with configuration. >> >> I'd like to set up such a router between two AMQP brokers, and routes >> messages from BrokerA to BrokerB. >> >> Right now, I have Qpid BrokerA running on port 5672, and Qpid BrokerB >> running on port 5670, and I have a router running the following >> "qdrouterd.conf" config file content: >> >> listener { >> addr: localhost >> port: 5672 >> sasl-mechanisms: ANONYMOUS >> } >> >> connector { >> addr: localhost >> port: 5670 >> sasl-mechanisms: ANONYMOUS >> } >> >> router { >> mode: standalone >> } >> >> Why doesn't the above config work with this simple scenario? >> I tested this broker+router setup using two clients: subscriber >> subscribing >> to port 5670, and publisher publishing to port 5672. Messages don't flow >> through... >> >> Thanks >> >> jjw >> >> > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org > For additional commands, e-mail: users-help@qpid.apache.org > > --089e0141a8dcaab36f051e64f53f--