Thanks a lot Tim . The config with ackBatchSize indeed worked .I saw the reference to this parameter in the doc but thought this might be not relevant to our setup .Federationactivemq.apache.orgBest regards,Saju DanielOn 1. Jul 2024, at 20:53, Timothy Bish wrote:On 6/26/24 06:56, Saju Daniel wro
On 6/26/24 06:56, Saju Daniel wrote:
Hello,
Just a gentle reminder. The issue is kind of critical for us to
implement federation on our setup .
Please let me know if you need more information on the problem.
After talking to Justin Bertram about some core client details I tried
your setup an
Hello ,
Are there any update on the issue ? If its confirmed to be a known
limitation with our configuration, we would like to find a workaround to
move forward with our federation setup.
Any tips in this regards would be greatly help us . Thank you.
FYI , Unfortunately AMQP is not an option for
Hello,
Just a gentle reminder. The issue is kind of critical for us to implement
federation on our setup .
Please let me know if you need more information on the problem.
Regards,
Saju
On Tue, 25 Jun 2024 at 16:50, Saju Daniel wrote:
> Hello Tim ,
>
> The issue seems to be easy to reproduce.
On 6/24/24 02:56, Saju Daniel wrote:
Hello Tim ,
Were you able to reproduce the issue with the messages in Delivering state
in the federated queue ?
Please let me know if you need more information .
I have not seen a reproducer provided so I have not looked into this
further.
My suggestion
Hello Tim ,
Were you able to reproduce the issue with the messages in Delivering state
in the federated queue ?
Please let me know if you need more information .
Regards,
Saju
On Fri, 21 Jun 2024 at 11:57, Saju Daniel wrote:
> Hello ,
>
> I tried out the same scenario with the version 2.35 and
Hello ,
I tried out the same scenario with the version 2.35 and still see the issue
that federated queue shows the message in delivering state even though its
correctly delivered at the other end .
I hope you are able to reproduce this at your end as well.
For illustration below is the status at
On 6/20/24 12:50, Saju Daniel wrote:
Hello Tim,
Thanks for the reply . We figured out the reason for duplicate message .
It was caused by the wildcard entry we used on federation configuration . This
was because the wild card address was also an address queue on the Europe
cluster. i.e events
For what it's worth, the latest version is currently 2.35.0 [1].
Justin
[1] https://activemq.apache.org/components/artemis/download/
On Thu, Jun 20, 2024 at 1:14 PM Saju Daniel wrote:
> We are using the the latest version of activemq . 2.33 . Forgot to mention
> this
>
> Best regards
> Saju D
We are using the the latest version of activemq . 2.33 . Forgot to mention this
Best regards
Saju Daniel
> On 20. Jun 2024, at 18:50, Saju Daniel wrote:
>
> Hello Tim,
>
> Thanks for the reply . We figured out the reason for duplicate message .
>
> It was caused by the wildcard entry we use
Hello Tim,
Thanks for the reply . We figured out the reason for duplicate message .
It was caused by the wildcard entry we used on federation configuration . This
was because the wild card address was also an address queue on the Europe
cluster. i.e events.#.
The consumer at the USA ends up re
On 6/19/24 14:33, Saju Daniel wrote:
Hello All ,
We see duplicated message at the consumer end on USA federation with a
symmetric federation setup as described here -
https://activemq.apache.org/components/artemis/documentation/2.20.0/federation-address.html
The configuration is described in t
Hello All ,
We see duplicated message at the consumer end on USA federation with a
symmetric federation setup as described here -
https://activemq.apache.org/components/artemis/documentation/2.20.0/federation-address.html
The configuration is described in the stackoverflow query here:
https://s
13 matches
Mail list logo
