auses duplicate messages after container restart
[EXTERNAL] This message originated outside of IG.
On 08/06/2020 8:00 pm, Attila Kun wrote:
> Hi,
>
> I’m using the qpid-proton C++ library and receiving messages via this
> component:
> https://eur01.safelinks.protection.outlook.com/?ur
stops because of the error above.
8. My app starts the container again.
9. My app receives messages A and B again. These are undesirable duplicates
that the app has already processed in points 4-5.
My aim is to eliminate the duplicate messages in point 9. I tried the following:
1. I
that the app has already processed in points 4-5.
My aim is to eliminate the duplicate messages in point 9. I tried the following:
1. I could use a local cache where I store the message ids that my app has
already processed. I don’t really want to do this, because this cache might
grow
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
Hello,
I am new to Qpid, starting to work on an extensive projects code base.
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 message twice?
There i
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
If I put the same TextMessage in a queue more than once, say 10 times, I
always end up with just one item in the queue.
ie. {"query":"apple"}
Is this expected behavior for AMQP and Queues?
Regards,
Ed Bragg
--
---
Ed Bragg
iHarvest Product Manager
Principle Software Engineer
Thermopylae Scien
'format', arguments :
{x-match:any, data-format:standard}}
I see duplicate messages for subscription (1).
However if I use two subscriptions that subscribe to "x-match:all", e.g.
1) x-bindings:[{exchange:'amq.match', key:'source', arguments :
{x-match:all, dat
'amq.match', key:'source', arguments :
{x-match:any, data-source:A}}
2) x-bindings:[{exchange:'amq.match', key:'format', arguments :
{x-match:any, data-format:standard}}
I see duplicate messages for subscription (1).
However if I use two subscriptions tha
ts:
> {x-match: any, data-service: item-selection, item-owner: fadams}}]}}"
>
>
>
--
View this message in context:
http://apache-qpid-users.2158936.n2.nabble.com/Dynamic-Routes-and-Duplicate-Messages-tp6562267p6591836.html
Sent from the Apache Qpid users mailing list archive a
>
> Hmmm... it worked for me (albeit on trunk, but I don't *think* that
> should make a difference here).
>
>
>
--
View this message in context:
http://apache-qpid-users.2158936.n2.nabble.com/Dynamic-Routes-and-Duplicate-Messages-tp6562267p6587695.html
Sent from
On 07/15/2011 04:43 PM, Fallon, Richard wrote:
FYI - I have tried adding unique keys to each of the subscribers but
unfortunately still get the same results.
Hmmm... it worked for me (albeit on trunk, but I don't *think* that
should make a difference here).
Did you restart the brokers? The d
Hi Gordon,
FYI - I have tried adding unique keys to each of the subscribers but
unfortunately still get the same results.
Richard
-Original Message-
From: Gordon Sim [mailto:g...@redhat.com]
Sent: 14 July 2011 16:59
To: users@qpid.apache.org
Subject: Re: Dynamic Routes and Duplicate
On 07/14/2011 04:40 PM, rfallon wrote:
I'll have a go at using a unique key and let you know how I get on.
Great, btw I meant using a unique key on your subscribers here, not on
the federated route.
-
Apache Qpid - AMQP Mess
Hi Gordon,
Thanks for the update.
I'll have a go at using a unique key and let you know how I get on.
Richard
--
View this message in context:
http://apache-qpid-users.2158936.n2.nabble.com/Dynamic-Routes-and-Duplicate-Messages-tp6562267p6583763.html
Sent from the Apache Qpid
On 07/08/2011 01:09 PM, reekahdoh wrote:
Hello All,
I'll try and keep this as simple as possible. I'm using C++ Apache Qpid
v0.8, and am having a problem when using dynamic routes with the headers
exchange.
FIRSTLY:
Send two messages the default headers exchange on a broker.
One Message has
Thanks for your time,
Richard Fallon
--
View this message in context:
http://apache-qpid-users.2158936.n2.nabble.com/Dynamic-Routes-and-Duplicate-Messages-tp6562267p6562267.html
Sent from the Apache Qpid users mailing list archive at
Hello All,
I'll try and keep this as simple as possible. I'm using C++ Apache Qpid
v0.8, and am having a problem when using dynamic routes with the headers
exchange.
FIRSTLY:
Send two messages to BROKER_A on the default headers exchange.
One Message has the headers :data-format=standard, dat
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
ws:
FailoverSingleServer:114 - No delay between connect retries, use
tcp://host:port?connectdelay='value' to enable.
It seems that the connectdelay value has not been picked up. Can anyone
conjecture why?
Thanks for any help!
-Simon
--- On Sun, 2/28/10, me really wrote:
Fr
27;
We are experiencing duplicate messages.
Here's what happens. The producer sends a steady stream of messages, but we
cansee that occasionally, the consumer receives duplicate messages. What we see
in the logs is that the duplicate messages appear to be transmitted when there
is a failove
25 matches
Mail list logo
