We will not be using a network of brokers, due to the possibility of
persistent messages getting undelivered after a failover (not sure if
"orphaned" is a better term?) due to this issue:
https://issues.apache.org/jira/browse/AMQ-5897
We are using a shared filesystem master/slave setup. We are w
There are other concerns as well. For example, when using a network of
brokers, topic messages can be lost if a network connection between brokers
goes down, even just for an instant, and there's no way for the applications
to detect this loss (unless your messages have something that can be used
You raise some valid-sounding concerns: specifically the information that
there can be message loss for non-durable subscriptions even in the absence
of a connection failure or broker failure.
Our cached items remain cached for extended periods, so we'd in trouble if
we miss a cache message for an
I don't know the exactly details of your use case but this seems reasonable
to me as long as you account for the fact that messages could still be lost
or not received in a timely matter even if there isn't a broker restart or
lost connection. An example where a message could be lost is if the top
