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 to detect loss).
Thinking about this problem leads me to thinking of hazelcast and others, which then makes me wonder why you're implementing a distributed cache as there are awesome toolsets for that very use-cache. Ehcache is definitely one. I believe hazelcast is another. Something to consider. The biggest concern that comes to mind using JMS for this purpose is the time it takes for messages to distribute to all the consumers which raises the question, "how bad is it if one of the cache copies is out of date for any length of time?" -- View this message in context: http://activemq.2283324.n4.nabble.com/Depending-on-TransportListener-for-cache-consistency-tp4700535p4701174.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
