The Broker built from trunk rev 80239 and the 3rd part persistence from rev
3353 seem to send the messages in order when the connection is broken and
then reestablished. The problems I noticed with the 0.5 release seem to be
resolved at this level.
--
View this message in context:
lroloson wrote:
I turned on the additional logging as suggested - and ran some additional
tests today, using the 0.5 broker on Linux the 0.5 listener on Windows
(which I modified to reconnect). When I tested again today the messages were
all delivered, however they were out of order. I have
Carl,
I tried you experiment this AM, and basically - if I unplug the cable on the
linux end, and kill the listener on the other end (today I was using a linux
listener on a separate machine), it works fine. When I plug the cable back
in (a couple minutes later) restart the listener, all the
lroloson wrote:
Carl,
I tried you experiment this AM, and basically - if I unplug the cable on the
linux end, and kill the listener on the other end (today I was using a linux
listener on a separate machine), it works fine. When I plug the cable back
in (a couple minutes later) restart the
I will work on getting the latest broker to build from the trunk, and I will
repeat the test. I will post the results here when completed. Thanks !
--
View this message in context:
http://n2.nabble.com/0.5-C%2B%2B-example-listener-hangs-during-testing-tp3344401p3399777.html
Sent from the Apache
I have tried the client on linux, with the same results. All of the messages
are delivered - but they are out of order if the connection is broken. My
application requires delivery in chronological order - and when the
connection is intact all of the messages are delivered in order. When the
lroloson wrote:
I have tried the client on linux, with the same results. All of the messages
are delivered - but they are out of order if the connection is broken. My
application requires delivery in chronological order - and when the
connection is intact all of the messages are delivered in
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
I have added some reconnect logic to the example listener that I am running
on windows, and now when the connection is broken the listener reconnects
and I can continue receiving messages. At this point I have not detected any
missing messages. I have received one duplicate message, but I believe
currentSequenceNum = 12850
All messages 12850...N are in order)
-Original Message-
From: lroloson [mailto:lrolo...@trmi.com]
Sent: Thu 7/30/2009 9:10 AM
To: users@qpid.apache.org
Subject: Re: 0.5 C++ example listener hangs during testing
I have added some reconnect logic to the example
lroloson wrote:
I have added some reconnect logic to the example listener that I am running
on windows, and now when the connection is broken the listener reconnects
and I can continue receiving messages. At this point I have not detected any
missing messages. I have received one duplicate
lroloson wrote:
I have the 0.5 broker and direct_producer running on Linux, and I have the
0.5 C++ direct listener example code running in Windows. I have transferred
tons of messages, and all seems to be working fine under normal conditions.
I am using persistent queues and messages - all work
I found some information on the ConnectionSettings, I can see the heartbeat
is an integer, but I cannot find the unit of measure. Is the value a count,
or a time? I can't find any information that tells me how it is handled.
--
View this message in context:
lroloson wrote:
I found some information on the ConnectionSettings, I can see the heartbeat
is an integer, but I cannot find the unit of measure. Is the value a count,
or a time? I can't find any information that tells me how it is handled.
It is an interval, specified in seconds, at which
Please disregard the last - I forgot to set the user and password :-(
--
View this message in context:
http://n2.nabble.com/0.5-C%2B%2B-example-listener-hangs-during-testing-tp3344401p3346153.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
15 matches
Mail list logo