2 Replies Latest reply on Jan 1, 2005 6:24 AM by rino_salvade

    JBossCache & durable subscription & resynchronisation

    rino_salvade

      We would like to implement a distributed system based on JBossCache and JMS as a procoll. The point is now that the caches need to resynchronize again after one of the machines was down. The idea was to use a durable subscription of a JMS topic (createDurableSubscription) so that no messages get lost. Having had a look at the JGroups code of the JMS protocol this seems not to be part of the implementation. Is there a standard or better way to perform this behaviour than our idea?

        • 1. Re: JBossCache & durable subscription & resynchronisation
          belaban

          There is: use JBossCache in replicated mode with JGroups doing the replication, *and* use a shared or non-shared CacheLoader.

          This way you have (in-memory) replication, but you also have persistence.
          Bela

          • 2. Re: JBossCache & durable subscription & resynchronisation
            rino_salvade

            Ok, this would solve the problem of a restart of a cache, because then it would retrieve the information from the cacheloader. But what happens if we have, let's say, a short network interrupt. To my understanding of the cache loader this would not be noticed and changes which happen during this time will not be replicated. Are those network exceptions somehow propagated to the cache so that they can be handled, especially the reconnect?
            I think, that without a durable JMS subscription there will still be situation where we miss cache changes. Or did I miss something