Hi, sorry for the late response.
1) Red Hat does offer paid support for JBoss Cache as a part of the JBoss EAP
subscription.
2) Interesting that using the dummy TM solves the problem - it is still a real
TM capable of holding real locks. It's just that other components in the app
server won'
According to the "MVCCLockManager" api:
(http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs/3.1.0.CR1/apidocs/org/jboss/cache/lock/MVCCLockManager.html
anonymous wrote : Boss Cache's MVCC design doesn't use read locks at all.
Really?
Then why are the writers waiting for
If we change the EJB to
@TransactionAttribute(value=TransactionAttributeType.NEVER), then we can use
the GenericTransactionManager and it prevents the lockups.
So, why is it locking on a read?
Also, since this cache is supposed to persist until explicitly removed we've
commented the node.
Ot
BTW we are using "JBossCache 'Cascabel' 3.1.0.GA"
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4245679#4245679
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4245679
___
jboss
