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 <jbert...@apache.org> 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 consumer stops then the queue will likely be removed so you won't have any message accumulation in that case. Justin On Wed, Jul 24, 2024 at 9:05 AM Edson Richter <edsonrich...@hotmail.com> wrote: > 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 a Json message with data to an address, > and then several queues receive a copy of that message (it’s the > purpose of multicast, right?). > 3. Each queue will have an aggregator service as consumer, where > each service receiving the messages generate one (of dozens) of real > time indicators (It’s a kind more complex than that). > 4. If one consumer is stopped, the respective queue will continue > to receive the messages until the service is restarted. > > Thanks in advance, > > ER. > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@activemq.apache.org For additional commands, e-mail: users-h...@activemq.apache.org For further information, visit: https://activemq.apache.org/contact
