[infinispan-dev] locking optimisations reloaded
Mircea Markus
mircea.markus at jboss.com
Fri Jun 17 05:30:00 EDT 2011
On 9 Jun 2011, at 20:39, Manik Surtani wrote:
> Regarding the comment on transactional versus non-transactional threads mentioned on https://issues.jboss.org/browse/ISPN-1137 - I think the fact that we allow this is a flaw.
>
> The approach we are taking with JSR 107 is such:
>
> 1) If a cache is non-transactional, transactional threads accessing the cache throw an exception.
> 2) If a cache is transactional, threads must have an ongoing transaction. If not, an exception is thrown, unless:
> 3) Auto-commit is configured to be true. In this case, if a non-transactional thread accesses the cache, a tx is started, work done, and the tx auto-committed.
+1. This requires an auto-commit option on the cache.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/infinispan-dev/attachments/20110617/38dd3214/attachment.html
More information about the infinispan-dev
mailing list