is there a plan to implement something similar in
ActiveMQ Classic like there ids for Artemis that can detect duplicate messages,
Jason
From: Jason Jackson
Sent: Wednesday, July 10, 2024 9:16 AM
To: users@activemq.apache.org
Subject: Re: ActiveMQ Classic
taking place while there is no broker failure.
The duplicate messages will occur when a broker fails, I suspect it is due to a
message being sent but no acknowledgement being received and then the message
is resent.
Here is an example of my route from ActiveMQ to IBM MQ.
"active
Are the duplicate messages already in the queue or are they being created
during the process of moving them from ActiveMQ Classic to IBM MQ? If the
latter, do you know why the duplicates are being created (e.g. the network
connection fails)? Are you mitigating duplicates by using a transaction of
Good afternoon.
I was wondering if anyone had any good links of information regarding how to
use Idempotent within ActiveMQ Classic Camel routes.
I am having an issue with duplicate messages within ActiveMQ Classic 5.18.4
when messages are moved from ActiveMQ to IBM MQ using Camel.
>From
I have just send a PR for this
https://github.com/apache/activemq-artemis/pull/2510
I don't know if I need to post it here but just for let you know.
Thanks
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
I have just being able to reproduce it . I have to add the two following
lines.
createQueue(0, "x.Provider.y.Agent.z.Status", "x.Provider.y.Agent.z.Status",
null, false, "admin" , "admin", RoutingType.ANYCAST);
createQueue(1, "x.Provider.y.Agent.z.Status", "x.Provider.y.Agent.z.Status",
null, fals
Hi,
I was trying to create a test case for this issue but I am not being able to
replicate it in an automatic tests, I was debugging the servers that use for
reproduce the issue and print all the binding information from one of them.
= Start Server 1
*Start* LocalQueueBinding [address=Notificati
I was able to reproduce this issue with Artemis server 2.6.3 and Artemis
client 2.6.0 I have updated the original jira.
https://issues.apache.org/jira/browse/ARTEMIS-2156
I will try to create a test case, it could take some time because I am on
holidays and internet connection is very bad.
Regar
there is an option on connection factory for the prefix. I did not mean
the name of the queue itself.
Perhaps the client connects to the server perceives version and includes
the version automatically?
I will do some tinker with your example tomorrow. I had other tasks and I
was trying to hel
Hi Justin,
Maybe I am wrong but I think I cannot use that because in my use case the
server is 1.5.5 and the client is 2.6.2 and as far as I understand you
configure the acceptor in the broker.xml which is the server and that
configuration is for newer server versions.
Thanks & Best regards,
Luis
Hi Clebert,
I am using prefixes in my clients. I am not totally sure how the server
handles at new message from a new client (Server 1.5.5 - Client 2.6.2) but
they issue does not happens if the divert is not exclusive, so I am not sure
if that is a configuration issue.
On the other hand the clien
@Justin: They are using 1.6.2 as the server. and 2.6.2 as they client.
So he needs to set the prefixes at the connection factory I think.
On Thu, Nov 1, 2018 at 10:32 AM Justin Bertram wrote:
>
> In the default broker.xml since Artemis 2.5.0 you'll see a comment like
> this above the acceptors:
In the default broker.xml since Artemis 2.5.0 you'll see a comment like
this above the acceptors:
This is also noted in the documentation for the 2.5.0 release [1].
Have you configured these prefixes when observing the problem?
Justin
[1] https://activemq.apache.org/artemis/docs/lat
On that case you must use prefixes on your 2.6.2 clients.
Do you really need to mix 1.x and 2.x on this? I would keep things
aligned on this case.
But this is definitely related to your prefixes. When the client
connects to the older version a new queue is being created, and that's
causing your
Hi Clebert,
Thanks for your response, the issue is the other way around.
- I have a Artemis Server 1.5.5 (In Cluster) using exclusive diverts. If the
client use the version 2.6.2 the message got duplicate.
Let me know if I can provide more details on the issue.
Thanks & Best Regards,
Luis
-
There's a break on prefixes between 1.x and 2.x.
The fact that you have a divert on a prefixes address.. I'm not sure
what could happen between your routes.
Can you remove the prefixes and only use 2.x clients?
if you really want to mix this.. we would need to look at
compatibility tests betwe
I'm trying to understand the issue... you have a 2.6.2 server.. and
the issue happens when y ou use a 1.5.x client? is that correct?
On Tue, Oct 30, 2018 at 2:41 PM ldebello wrote:
>
> Hi,
>
> I have just raised a JIRA Ticket
> https://issues.apache.org/jira/browse/ARTEMIS-2156. We are facing an i
Hi,
I have just raised a JIRA Ticket
https://issues.apache.org/jira/browse/ARTEMIS-2156. We are facing an issue
having duplicate message using Artemis 1.5.5 in cluster with exclusive
divert.
I don't know how is the formal process to report a JIRA or let you know
about the ticket, that is the reas
; So the question remains, is the way I am doing it a proper way to do hub and
> spoke? The current behavior means that if each spoke has an embedded broker
> and if there are multiple spokes consuming a topic, then you can get
> duplicate messages. Embedded brokers are useful on both produce
I have opened an issue for this and added a unit test that reproduces the
problem to it:
https://issues.apache.org/jira/browse/AMQ-6784
Tomas
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Duplicate-messages-received-with-ActiveMQ-5-13-2-tp4728627p4729221.html
Sent
if each spoke has an embedded broker
and if there are multiple spokes consuming a topic, then you can get
duplicate messages. Embedded brokers are useful on both producer and
consumer, because they allow me to not have to deal with reconnects (the
embedded broker takes care of that).
There is also
t");
transportConnector.setBrokerService(broker);
transportConnector.start();
}
@Override
public void close() throws Exception {
transportConnector.stop();
broker.stop();
}
}
}
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Duplicate-messages-received-with-ActiveMQ-5-13-2-tp4728627p4729100.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
r]
spoke [broker] -> hub [broker] <- spoke
<- spoke
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Duplicate-messages-received-with-ActiveMQ-5-13-2-tp4728627p4729096.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
; over duplex connections. I noticed some special processing for duplex
> connections, namely that it creates additional bridges, in
> org.apache.activemq.broker.TransportConnection#processBrokerInfo.
>
> Tomas
>
>
>
> --
> View this message in context: http://activemq.22833
://activemq.2283324.n4.nabble.com/Duplicate-messages-received-with-ActiveMQ-5-13-2-tp4728627p4729068.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
pdated
when it should...
Tomas
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Duplicate-messages-received-with-ActiveMQ-5-13-2-tp4728627p4729005.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
it is not happening but I can now trace the code flow
> to within ConduitBridge.
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.
> nabble.com/Duplicate-messages-received-with-ActiveMQ-5-13-2-
> tp4728627p4728966.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
this message in context:
http://activemq.2283324.n4.nabble.com/Duplicate-messages-received-with-ActiveMQ-5-13-2-tp4728627p4728966.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
oes the decision not to conduit get
> made
> but I am still kind of lost in the code.
>
> Tomas
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.
> nabble.com/Duplicate-messages-received-with-ActiveMQ-5-13-2-
> tp4728627p4728962.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
s and not for the topic which I am sending messages to.
So either I don't have the tracing setup right or there is some other
channel via which brokers exchange information about consumers.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Duplicate-messages-received-wit
n not to conduit get made
but I am still kind of lost in the code.
Tomas
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Duplicate-messages-received-with-ActiveMQ-5-13-2-tp4728627p4728962.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
oint in and made it display the result of
> configuration.isConduitSubscriptions(), it shows as true for every call
> for
> every end point.
>
> Can you think of any other place that I may have missed that could change
> the conduitSubscribers behavior?
>
>
>
> --
> Vie
message in context:
http://activemq.2283324.n4.nabble.com/Duplicate-messages-received-with-ActiveMQ-5-13-2-tp4728627p4728931.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
ry to reproduce this in plain ActiveMQ.
>
> Thanks for the help!
>
> Tomas
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.
> nabble.com/Duplicate-messages-received-with-ActiveMQ-5-13-2-
> tp4728627p4728926.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
I am using some proprietary wrappers
which I can't share. If I can't find the root cause in reasonable time I can
try to reproduce this in plain ActiveMQ.
Thanks for the help!
Tomas
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Duplicate-messages-received-with-
behavior leaves me a bit puzzled:
>
> The issue is that the broker adds the message twice to the subscription,
> via
> org.apache.activemq.broker.region.TopicSubscription#add
>
> There is a check for duplicate messages,
> org.apache.activemq.bro
I can now reliably reproduce the duplication and I can prevent it. However,
the behavior leaves me a bit puzzled:
The issue is that the broker adds the message twice to the subscription, via
org.apache.activemq.broker.region.TopicSubscription#add
There is a check for duplicate messages
hanks,
Tomas
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Duplicate-messages-received-with-ActiveMQ-5-13-2-tp4728627p4728675.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
gt;
> Is there anything I could do to trace the flow to see where the message
> gets
> duplicated?
>
> Thanks,
> Tomas
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.
> nabble.com/Duplicate-messages-received-with-ActiveMQ-5-13-2-
> tp
#createBridge
returns an instance of org.apache.activemq.network.DurableConduitBridge.
Is there anything I could do to trace the flow to see where the message gets
duplicated?
Thanks,
Tomas
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Duplicate-messages-received-with-ActiveMQ
Do you have conduitSubscriptions set to false for your networkConnectors?
Or are your topics virtual and you're dynamically including both the topic
and the consumer queues?
Both of those could result in duplicate messages on a topic.
Tim
On Jul 18, 2017 6:36 AM, "tpavelka" wro
s
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Duplicate-messages-received-with-ActiveMQ-5-13-2-tp4728627.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
message in context: http://activemq.2283324.n4.
nabble.com/Duplicate-Messages-in-the-Message-Store-tp4724959p4725019.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
messages, but it did consume only
the once that inserted via Broker1.
This certainly explains me there is message store cached per Broker, which
is not good and causing problems.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Duplicate-Messages-in-the-Message-Store
fficulty in understanding how broker inserts messages into message
> queues.
> The code in activemq jar does explain that it gets the max(ID) for next
> sequence generator but when is this really happening? Is there any caching
> mechanism here? What is the message is already consumed and
t:
http://activemq.2283324.n4.nabble.com/Duplicate-Messages-in-the-Message-Store-tp4724959.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Session,
> Username and Password(if they are required), and also ensures closure on
> disposal. The missing code is is the Connect method
>
>
>
> where the Factory is instantiated by
>
>
>
> in the class constructor.
>
>
>
>
> --
> View this message in conte
is instantiated by
in the class constructor.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Receiving-multiple-duplicate-messages-Beginner-question-tp4706474p4706627.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
esponse code is running in a windows service, and request is
> called from a client on a different machine.
>
> Any ideas what the hopefully simple problem is?
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Receiving-multiple-duplicate-message
erent machine.
Any ideas what the hopefully simple problem is?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Receiving-multiple-duplicate-messages-Beginner-question-tp4706474p4706607.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
_manager.Connect creates a connection and session if this has not
already been done. The address simply holds the queue name and if the
message should be persisted.
Any ideas?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Receiving-multiple-duplicate-messages-Beginner
?
My Brokers : (Broker_A, Broker_B, Broker_C)
My Broker_B Setup:
Thanks
Mike
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Network-of-Brokers-using-5-12-1-duplicate-messages-tp4703129.html
Sent fro
That's the way I'd prefer it ;)
Will keep you posted
Andreas
On 04/11/14 18:55, Tim Bain wrote:
The functionality you're contemplating for the broker plugin seems pretty
far off from the standard ActiveMQ approach, since it involves knowing the
state of a message across the full network of brok
The functionality you're contemplating for the broker plugin seems pretty
far off from the standard ActiveMQ approach, since it involves knowing the
state of a message across the full network of brokers rather than allowing
each broker to operate as a stand-alone island that only needs to know
abou
Hi Tim,
I will make some time tomorrow to try your suggestions.
A Virtual destination would simply replace a durable subscriber with a
Queue receiver.
Messages posted to a mapped topic would end up in the the underlying
queues.
Now, a consumer that wasn't connected to the peer broker would
Andreas,
Your spec added two configuration elements your previous post didn't
mention, and I'd like to eliminate each of them in turn to see if it's
causing/contributing to the problem.
1. Your networkConnectors are apparently multicast. Please see what
happens if you configure them as
Hello Tim,
thanks for your answer. It took me a bit to digest it - so my apologies for
the delay in my answer.
I have come up with a test case that shows - and unfortunately confirms
my observations.The test case is located at [1].
Here is the excerpt of my problem descriptions & observation
ing a distributed cache to
hold txn-id for a certain period of time, etc. All of that highly depends on
your very specific use cases so you will have to look at your overall
architecture and decide for yourself.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/preventing-dupl
This sounds like application logic to me. It's the broker's job to try to
prevent re-delivery of the same message, but it's not the broker's job to
identify that two messages have similar content. That's the job of the
consumer of your messages, using whatever heuristics are most appropriate
to y
View this message in context:
http://activemq.2283324.n4.nabble.com/preventing-duplicate-messages-that-perform-the-same-action-tp4686571p4686573.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Are there any decent strategies to prevent sending the same message to the
queue twice?
Say for example it’s a money transfer … if you initiate the transfer twice
you’d transfer too much money. If you have an algorithm that retries you
would want it to NOT enqueue the message transfer message aga
If you have a network of brokers, messages on topics will be forwarded to
whichever broker the consumer connects to, without duplicate delivery of
any messages so long as no messages were processed by the consumer without
being ack'ed. If you were using queues, there's the potential for messages
t
Take a look at idempotent consumers in camel. This may help you out as a
basis for your plugin if you decide to go with it.
On Oct 18, 2014 5:47 PM, "Andreas Gies" wrote:
> Hi
>
> I am using ActiveMQ 5.10 in an application. So far the requirement for the
> remote locations has been for pure store
Hi
I am using ActiveMQ 5.10 in an application. So far the requirement for the
remote locations has been for pure store and forward capabilities,
so that a single AMQ broker was sufficient. This has changed in a way that now
2 nodes should be present in the remote location for
resilience and l
n the queue and due to which we
get duplicate messages at the consumer side. We are suspecting the data
files not getting deleted could be the reason along with some bug in
ActiveMQ. Wanted to what could be the reason of Messages which were actively
consumed re-appear on the Queue after the crash ?
P
the above settings & I am still getting duplicate messages
> replayed.
>
> Should I upgrade from Active MQ 5.5 to Active MQ 5.9 instead of upgrading to
> Active MQ 5.7?
>
> Thanks!
>
>
>
>
>
> --
> View this message in context:
> http://activemq.22
Can someone help me out what other settings other than trackMessages=true or
enableAudit="true" or auditNetworkProducers="true" can be used?
I have tried all the above settings & I am still getting duplicate messages
replayed.
Should I upgrade from Active MQ 5.5 to
I tried setting trackMessages=true. Still I get duplicate messages.
failover:(${jms.broker1.uri},${jms.broker2.uri})?randomize=false&jms.prefetchPolicy.queuePrefetch=1&maxReconnectAttempts=-1&trackMessages=true
I also added auditNetworkProd
> }
>
> Will adding session.commit() before tId=message.getStringProperty("TID")
> help in anyway?
>
> Thanks.
>
>
>
>
>
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Duplicate-messages-sent-in-Active-MQ-5-7-tp4675063p4675207.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
rty("TID")
help in anyway?
Thanks.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Duplicate-messages-sent-in-Active-MQ-5-7-tp4675063p4675207.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
> According to example in blog:
> http://bsnyderblog.blogspot.com/2010/05/tuning-jms-message-consumption-in.html
> The example has acknowledge="auto". I am wondering if I need to add this
> explicitly in my configuration.
>
> Thanks
> Badri
>
>
>
>
> -
ks
Badri
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Duplicate-messages-sent-in-Active-MQ-5-7-tp4675063p4675151.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
axReconnectAttempts=-1
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Duplicate-messages-sent-in-Active-MQ-5-7-tp4675063p4675139.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
;
> Can you please let me know if any configuration can be done to avoid this
> scenario? I am not doing enableAudit or optimizeAcknowledge.
>
> Appreciate your help!
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Duplicate-messages-sent-in-Active-MQ-5-7-tp4675063.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
dit or optimizeAcknowledge.
Appreciate your help!
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Duplicate-messages-sent-in-Active-MQ-5-7-tp4675063.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
The problem is resolved in 5.6-SNAPSHOT with the auditNetworkProducers flag
so I'll take another look at my backport.
Thanks,
Bruce
--
View this message in context:
http://activemq.2283324.n4.nabble.com/AMQ-5-5-1-Duplicate-Messages-After-Network-Outage-and-Broker-Restart-tp4520697p4526378
ter resolving my previous problem with the a network connector reconnection
> after a network outage I am now seeing duplicate messages being delivered
> from a queue. The situation is this:
>
> I have a spoke instance which has a network connector to a hub instance.
> For testing purposes I
After resolving my previous problem with the a network connector reconnection
after a network outage I am now seeing duplicate messages being delivered
from a queue. The situation is this:
I have a spoke instance which has a network connector to a hub instance.
For testing purposes I have them
apparently republished
(and were therefore reprocessed) within the next several minutes.
If anyone knows why/how duplicate messages might get published and/or has
suggestions for preventing this I would be very grateful!
TIA,
Mike L. (aka patzerbud)
ailover not load-balancing.
The reliability and availability (i.e. failover) of ActiveMQ have been
outstanding. However, producing (and then processing) 849 duplicate messages is
unacceptable.
Is the (occasional) production of duplicate messages known and customary
behavior?Is there something
this a bug?
Thanks,
Tejal
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Getting-duplicate-messages-with-retroactive-consumer-tp3321887p3321887.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
have different conduitSubscription settings for each kind of
> destination on a single network connection?
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Duplicate-messages-on-temporary-Topics-tp3209648p3215057.html
> Sent from the ActiveMQ - User m
kind of
destination on a single network connection?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Duplicate-messages-on-temporary-Topics-tp3209648p3215057.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
standing.
I am happy to provide a patch here, but I am not sure what the right thing
to do is. Extra config? Fix the filtering?
-adam
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Duplicate-messages-on-temporary-Topics-tp3209648p3214984.html
Sent from the ActiveMQ - Us
ix to add temp-destinations to the logic, or maybe
> a new config to allow temp-destinations in the excludes?
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Duplicate-messages-on-temporary-Topics-tp3209648p3210043.html
> Sent from the ActiveMQ -
dedDestinations" logic on the forwarding bridge?
Question 2: Is the right fix to add temp-destinations to the logic, or maybe
a new config to allow temp-destinations in the excludes?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Duplicate-messages-on-temporary-Topics-tp
I have a hub&spoke network of brokers setup (as documented) with
conduitSubscriptions=true for all topics.
When sending messages to a temporary Topic, the subscriber gets duplicate
messages at a number equal
to the number of spokes. This does NOT happen for regular Topics.
Am I missi
/usecases/ThreeBrokerVirtualTopicNetworkTest.java
On 19 May 2010 15:53, rsmith198 wrote:
>
> Hi
> I am not using a master slave configuration
> it a peer-peer
> Thanks
>
> --
> View this message in context:
> http://old.nabble.com/Duplicate-messages-with-a-Durabl
Hi
I am not using a master slave configuration
it a peer-peer
Thanks
--
View this message in context:
http://old.nabble.com/Duplicate-messages-with-a-Durable-Subscriber-with-networked-brokers-tp27827251p28609396.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
..later when they reconnect what will happen?
rsmith198 wrote:
>
> UPDATE is activeMQ 5.3 install
>
>
> rsmith198 wrote:
>>
>> Duplicate messages with a Durable Subscriber in networked brokers I have
>> a network of three brokers wsmithe6400 who has two bridges on
UPDATE is activeMQ 5.3 install
rsmith198 wrote:
>
> Duplicate messages with a Durable Subscriber in networked brokers I have a
> network of three brokers wsmithe6400 who has two bridges one to DrWho
> the other to FUJI I; I have a Durable Subscriber set up on wsmithe6400
Duplicate messages with a Durable Subscriber in networked brokers I have a
network of three brokers wsmithe6400 who has two bridges one to DrWho the
other to FUJI I; I have a Durable Subscriber set up on wsmithe6400 to
receive messages from DrWho and consumer DrWho to receive message from
On Wed, Feb 24, 2010 at 2:31 PM, Josh Carlson wrote:
> Hi Gary,
>
> Thanks for the explanation. The order is:
>
> consumer retrieves message
>
> connection is lost and consumer re-establishes connection to new master
> broker
>
> consumer acks the message retrieved from the former broker
Hi Gary,
Thanks for the explanation. The order is:
consumer retrieves message
connection is lost and consumer re-establishes connection to new
master broker
consumer acks the message retrieved from the former broker
consumer retrieves the same message it just ack'ed.
I gues
On failover, redispatch of unacked messages will occur and this is
unordered. There is no guarantee that the same consumer will get the same
messages after failover of a connection.
On the java client there is a message audit that will suppress duplicates
that may occur, I think the same is true fo
When using a shared file system master/server activemq configuration and
client acknoledgements we run into a problem when
our clients fail over to a new server. The problem is that the new
server does not appear to have any knowledge of pending
messages that the old server had dispatched to clie
back up in the location where it was brought down. When
it comes back up, it will process the first sent message again.
--
View this message in context:
http://www.nabble.com/Duplicate-Messages-on-Listener-Restart-tp25440673p25454456.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
On 15 Sep 2009, at 13:01, dbczak wrote:
the consumers do have normal url's (see TIPServer.java). But for
the sender,
what url do I use to send to multiple consumers?
--
View this message in context:
http://www.nabble.com/Duplicate-Messages-on-Listener-Restart-tp25440673p25452663
On Tue, Sep 15, 2009 at 6:01 AM, dbczak wrote:
>
> the consumers do have normal url's (see TIPServer.java). But for the sender,
> what url do I use to send to multiple consumers?
Just use the normal URL - tcp://:
If you want all subscribers to get a copy of a message, then you
should be using t
the consumers do have normal url's (see TIPServer.java). But for the sender,
what url do I use to send to multiple consumers?
--
View this message in context:
http://www.nabble.com/Duplicate-Messages-on-Listener-Restart-tp25440673p25452663.html
Sent from the ActiveMQ - User mailing
1 - 100 of 136 matches
Mail list logo
