ing STOMP with durable messages, no
> delete queues, no delete address.
>
> Regards,
>
> ER.
>
> -Mensagem original-
> De: Justin Bertram
> Enviada em: quarta-feira, 24 de julho de 2024 11:44
> Para: users@activemq.apache.org
> Assunto: Re: AMQ Multi-cast beh
Perfect, I forgot to mention, we are using STOMP with durable messages, no
delete queues, no delete address.
Regards,
ER.
-Mensagem original-
De: Justin Bertram
Enviada em: quarta-feira, 24 de julho de 2024 11:44
Para: users@activemq.apache.org
Assunto: Re: AMQ Multi-cast behavior
As far as ActiveMQ Artemis is concerned all your assumptions look to be
correct for the most part.
Number 4 is somewhat questionable depending on what exactly the client is
doing. If, for example, it's using the JMS API and creating a non-durable
subscription to receive messages then when the cons
Please, tell me if any of my assumptions are wrong:
1. I have a data analysis streaming project using AMQ as temporary store. I
know, most projects use Kafka, but in our company, AMQ is standard tool for
everything “inter services communication”, and I love it 😊 .
2. One service will send
