[infinispan-dev] putForExternalRead and stale locks

[Manik Surtani]

I presume you're specifically referring to the 2nd level cache adapter in Hibernate?  If so, and if there is some other guarantee higher up in Hibernate to ensure data isn't overwritten, then yes, that flag should be used but only when invoked from Hibernate's 2LC.

On 31 Oct 2012, at 17:04, Sanne Grinovero <sanne at infinispan.org> wrote:

> Wouldn't it be reasonable to expect users of putForExternalRead() to
> use SKIP_LOCK combined with it?
> 
> On 31 October 2012 16:05, Manik Surtani <manik at jboss.org> wrote:
>> Guys
>> 
>> Someone's reported https://issues.jboss.org/browse/ISPN-2426 which can cause a stale lock when using putForExternalRead() in a non-transactional context.
>> 
>> The contributed patch looks good, I'm submitting a pull request - but a question to the Hibernate and AS folks on the list, I presume this is something you are both exposed to?  Or do you only use putForExternalRead() in a transactional context?
>> 
>> Cheers
>> Manik
>> --
>> Manik Surtani
>> manik at jboss.org
>> twitter.com/maniksurtani
>> 
>> Platform Architect, JBoss Data Grid
>> http://red.ht/data-grid
>> 
>> 
>> _______________________________________________
>> infinispan-dev mailing list
>> infinispan-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/infinispan-dev
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev

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

Platform Architect, JBoss Data Grid
http://red.ht/data-grid