message-counter | Message Counter Android App Tracks the number of Text | SMS library

Looking through the code of the Python SDK (the Azure Service Bus client library for Python), it appears that there's a ServiceBusAdministrationClient that has a get_queue_runtime_properties method.

You have defined "anycastPrefix=jms.queue;multicastPrefix=jms.topic." in your SSL acceptor. You should remove them. Another solution is to setEnableAmq1Prefix to false on your connection factory (but i think this is the default value)

You need to configure (or add) your acceptor with sslEnabled and the keystore/truststore to use.

ActiveMQ Artemis is failing because the bind attribute of the web element is using the HTTPS protocol:

Apache ActiveMQ Artemis clients receive knowledge of all live and backup servers after connecting, so that in event of connection failure at the client - live server connection, the client will detect this and reconnect to the backup server. This means that using only masters in the boker url could work but what would happen if none of the masters is live?

The client would not be able to connect, so adding the backups to the boker url would allow the client to connect when none of the masters is live.

I would start by putting a property in each message that will allow it to be uniquely identified and then logging that value so you can correlate client and broker logs later. If you're using JMS then you can use something like this:

I set up a simple pair of brokers using replication and the "Broker Diagram" displays both the master and the slave as expected: Ensure you have the "Show Backup Brokers" checkbox selected.

Regarding the SSL issue, see the upgrade instructions for 2.18.0 in the documentation:

...core clients will now expect the CN or Subject Alternative Name values of the broker's SSL certificate to match the hostname in the client's URL.

...

To deal with this you can do one of the following:

• Update your SSL certificates to use a hostname which matches the hostname in the client's URL. This is the recommended option with regard to security.

• Update any connector using sslEnabled=true to also use verifyHost=false. Using this option means that you won't get the extra security of hostname verification, but no certificates will need to change. This essentially restores the previous default behavior.

ActiveMQ Artemis has no default connection limit. I just wrote a quick test based on this which uses the Paho 1.2.5 MQTT client. It spun up 500 concurrent connections using both normal TCP and WebSockets. The test finished in less than 20 seconds with no errors. I'm just running this test on my laptop.

I noticed that your journal-buffer-timeout is 700000 which seems quite high which means you have a very low write speed of 1.43 writes per millisecond (i.e. a slow disk). The journal-buffer-timeout that is calculated, for example, on my laptop is 4000 which translates into a write-speed of 250 which is significantly faster than yours. My laptop is nothing special, but it does have an SSD. That said, SSDs are pretty common. If this low write-speed is indicative of the overall performance of your VM it may simply be too weak to handle the load you want. To be clear, this value isn't related directly to MQTT connections. It's just something I noticed while reviewing your configuration that may be indirect evidence of your issue.

The journal-buffer-timeout value is calculated and configured automatically when the instance is created. You can re-calculate this value later and configure it manually using the bin/artemis perf-journal command.

Ultimately, your issue looks environmental to me. I recommend you inspect your VM and network. TCP dumps may be useful to see perhaps how/why the connection is being reset. Thread dumps from the server during the time of the trouble would also be worth inspecting.

I've taken your simplified configured with just 2 nodes using a non-wildcard queue with redistribution-delay of 0, and I reproduced the behavior you're seeing on my local machine (i.e. without Kubernetes). I believe I see why the behavior is such, but in order to understand the current behavior you first must understand how redistribution works in the first place.

In a cluster every time a consumer is created the node on which the consumer is created notifies every other node in the cluster about the consumer. If other nodes in the cluster have messages in their corresponding queue but don't have any consumers then those other nodes redistribute their messages to the node with the consumer (assuming the message-load-balancing is ON_DEMAND and the redistribution-delay is >= 0).

In your case however, the node with the messages is actually down when the consumer is created on the other node so it never actually receives the notification about the consumer. Therefore, once that node restarts it doesn't know about the other consumer and does not redistribute its messages.

I see you've opened ARTEMIS-3321 to enhance the broker to deal with this situation. However, that will take time to develop and release (assuming the change is approved). My recommendation to you in the mean-time would be to configure your client reconnection which is discussed in the documentation, e.g.: