[jbosscache-users] Lots of TimeoutException when calling Cache#get()

Hi, I've been getting a lot of TimeoutExceptions when the method Cache#get() is called. My cluster is set up as below: 0. The cluster runs on JBoss Cache 3.1.0 GA. The locking scheme is MVCC. The isolation level is READ_COMMITTED. 1. Two nodes, N1, and N2. Each node is a different machine. Each node has a cache instance. 2. The node N1 only reads from cache. If it doesn't find an entry from its local cache, it will read from N2 via a ClusteredCacheLoader. The ClusteredCacheLoader is asynchronous, but its serialization thread pool size is 0 (it would not work otherwise for some reason) 3. The node N2 both reads from and writes to its cache. If I understand it correctly, a read operation doesn't not aquire a lock, let alone a write-lock. So, why would I get many TimeoutExceptions when Cache#get() was called, as the stack trace shows? Could anyone please let me what possibly could cause this problem? Another interesting thing is, this problem was not seen during peak load. It happened when load was really low as if it would only happen after the system has been running for a while. org.jboss.cache.lock.TimeoutException: Unable to acquire lock on Fqn at org.jboss.cache.mvcc.MVCCNodeHelper.acquireLock(MVCCNodeHelper.java:157) at at at at at at at at at at at at at at at at at at at at at at at at at at at at I also noticed quite many RejectedExceptions when there were many TimeoutExceptions. Are they somehow correlated? java.util.concurrent.RejectedExecutionException at at at at at at at at at at at at at at at at at at at at at at at at at at at at at at at at at at at at at Thanks, Yong