I've been working on some state transfer/virtual cache view
improvements: ISPN-1606. I'll have a pull request up in an hour.
Dan
On Thu, Dec 15, 2011 at 8:58 PM, Galder Zamarreño gal...@redhat.com wrote:
On Dec 15, 2011, at 2:21 PM, Vladimir Blagojevic wrote:
If someone can deal with my
This is why you shouldn't use the assert keyword in tests, much better to use
the Assert class functions :-)
On 16 Dec 2011, at 10:07, Mircea Markus wrote:
Thanks for the tip.
I think we should add a test that check that assertions are enabled so that
you get the feedback on this issue
Hi,
See below
On Fri, Dec 16, 2011 at 06:57, Galder Zamarreño gal...@jboss.org wrote:
On Dec 15, 2011, at 11:15 PM, Slorg1 wrote:
I am thinking of something evil and wonder what you think about that.
I am supposing the fail silently code + solution #3.
tx1 |
1. tx2 read data1.
2. it performs a PFER with fails for some random reason. With the new
code you put in, that does not rollback the tx and continue as though
nothing happened.
it's not only with the new code, that's part of PFER's contract.
Or do you need something that would force an
Hi,
On Fri, Dec 16, 2011 at 11:59, Mircea Markus mircea.mar...@jboss.com wrote:
1. tx2 read data1.
2. it performs a PFER with fails for some random reason. With the new
code you put in, that does not rollback the tx and continue as though
nothing happened.
it's not only with the new code,
