Am trying to understand some intermittent lock timeout exceptions we are seeing. These could be related to the LRU eviction policy thread not able to acquire a lock as it seems to timeout after 0ms and not 15000ms as it is specified in the 15000 attribute. If these are more informational i.e. eviction will occur in the next go around, can we log them differently. Or what can we do to set a timeout, etc. for these? Version: 1.4.1GA on Linux Here is the trace: .... at org.jgroups.blocks.RequestCorrelator.receive(RequestCorrelator.java:358) at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.up(MessageDispatcher.java:775) at org.jgroups.JChannel.up(JChannel.java:1091) at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:377) at org.jgroups.stack.ProtocolStack.receiveUpEvent(ProtocolStack.java:393) at org.jgroups.stack.Protocol.passUp(Protocol.java:538) at org.jgroups.protocols.pbcast.STATE_TRANSFER.up(STATE_TRANSFER.java:158) at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:488) at org.jgroups.stack.Protocol.passUp(Protocol.java:538) at org.jgroups.protocols.pbcast.GMS.up(GMS.java:771) at org.jgroups.stack.UpHandler.run(Protocol.java:60) Caused by: org.jboss.cache.lock.TimeoutException: read lock for /user/name-id could not be acquired by Thread[UpHandler (GMS),5,JGroups threads] after 0 ms. Locks: Read lock owners: [] Write lock owner: null , lock info: (activeReaders=0, activeWriter=null, waitingReaders=0, waitingWriters=0, waitingUpgrader=0) at org.jboss.cache.lock.IdentityLock.acquireReadLock(IdentityLock.java:261) at org.jboss.cache.Node.acquireReadLock(Node.java:512) at org.jboss.cache.Node.acquire(Node.java:474) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157450#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...