Return-Path: Delivered-To: apmail-qpid-users-archive@www.apache.org Received: (qmail 31095 invoked from network); 16 Feb 2011 15:34:48 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 16 Feb 2011 15:34:48 -0000 Received: (qmail 63142 invoked by uid 500); 16 Feb 2011 15:34:48 -0000 Delivered-To: apmail-qpid-users-archive@qpid.apache.org Received: (qmail 62257 invoked by uid 500); 16 Feb 2011 15:34:46 -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 62249 invoked by uid 99); 16 Feb 2011 15:34:45 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Feb 2011 15:34:45 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of gregory.bayard@gmail.com designates 209.85.214.170 as permitted sender) Received: from [209.85.214.170] (HELO mail-iw0-f170.google.com) (209.85.214.170) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Feb 2011 15:34:37 +0000 Received: by iwn6 with SMTP id 6so1782604iwn.15 for ; Wed, 16 Feb 2011 07:34:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type:content-transfer-encoding; bh=CR4fbWrFzj8vjGWz0g+XBUCY0JRVZZHfm9qjqxJOf9E=; b=tajPK0cLP4xoRs5PmgsKRmSIrt1OREyty99ewSyHOH8mG1RLIur72APMdR6MX16lAo P4Ppk8PI9LeR/u2q2VPJ6iAMoaUPsM3bt5g7sS5Ct1AYKkXlqIgRkWh1H8zMdmFBeBLt QhMPp4cFJt5SlryW2szJFSGrlrTqTXtyaicQY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=ZTyyJVShG8O2n7p2LQGAe8R4Yg2jzTXUGy4Bd4OhnXLTJsmzYnW+bQD/m6Uuqi3PG2 LOkUeCrLJTIZGJ81sm162MdGJE/8TrGpMpCuiT74PZPgKRu8rl7XJeIinHSPc52S0yuU oebVbBTKsguliPGfVBHILBBwZl7ZuioiTxrWI= MIME-Version: 1.0 Received: by 10.42.220.8 with SMTP id hw8mr1104274icb.111.1297870456469; Wed, 16 Feb 2011 07:34:16 -0800 (PST) Received: by 10.231.36.199 with HTTP; Wed, 16 Feb 2011 07:34:16 -0800 (PST) In-Reply-To: <4D5A6457.20902@redhat.com> References: <4D596C0F.4070301@redhat.com> <4D5A6457.20902@redhat.com> Date: Wed, 16 Feb 2011 10:34:16 -0500 Message-ID: Subject: Re: Sending a message to a custom QPID direct exchange from Python From: Gregory Bayard To: users@qpid.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org I did a clean install of Python with the 0.8 module and it is working as expected on both Windows and Linux, so I was clearly troubleshooting the wrong things. I previously had the 0.6 version installed before I added the 0.8 version. Thanks for your responses and suggestions! Greg On Tue, Feb 15, 2011 at 6:32 AM, Gordon Sim wrote: > On 02/14/2011 09:45 PM, Gregory Bayard wrote: >> >> Hi Gordon, >> >> I was originally working with 0.6 and the double-quoting was a quick >> attempt to find some problem with my exchange and queue specification. >> =A0When I updated my addressing string for Qpid 0.8, I still get the >> same result. =A0The message is picked up by topic listeners listening to >> the masterserver.summary.queue' topic on the 'masterserver.direct' >> exchange. =A0The string, as you specified, is now: >> >> "masterserver.direct/masterserver.summary.queue; {create: always, >> node: {type:topic, x-declare:{type:direct}}}" > > To be clear, I don't think you need the "; {create: always, node: > {type:topic, x-declare:{type:direct}}}" part, that was just as an example= of > the correct syntax. > >> Keep in mind this queue will essentially always have been created by >> the C++ server which is essentially guaranteed to start before any >> Python clients. =A0I just can't figure out anyway to get Python to send >> messages to the 'masterserver.summary.queue' on the >> 'masterserver.direct' exchange. > > Just to be clear, are you saying that creating a sender in python for the > address "masterserver.direct/masterserver.summary.queue" and then sending= a > message with that, the messages do not get to the queue in question? > > That works fine for me, are you sure you don't have older python libs on > your path? > >> However, I have no problem sending >> messages to the 'amq.direct' direct exchange from Python. =A0This issue >> seems to be limited to custom direct exchanges. =A0Any suggestions on >> how I could get a message via the custom direct exchange created by >> the C++ from Python to the C++ server's queue would be greatly >> appreciated. > > Are you getting errors or the messages just appear to be dropped? As I sa= y > it works fine for me with 0.8 packages. See attached client and server. T= he > server is a modified version of the old example that I think matches what > you describe, the client is a simple python program that sends to > "masterserver.direct/masterserver.summary.queue". Start the server first, > then run the client and that all works for me, does it work for you? > > Btw, there is a messaging API in c++ as well that I think is a lot simple= r > than the old qpid/client API. It is conceptually similar to the python AP= I > you are using. > > > --------------------------------------------------------------------- > Apache Qpid - AMQP Messaging Implementation > Project: =A0 =A0 =A0http://qpid.apache.org > Use/Interact: mailto:users-subscribe@qpid.apache.org > --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:users-subscribe@qpid.apache.org