Re: [infinispan-dev] Stale locks: stress test for the ReplaceCommand
Yes I was running on master as of 5cf3494a3ccd59eb7675c2caff4a7f0b75f244c5
It's trivial to cherry-pick the test where you want, as I didn't
change any code and it just adds the single file needed for the test.
I don't have TRACE logs enabled, no; you're very welcome to run it in
all modes you want.
On 30 October 2012 14:29, Mircea Markus <mircea.markus(a)jboss.com> wrote:
So the fix for ISPN-2381 is not complete?
That's unclear, there might be multiple subtle problems going on.
ISPN-2381 might be resolved, seems there are more issues of similar
nature.
This test started as a testcase for ISPN-2435 (also quite critical
imho), but now I'll track this new locking problem separately:
ISPN-2453
Cheers,
Sanne
On 30 Oct 2012, at 14:09, Manik Surtani wrote:
On 30 Oct 2012, at 14:00, Sanne Grinovero <sanne(a)infinispan.org> wrote:
Funnily enough while writing this it just failed a run even in single
thread mode: in one iteration it was spotted that the lock wasn't
cleaned up; this was REPL_SYNC+TX;
I find this particularly concerning, but also potentially easy to debug. Do
you have TRACE logs from this run? And I presume this is on master, with
the fix for ISPN-2381 in?
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
Cheers,
--
Mircea Markus
Infinispan lead (www.infinispan.org)
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev