A multicast address is something you configure on the ActiveMQ Artemis
broker. See more details in the documentation [1].
Justin
[1] http://activemq.apache.org/artemis/docs/latest/address-model.html
On Sat, Aug 12, 2017 at 5:36 PM, Lionel van den Berg
wrote:
> I can be flexible on the protoc
I can be flexible on the protocol. Currently we are using openwire.
For the option of a multicast address, is this an activemq configuration or
network configuration? OK, it's in activemq and there is some
documentation, I'll get to ready. At first glance it seems there are some
limitations, but i
> (2) both instance #1 and instance#2 were processing the messages, and
shut down instance #1 in the middle
Are you saying that the live and backup brokers were both active at the
same time?
Do you have a reproducible test-case I could use to observe exactly the
behavior you're describing? If no
What client protocol/API are you going to be using?
I think you could accomplish what you're after by using a multicast address
with multiple last-value queues which represent all your workstations. How
you access those will depend on what protocol/API you decide to use.
Justin
On Fri, Aug 11,
Sounds like you're on the right path.
If you're worried about being constrained by your available memory but
don't want to restrict your producers and the fast application, you could
send the messages to a persistence store on disk instead, to allow you to
store more of them.
Tim
On Aug 11, 2017
