I have a jboss cache cluster with 2 nodes. When one of the nodes is over-loaded
or is running into OOM issues, the other node also becomes non-responsive. A
thread dump on the (non-OOM) instance shows jboss cache threads waiting on a
lock (excerpt below).
Do I need to tweak the failure detectio
You are right. We are using INVALIDATION_SYNC.
I think for now I will switch over to using REPL_[A]SYNC instead and plan to
upgrade to 2.x later.
Thanks
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157533#4157533
Reply to the post :
http://www.jboss.com/
Brian,
Thanks. Here you go:
INFO 2008-06-11 18:50:34,071 UpHandler (GMS) U-
org.jboss.cache.interceptors.TxInterceptor - There was a problem handling this
request
org.jboss.cache.lock.TimeoutException: failure acquiring lock: fqn=/user/id,
caller=Thread[UpHandler (GMS),5,JGroups threads], l
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.