sday, September 30, 2014 10:20:18 AM
> Subject: Re: Duplicate Messages
>
> Hi Steve,
>
> I wonder how to check for duplicates, as well. I create topics using
> --sequence like:
>
> qpid-config -b localhost exchange topic test_topic --durable
> --sequence
>
Hi Steve,
I wonder how to check for duplicates, as well. I create topics using
--sequence like:
qpid-config -b localhost exchange topic test_topic --durable
--sequence
I understood that the the order of messages is guaranteed, then. This
means a duplicate message can only be the
Hi Raphael,
> I am new to Qpid, starting to work on an extensive projects code base.
Welcome!
> I am trying to find the spot in the documentation where guarantees of the
> messaging system are discussed. For example: in case of a network problem,
> could it happen that the broker sends the same
I apologize. I found where somebody on our end was shoving everything into
a HashSet.
Sorry for the confusion.
Ed
On Thu, Jun 13, 2013 at 3:22 PM, Ed Bragg wrote:
> Hi Rob,
>
> We are using the Java Broker. Version 0.20.
> Right now we are running stock configuration (test).
>
> I have a Jav
Hi Rob,
We are using the Java Broker. Version 0.20.
Right now we are running stock configuration (test).
I have a Java class that is popping items onto the queue, and then pulling
them all off until none are left.
I'm using a QueueProducer, and initializing it with:
Destination dest =
No - that wouldn't be the expected behaviour of queues... can you give a
little more information about your test scenario... which broker are you
using (Java or C++)?, how did you set up the queue? how are you verifying
that only one message is actually on the queue?
There are queue types (such as
OK, so seems like there's at least a partial resolution to this, which is to
use the latest trunk build, due to the bug QPID-1893. This bug relates to the
java client not generating heartbeats, fixed 12-Jan-2010.
I'm not entirely sure how not properly responding to heartbeats causes the
resend o
As a follow-on...
The problem appears to be between the Java producer and the initial federated
broker.
The scenario is that after 8 mins, the connection times out on the broker, and
the producer
does failover, and resends a message that was sent previously, and received by
a
consumer.
Th
