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(a)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(a)jboss.org
twitter.com/maniksurtani
Platform Architect, JBoss Data Grid
http://red.ht/data-grid
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev