Return-Path: Delivered-To: apmail-qpid-users-archive@www.apache.org Received: (qmail 24074 invoked from network); 15 Apr 2009 14:40:36 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 15 Apr 2009 14:40:36 -0000 Received: (qmail 65122 invoked by uid 500); 15 Apr 2009 14:40:36 -0000 Delivered-To: apmail-qpid-users-archive@qpid.apache.org Received: (qmail 65073 invoked by uid 500); 15 Apr 2009 14:40:36 -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 65062 invoked by uid 99); 15 Apr 2009 14:40:36 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 Apr 2009 14:40:36 +0000 X-ASF-Spam-Status: No, hits=-4.0 required=10.0 tests=RCVD_IN_DNSWL_MED,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of cctrieloff@redhat.com designates 66.187.237.31 as permitted sender) Received: from [66.187.237.31] (HELO mx2.redhat.com) (66.187.237.31) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 Apr 2009 14:40:28 +0000 Received: from int-mx2.corp.redhat.com (int-mx2.corp.redhat.com [172.16.27.26]) by mx2.redhat.com (8.13.8/8.13.8) with ESMTP id n3FEe8B1019457 for ; Wed, 15 Apr 2009 10:40:08 -0400 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx2.corp.redhat.com (8.13.1/8.13.1) with ESMTP id n3FEe7KP031694 for ; Wed, 15 Apr 2009 10:40:08 -0400 Received: from localhost.localdomain (dhcp-100-19-90.bos.redhat.com [10.16.19.90]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id n3FEe117030546 for ; Wed, 15 Apr 2009 10:40:07 -0400 Message-ID: <49E5F11A.8020609@redhat.com> Date: Wed, 15 Apr 2009 10:37:14 -0400 From: Carl Trieloff Reply-To: cctrieloff@redhat.com Organization: Red Hat User-Agent: Thunderbird 2.0.0.21 (X11/20090320) MIME-Version: 1.0 To: users@qpid.apache.org Subject: Re: rdma protocol with qpid References: <1239806038831-2639156.post@n2.nabble.com> In-Reply-To: <1239806038831-2639156.post@n2.nabble.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.58 on 172.16.27.26 X-Virus-Checked: Checked by ClamAV on apache.org ft420 wrote: > how to use qpidd with rdma protocol? I have gone through the FAQ still i am unclear about what exactly has to be done to use rdma protocol? do we have to install anything? i have already installed qpidd-rdma-0.4.732838-1.el5.i386 and qpidc-rdma-0.4.732838-1.el5.i386 > > ./qpidd --transport rdma -p 5006 > 2009-apr-15 19:26:58 notice Listening on TCP port 5006 > 2009-apr-15 19:26:58 critical Broker start-up failed: No such transport: 'rdma' (qpid/broker/Broker.cpp:389) > 2009-apr-15 19:26:58 notice Shut down > > thanking in anticipation > > Two things, 1. load the rdma module on the broker & client 2. if you use perftest or latencytest, use -P rdma or if you have your our client, specify rdma and the protocol in the connection options. i.e. it is done the same way tls /ssl is specified. Connection Settings: -b [ --broker ] HOST (localhost) Broker host to connect to -p [ --port ] PORT (5672) Broker port to connect to -P [ --protocol ] tcp|rdma (tcp) Protocol to use for broker connection regards Carl. --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:users-subscribe@qpid.apache.org