I believe so..
I wouldn't use FAIL if you are using clustered redistribution...
I would probably set your policy as OFF_WITH_REDISTRIBUTION. And try
to have your consumers and producers on the same broker.
On Fri, Jun 16, 2023 at 10:48 AM Tapan Gupta <03.ta...@gmail.com> wrote:
>
> A bridge/clus
A bridge/cluster being stopped will affect all addresses rather than just
the one which had BLOCK policy?
Best Regards
Tapan Gupta
On Fri, 16 Jun, 2023, 16:11 Clebert Suconic,
wrote:
> With Block there are no retries involved.. the system will stop
> sending credits and the bridge will pause un
With Block there are no retries involved.. the system will stop
sending credits and the bridge will pause until more credits are sent.
With a bridge connected the best scenario would be BLOCK. I didn't
even consider it a bug, as I thought no one would be using a Bridge
with a FAIL policy.
But if
Thanks a lot for explaining.
Is the behaviour same if we use BLOCK instead of FAIL, i.e bridge producer
will be blocked so does that make bridge reconnect?
Will it be blocked for one address only or for all addresses?
Best Regards
Tapan Gupta
On Thu, Jun 15, 2023 at 4:56 PM Justin Bertram wrote
If sending fails then the bridge will attempt to reconnect according to its
configuration and send the message again. Of course, load-balancing and
redistribution will be impacted either way.
Ideally, in the time it takes for the bridge to reconnect consumers will
have acknowledged messages to fre
Hi,
Thanks for the quick reply.
What is the expected behaviour after the fix?
If I understood the change correctly the bridge will reconnect and try to
send the message again, will most probably fail again and continue doing
this?
Best Regards
Tapan Gupta
On Thu, Jun 15, 2023 at 3:38 PM Justin
This will be fixed in 2.29.0 via ARTEMIS-4313 [1].
Justin
[1] https://issues.apache.org/jira/browse/ARTEMIS-4313
On Thu, Jun 15, 2023 at 7:40 AM Tapan Gupta <03.ta...@gmail.com> wrote:
> Hi,
>
> We have 3 node symmetric cluster, with server side load balancing
> (ON_DEMAND) and message redistr
Hi,
We have 3 node symmetric cluster, with server side load balancing
(ON_DEMAND) and message redistribution enabled.
When using FAIL, we noticed that
amqp producers got an exception as expected, however the bridge connection
also got the exception and disconnected with below error. This affected
