From users-return-1729-apmail-qpid-users-archive=qpid.apache.org@qpid.apache.org Wed Aug 05 20:48:07 2009 Return-Path: Delivered-To: apmail-qpid-users-archive@www.apache.org Received: (qmail 15243 invoked from network); 5 Aug 2009 20:48:07 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 5 Aug 2009 20:48:07 -0000 Received: (qmail 61006 invoked by uid 500); 5 Aug 2009 20:48:14 -0000 Delivered-To: apmail-qpid-users-archive@qpid.apache.org Received: (qmail 60944 invoked by uid 500); 5 Aug 2009 20:48:14 -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 60931 invoked by uid 99); 5 Aug 2009 20:48:14 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Aug 2009 20:48:14 +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, 05 Aug 2009 20:48:05 +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 n75KljMp002424 for ; Wed, 5 Aug 2009 16:47:45 -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 n75KliTu000361 for ; Wed, 5 Aug 2009 16:47:44 -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 n75Klhks011482 for ; Wed, 5 Aug 2009 16:47:43 -0400 Message-ID: <4A79EF9C.5020605@redhat.com> Date: Wed, 05 Aug 2009 16:46:20 -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: 0.5 C++ example listener hangs during testing References: <1248799735467-3344401.post@n2.nabble.com> <4A6F345F.5050505@redhat.com> <1248810698943-3345588.post@n2.nabble.com> <4A6F5C2A.9020906@redhat.com> <1248815837126-3346078.post@n2.nabble.com> <1248816640931-3346153.post@n2.nabble.com> <1248963031998-3356545.post@n2.nabble.com> <4A71BB2E.8080409@redhat.com> <1249410897716-3386382.post@n2.nabble.com> <1249499010937-3394145.post@n2.nabble.com> <4A79DA99.5010002@redhat.com> <1249502632049-3394382.post@n2.nabble.com> In-Reply-To: <1249502632049-3394382.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 lroloson wrote: > Carl, > > I have the 0.5 broker and direct_producer running on Linux, and a slightly > modified 0.5 direct_listener running on windows. When the connection is > established, I receive all of the messages, in order from the Linux broker. > Everything appears to be fine. > > I am now testing some fault recovery scenarios, such as a broken ethernet > connection between the linux broker and the windows consumer. When I > intentionally disconnect the cable from the linux machine, the producer > continues, the messages and the queue are persistent, all of the messages > are saved. The windows producer detects the broken connection and retries to > establish the connection (I modified direct_listener to do that). When I > plug the cable back in, the client reconnects, and the messages are > delivered again, albeit out of order. (see my previous posts in this > thread). > > I am looking for a way to get the broker to send the messages in order, when > the connection is reestablished. got it, can we do a quick experiment. pull the cable. then kill the client, and start a new one when the link is re-connected and check the order across the two clients. This will tell us if it is in the client or client's local queue for example. Carl. --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:users-subscribe@qpid.apache.org