I think there is some misunderstanding that I created. We don't plan to use
activemq to populate the cache. We build the cache on cache misses. Here's
how the overall flow looks like. Note there are multiple jvm's involved, I
have just pictured one for simplicity.
I didn't completely follow your r
Thanks Tim for your valuable comments.
1.
> so you're using message-driven code rather than managing the connection
> yourself. In that case you'd want to do the following to handle the error
> (by clearing the cache):
> https://stackoverflow.com/questions/40654586/spring-jms-set-errorhandler
Any thoughts on how to control the polling interval and other queries
mentioned below?
Thanks!
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Highly appreciate the detailed replies and the clarifications on distributed
cache vs database.
We are trying to build a distributed cache. I agree to all the inputs you
shared for such a cache implementation. In summary it would mean
1. Subscriber should clear the cache when it cannot conn
Thanks for the replies.
Below are my comments on the discussed topics
> Have you considered using an actual standalone caching product such as
> Redis or MemCache as your cache rather than trying to create your own
> synchronized distributed in-memory cache?
That was the first thought but sinc
I would like to revive this email thread since I have a exact similar use
case for which I am planning to use activemq - to keep the java objects in
sync between multiple nodes. This thread discusses a couple of approaches -
transacted session (does this refer to transactions?) or acknowledgements
We plan to use activemq to build a replicated cache in our distributed system
consisting of multiple java applications. In this deployment, an update to
any of the objects being cached in the jvm memory of the app server acts as
a producer which pushes the pojo to the jms topic. All other app serve
In our application we use guava eventbus along with activemq to implement
event based requirements between two web applications. Events are being
published and subscribed by different components of thw two web
applications. For receiving a message published by a component of a
different web applica