At the time we strongly suspected a deadlock caused by the local puts placing cached items back into the local memory caches when they recieved async put events from the remotecache.
Could the deadlock we were seeing when using remotePuts have been the same thing? We are quite keen to try remotePuts again as this functionality would be very useful to us (would allow iteration over whole caches on individual machines). As the deadlock was only occuring under high load we don't have a reliable way to test.
Any advice appreciated!
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
