I've opened a JIRA for this, mostly about the semantic with INVALIDATION_ASYNC:
https://jira.jboss.org/jira/browse/JBCACHE-1559
With INVALIDATION_SYNC, I wasn't too clear. Neither transaction is going to
succeed in putting the cache in a consistent state. That fact needs to
propagate to the
The 0 ms is coming from MVCCLockInterceptor:
|@Override
|public Object handleInvalidateCommand(InvocationContext ctx,
InvalidateCommand command) throws Throwable
|{
| // this should be handled the same as a recursive evict command.
|
Thank you, good point. But I in case of invalidation and the situation you
described I would expect that the timeoutexception would not be thrown to the
caller.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4267583#4267583
Reply to the post :
In debugger i see that inside MVCCHelper.acquireLock:159 invocation context's
option overrides the value of lockAcquisitionTimeout to zero, even though for
testing sake i explicitly set it to non-zero. What is more interesting, is that
in the main thread a second later i can still see my
In my case i see that two jvms are each trying to update the same set of nodes,
however i have lockAcquisitionTimeout=20 so I expected that they would
have at least waited that long before freaking out.
View the original post :
We are using Tree cache 1.4.1SP11 and getting simmilar excption
| 2009-11-16 09:33:31,435] [WARN ] [org.jboss.cache.TreeCache] replication
failure with method_call _evict; id:8; Args: ( arg[0] =
///masterdata/active
| BarcodeTypeList) exception
|
I can't believe I am the only one facing this problem. There has to be some
problem with the way jboss cache handles JTA transactions. I was able to get
the same problem with running one instance inside resin and enother on jotm.
View the original post :
Hi,
Any ideas as to what might be causing it this problem?
Thank you.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4265979#4265979
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4265979
apologies, the log was too long for forum. This is shorter version before the
exception:
| Nov 14 18:49:13,194 [main] TRACE
EvictionInterceptor:registerEvictionEventToRegionManager:254 - Registering
event ADD_ELEMENT_EVENT on node /hphRTp4/0:0_2
| Nov 14 18:49:13,194 [main] TRACE
