[infinispan-dev] PutForExternalRead and autoCommit

[Manik Surtani]

On 17 Nov 2011, at 09:30, Galder Zamarreño wrote:

> Hi,
> 
> Forcing caches to be either transactional or non transactional caches causes some issues with operations such as putForExternalRead with default configuration options.
> 
> Assuming we have a transactional cache, if autoCommit is on (default), putForExternalRead will:
> 1. Suspend the ongoing transaction
> 2. Will create a brand new transaction due to implicit transaction creation logic in auto commit.
> 
> This is not good.

What's not good about this?  1 is by design and is correct behaviour.  2 should not affect anything, since the new tx is completed at the end of the PFER invocation.

Cheers
Manik

--
Manik Surtani
manik at jboss.org
twitter.com/maniksurtani

Lead, Infinispan
http://www.infinispan.org