Here is what I am doing but my setup is a little different. I happen to be
using ActiveMQ Artemis. I am also in Master/Slave mode and behind a load
balancer. In ActiveMQ Artemis the slave will stop listening on the
necessary ports (5671 for me). My load balancer (which is not ELB) is
configured to
No, it should not be shared between brokers.
The temp store is for holding content that overflows from the memory store.
The memory store contains only non-persistent messages, which do not
survive a broker restart (or a failover), so the temp store should not
either.
Tim
On Oct 11, 2017 6:04 PM
I agree.
The fundamental problem you're hitting is that in ActiveMQ 5.x, a message
can exist in only one active broker, so networks of brokers move messages
around via store-and-forward, as you described. For a message to be
available to multiple brokers at the same time (such that it would still
Artemis does support this in a way via colocated lives and backups.
However, even then this is only valid for *persisted* messages. The title
of the original email indicates this is needed for *non-persistent*
messages. At least that's the way I understood it.
Justin
On Fri, Oct 13, 2017 at 7:
Can someone check this please.
I just wanted to know which library from "org." is being used here for MAP
messages as mentioned above.
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Hi all,
I'm using MQ 5.13.3 and I'm in the process of trying to setup userid access
to the web console. I've followed the instructions, I've found, to edit the
jetty.xml and import it into activemq.xml and then edited
jetty-realm.properties for userids and passwords. Yet, after I have bounc
Thank you both for your answers.
Yes, Justin, that's what I meant (non-persistent messaging).
I guess, I will have to look into different solutions.
Is it for example possible to force messages to be always sent to a local
consumer, if one exists, otherwise to a remote consumer (if one exists and
> Is it for example possible to force messages to be always sent to a local
consumer, if one exists, otherwise to a remote consumer (if one exists and
no local consumer is running)? And if the local consumer starts again to
send all messages to the local consumer?
I'm not familiar with the intrica
Persistent messages in artemis are pretty fast. You should consider
persistent.
The fact you need them reliable means you need them durable.
On Fri, Oct 13, 2017 at 3:32 PM pypen wrote:
> Thank you both for your answers.
> Yes, Justin, that's what I meant (non-persistent messaging).
>
> I guess
