Thanks for the Jira and test code. I'll look at it.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Same-message-redelivered-to-multiple-consumers-after-failover-tp4678640p4679184.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Same-message-redelivered-to-multiple-consumers-after-failover-tp4678640p4679176.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
;t get this problem when sending "activemq stop" from from command line.
>
>
>
> If you reply to this email, your message will be added to the discussion
> below:
> http://activemq.2283324.n4.nabble.com/Same-message-redelivered-to-multiple-consumers-after-failover
;activemq stop" from from command
line.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Same-message-redelivered-to-multiple-consumers-after-failover-tp4678640p4679064.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
n);
brokerThread.start();
}
public TestProducer() {
super();
}
}
Thanks!
gtully wrote
> Can you share your code?
> On 12 Mar 2014 17:40, "gregg" <
> garlakg@
> > wrote:
--
View this message in context:
till get the same problem.
> >>
> >> Would have to do some more testing to change the way the message is
> >> produced
> >> to potentially isolate the cause.
> >>
> >>
> >> artnaseef wrote
> >> > Is it possible the listeners are rejecting the message? T
testing to change the way the message is
>> produced
>> to potentially isolate the cause.
>>
>>
>> artnaseef wrote
>> > Is it possible the listeners are rejecting the message? That could
>> > explain the results you are seeing.
>>
>>
sults you are seeing.
>
>
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Same-message-redelivered-to-multiple-consumers-after-failover-tp4678640p4678674.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
com/Same-message-redelivered-to-multiple-consumers-after-failover-tp4678640p4678674.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Is it possible the listeners are rejecting the message? That could explain
the results you are seeing.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Same-message-redelivered-to-multiple-consumers-after-failover-tp4678640p4678664.html
Sent from the ActiveMQ - User
> Apologies if I misunderstood something ;-)
>>
>> Regards,
>>
>> *Raúl Kripalani*
>> Apache Camel PMC Member & Committer | Enterprise Architect, Open Source
>> Integration specialist
>> http://about.me/raulkripalani | http://www.
Kripalani*
> Apache Camel PMC Member & Committer | Enterprise Architect, Open Source
> Integration specialist
> http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
> http://blog.raulkr.net | twitter: @raulvk
>
>
> If you reply to this email, your
Hi Gary,
On Fri, Mar 7, 2014 at 4:41 PM, Gary Tully wrote:
> that is expected. with the caveat that you would need to repeat a few
> times to get it delivered to all the consumers.
>
Why is this? If I understood correctly, the OP reported that the same
message on a queue got redelivered to *all
am I missing some key broker configuration?
>
> Thanks,
>
> Greg
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Same-message-redelivered-to-multiple-consumers-after-failover-tp4678640.html
> Sent from the Active
approach, or
am I missing some key broker configuration?
Thanks,
Greg
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Same-message-redelivered-to-multiple-consumers-after-failover-tp4678640.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
15 matches
Mail list logo
