By setting the isolation level to NONE, I got a different error. Its
stacktrace is below.
| java.lang.IllegalStateException: addWriter(): owner already existed
| at org.jboss.cache.lock.LockMap.addWriter(LockMap.java:112)
| at
org.jboss.cache.lock.IdentityLock.acquireWriteLock(Identi
One more piece of new information, there is obviously some deadlock going on
here. I increased the lock acquisition timeout time to 5 minutes and noticed
the following:
* the process stopped (did nothing) waiting for 5 minutes after about 500
simultaneous client requests
* after this timeout p
Additionally, I have noticed/tried the following:
* the lock acquisition timeouts seem only to occur while listing a given node's
children and the retrieving information from each of the children
* if the isolation level is set to READ_COMMITTED, the lock acquisition
timeouts completely go away
In 1.2.1, we use method-level locking (lock held for the duration of the method
call, ege. put()). if no TXs are used. Therefore set the TX-level to NONE
should solve this
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871675#3871675
Reply to the post :
htt
I thought it might be something like that, but should I get the
IllegalStateException that I got (shown above) when I did that?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871684#3871684
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=pos
I fixed this (http://jira.jboss.com/jira/browse/JBCACHE-117).
Will be available in JBossCache 1.2.2
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872000#3872000
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872000
-
