If you use isolation level of SERIALIZABLE, then the behvior you get is
incorrect ! Reads and writes should have exclusive locks.
Since we have tested that this works, please submit a short unit test that
shows your issue.
View the original post :
Tim,
You are right. I had to retract my statement. It does support multiple threads
locally since we do have a test case TxConcurrentBankUnitTestCase for this. :-)
In terms of isolation level, there should be no difference though. I mean even
if you are using AS tm, the locking behavior across
Ben,
I was under the impression that the DummyTransactionManager supported multiple
threads locally. It doesn't seem to support the transaction isolation levels on
a cluster-wide basis (ie. all locking is local until commit() is called). My
testing (which I admit hasn't been overly extensive)
DummyTransactionManager included in the distro is only for testing only. It
only supports single thread. If you want to test it out, you will need to plug
in a different tm (e.g., running under JBoss AS).
But if anyone volunteers to make the current DummyTransactionManager supporting
