Hi Domenico,
Will investigate your enhancement, could be the answer!
Thanks,
Dave
On Fri, Jul 23, 2021, 1:37 PM Domenico Francesco Bruscino, <
bruscin...@gmail.com> wrote:
> Hi David,
>
> it could be a timing issue, when a first client connects to a broker, it
> sends a notification to other
Hi Tim,
I get your point but they are third parties.
I understand the problem will have to write a plug-in I think..
Dave
On Fri, Jul 23, 2021, 10:08 PM Tim Bain, wrote:
> Maybe I'm oversimplifying this, but isn't the client required to use a
> unique client ID, and we're splitting hairs over
Maybe I'm oversimplifying this, but isn't the client required to use a
unique client ID, and we're splitting hairs over the exact undefined
behavior that occurs when something invalid is done? It seems like the real
solution is to modify the client applications to make them use unique
client IDs, n
Hi David,
it could be a timing issue, when a first client connects to a broker, it
sends a notification to other brokers of the cluster. So if a second client
with the same clienID connects to another broker of the cluster before it
receive the notification, the second broker accepts the connectio
Hi Domenico,
OK thanks I'll have a look at that.
Was considering writing a plugin to block authorisation when the same
client ID is already connected elsewhere on the cluster, with leader
election via a multicast queue.
I'm puzzled why it's behaving this way though. It's not consistent. Usually
Hi Dave,
I'm working on a new ActiveMQ Artemis feature that allows users to
balance incoming client connections according to their ClientID (or other
connection parameters), see the draft documentation[2] for further details.
[2]
https://github.com/brusdev/activemq-artemis/blob/broker_balancers/d
Hi all,
Puzzled by some behaviour we're seeing on a broker cluster of 3 live
Artemis v2.16.0 brokers hosted on k8s which has an F5 in front of it
terminating TLS and routing to a k8s node port forwarding to an AMQP
acceptor for each broker. The cluster is healthy and has been up for about
2 months
