stomp+ActiveMQ with SSL

This might help you This is the nature of a Queue, only one subscriber will get a message placed on a Queue, if you want message broadcast then you want to subscribe to a Topic.
Queue vs Topic

seems to work fine Generally you wouldn't be using websockets on the server side, just connect using a normal STOMP or OpenWire connection.
That siad, looking at your code you appear to be using the ActiveMQ JMS client which speaks neither STOMP nor Websockets so you are doomed to failure. The ActiveMQ JMS client uses the OpenWire protocol and can connect via TCP or SSL (HTTP can work to with the right jar).

it fixes the issue I examined the client code (ruby stomp client) and it turned out that there was 'activemq.subscriptionName' sub header without 'client-id' connect header. When you set 'activemq.subscriptionName' subscription header that means that you want your subscriber to be durable. But you should also set 'client-id' connect header because otherwise it is autogenerated. When 'client-id' header is not set we have a situation in which the broker can't identify the stomp client by it's client id when it reconnects. As a result there were a lot of Offline Durable Topic Subscribers and messages were piling up for every client-id => OOM error.

I wish this helpful for you I've run into the same problem with the embedded ActiveMQ server in my project. Turns out I needed to add the following dependencies to my pom.

With these it helps The Python STOMP client (as of version 4.1.20) uses an SSLContext to process its key pair/certificate, so there is no reason to produce a Java KeyStore for the client.
With this in mind, let us go through the entire process of setting up ApacheMQ to support SSL-wrapped STOMP connections. The process below has been tested on ApacheMQ 5.15.4. We explicitly set up two-way trust by manually moving self-signed certificates between the broker and client; using a certificate authority is also possible but how to do so is a different question.