Return-Path: Delivered-To: apmail-qpid-users-archive@www.apache.org Received: (qmail 57362 invoked from network); 6 Feb 2009 13:54:34 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 6 Feb 2009 13:54:34 -0000 Received: (qmail 58583 invoked by uid 500); 6 Feb 2009 13:54:33 -0000 Delivered-To: apmail-qpid-users-archive@qpid.apache.org Received: (qmail 58564 invoked by uid 500); 6 Feb 2009 13:54:33 -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 58553 invoked by uid 99); 6 Feb 2009 13:54:33 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Feb 2009 05:54:33 -0800 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 aconway@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; Fri, 06 Feb 2009 13:54:27 +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 n16Ds5Hb009168 for ; Fri, 6 Feb 2009 08:54:05 -0500 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 n16Ds58N015620 for ; Fri, 6 Feb 2009 08:54:06 -0500 Received: from [10.16.10.100] (vpn-10-100.bos.redhat.com [10.16.10.100]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id n16Ds5sW028884 for ; Fri, 6 Feb 2009 08:54:05 -0500 Message-ID: <498C40FC.8060607@redhat.com> Date: Fri, 06 Feb 2009 08:54:04 -0500 From: Alan Conway Organization: Red Hat User-Agent: Thunderbird 2.0.0.19 (X11/20090105) MIME-Version: 1.0 To: users@qpid.apache.org Subject: Re: Checking qpid installation sanity References: <1802abc00902042016n26ea86eblf6c4bc117dd4a2b8@mail.gmail.com> <1802abc00902050959w22c9efe5s7cac8d481f250a5f@mail.gmail.com> <498B4580.50203@redhat.com> <1802abc00902051902u6aa016a0y20c3bc29cb1810ee@mail.gmail.com> In-Reply-To: <1802abc00902051902u6aa016a0y20c3bc29cb1810ee@mail.gmail.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 GS.Chandra N wrote: >> Alan Conway wrote: >> To play safe I'd suggest using a consistent version of all components, i.e. > all via yum or all built from source. That may be excessively paranoid on my > part > > Thanks Alan. I shall definitely try this. > > ps : Just being curious, does AMQP have any handshake upon initiating > conversation for the version info and such things? > Yes it does. If memory serves the broker indicates what protocols it supports and the client picks the one it likes. Currently a given version of Qpid broker or client only supports a single AMQP protocol version, but at some point we will probably support multiple AMQP versions. --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:users-subscribe@qpid.apache.org