Hi,

EHcache is a clusterable cache for a while. If I use EHcache as second level cache, and use read-write access strategy, but not in JTA environment, (means using tomcat server, not some application servers), will any operation unpredictable.

I've done some initial testing to verify the cache item does replicate to another cache instance in cluster (under the same multicast address).

In this hibernate documentation (http://docs.jboss.org/hibernate/stable/ ... ance-cache), it says "If you want to use this strategy in a cluster, you should ensure that the underlying cache implementation supports locking. The built-in cache providers do not support locking".

1. What kind of locking it refers to? I don't recall that ehcache has any API relates to locking?
2. If no such locking is provided at ehcache level, what inconsistent behavior we will see?
3. What happens if two DB updates just finish from two servers, and then both server will put the changes (older change into server1, newer change into server2) into cache at the same time? What will happen?

I look forward to your reply. Thanks.


Shaoxian Yang