2 Replies Latest reply on Jan 6, 2006 10:54 PM by Dan G

    CacheLoader data eviction?

    Dan G Newbie

      Do nodes get removed from the CacheLoader when they hit maxAgeSeconds?

      Thanks,
      Dan

      [It looks like part of my problem is that things aren't getting cleaned up from the CacheLoader, so Bdbje gets slower and slower, and eventually writes seem to timeout. I assume this only happens with AsyncCacheLoader b/c multiple threads must get queued up to wait for a lock.]

        • 1. Re: CacheLoader data eviction?
          Ben Wang Master

          No, it does not. Eviction just evict data in-memory. It will still keep the persistent data. You will need to issue remove explicitly. That makes sense right? Otherwise, why do you need persistency?

          -Ben

          • 2. Re: CacheLoader data eviction?
            Dan G Newbie

            Thanks Ben. I was just counting on persistence between invocations of Java but that if the object itself timed out, it would disappear. If I call treecache.remove(), I assume it will be removed from the persistent store, so perhaps I should catch an event when the node is being timed out (and also run through all the nodes at startup).

            Or, better yet:

            I still get the same timeouts if I add a je.properies to my WEB-INF/classes dir that contains je.lock.timeout=[LARGE NUMBER]. It seems to be ignored. Is there any way to crank up the timeouts for BDBJE?

            Thanks,
            Dan