This week's book giveaway is in the Testing forum. We're giving away four copies of The Way of the Web Tester: A Beginner's Guide to Automating Tests and have Jonathan Rasmusson on-line! See this thread for details.
So we have a system that uses ehcache, and we'd like to start doing some clustering...
A casual effort was made a while back, but kind of stumbled with some poor implementation (specifically, coded behaviors that tended to dump too much of the cache for minor updates) and now I'm being assigned getting the beasts up and running, about 10 caches in all.
I have looked through the User's Guide but probably not as carefully (yet) as I should
1. Ok, naive question: a "Put" shouldn't trigger a notification to the peers, but an "Update" should? So you can use Puts when initially populating a cache, but Updates for when there is a change to data that the peers might have a (now stale) copy of
2. Does multicast need to be enabled on a network if the two peers are on the same server? I think currently multicast is disabled - but that's mostly just needed for "discovery", correct?
3. I set up the ehcache-debugger... I thought that when the manual said "An easy way to tell if your multicast is getting through is to use the Ehcache remote debugger and watch for the heartbeat packets to arrive." that when I saw repeated
Cache: [CacheName] Notifications received: 0 Elements in cache: 0
that was the heartbeat that meant that the communication was happening, but I guess this could just be a form of the FAQ :
36.33 I am using the RemoteDebugger to monitor cluster messages but all I see is "Cache size: 0"
Can you use the remote debugger in manual discovery mode?