> 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 intricacies of the 5.x broker in this use-case, but from what I recall Artemis does all the things you want here (and there's no need to use JMSXGroupID). Justin On Fri, Oct 13, 2017 at 2:32 PM, pypen <py...@gmx.net> wrote: > 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 > no local consumer is running)? And if the local consumer starts again to > send all messages to the local consumer? It looks like the JMSXGroupID > seems > to work for the case that the local consumer receives the first message and > all following messages will be delivered to that same consumer, until this > consumer is stopped. The problem is that once another (remote) consumer is > "pinned", the local consumer will not receive messages until that remote > consumer is stopped. > > > > -- > Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User- > f2341805.html >
