The problem is described at JBPORTAL-1879 and I have narrowed down it to configuration
where this problem can be easily replicated.
It only happens when optimistic locking used with REPL_SYNC as cache_mode.
<attribute name="NodeLockingScheme">OPTIMISTIC</attribute>
| <attribute name="IsolationLevel">REPEATABLE_READ</attribute>
| <attribute name="CacheMode">REPL_SYNC</attribute>
|
Changing CacheMode to REPL_ASYNC or LOCAL as well as using Pessimistic locking does not
result into this problem. I think we need to look into following possibilities besides
looking into portal code base
1. Problem with org.hibernate.cache.OptimisticTreeCache or the way we are using it
2. Deadlock in org.jboss.cache.lock.ReadWriteLockWithUpgrade
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156792#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...