On 15 Jul 2013, at 16:27, Ales Justin <ales.justin(a)gmail.com> wrote:
So you're saying that while this state transfer was going on,
some other process (another thread) changed this value?
The functionality I've described is not related to the state transfer in particular,
but has to do with how optimistic transactions work.
Was there a state transfer in progress anyway? (hard to determine that from the thread
dump)
Any way to avoid this?
Global lock is fine, for now.
You can always disable write skew check (<locking
writeSkewCheck="false"/>) . That would allow the transaction to succeed even
if the value has changed in between the read time and commit time. But that's only if
your application can live with that, i.e. an application specific decision.
Cheers,
--
Mircea Markus
Infinispan lead (
www.infinispan.org)