2 Replies Latest reply on May 24, 2006 1:27 PM by pnguyen45

    TcpDelegatingCacheLoader behaviour!

    pnguyen45

      Hi,

      I'm trying to using TcpDelegatingCacheLoader to set up my enviroment which has the primarry cache (loaded from file cache loader) and running as tree cache server. The secondary cache load cache from primary uses TcpDelegatingCacheLoader.

      Whenever my server (primary cache) is down, I cannot make any get object call from the secondary cache. Is this a true behaviour or am I missing something? I would assume that even the primary cache down, I can still work with the secondary?

      If this is the behaviour, is there any way to get around this?

      Thanks

        • 1. Re: TcpDelegatingCacheLoader behaviour!
          manik

          You should be able to make calls on the 'secondary' cache provided the data has been loaded into the memory of the secondary cache. If not, and it attempts to make a remote tcp call for this data, it will fail.

          • 2. Re: TcpDelegatingCacheLoader behaviour!
            pnguyen45

            Manik,

            Thanks for the response. Actually I have figured out my problem. My TCP server keep on changing the cache (every one minute) and since I'm using INVALIDATION_ASYNC, the node on the Secondary cache got evicted; hence when I call get() from the secnondary cache it will go to the cache loader to get the value instead of getting the value locally. Fixing the TCP server has fixed my problem.

            Thanks.

            Phi