<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><blockquote type="cite"><div><blockquote type="cite"><blockquote type="cite">On 25 Jan 2011, at 17:12, Manik Surtani wrote:<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">How's this for a solution:<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">1) Test suite remains the same<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">I don't think performance is affected by using JBossTM for test runs, I'll need to check by running it<br></blockquote></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">It should be quicker. There is no maintenance of a persistent tx log.<br></blockquote>Not necessarily: the log would only be written for tx that span more than an participant (have more than 1 XAReource enlisted). AFAIK there are very few tests like that in ISPN (I can only remember one). If only one participant in tx the TM would doesn't have to persist the log to disk. <br></div></blockquote><div><br></div><div>There are a few tests testing transactions that span different cache instances. Each one would be considered as its own RM.</div></div></div></blockquote>indeed, but very few. I'll measure and see the difference, that should tell us beyond doubt :)<br><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>Not true.</div><div><br></div><div><a href="https://github.com/infinispan/infinispan/blob/master/core/src/main/java/org/infinispan/transaction/tm/DummyTransaction.java#L305">https://github.com/infinispan/infinispan/blob/master/core/src/main/java/org/infinispan/transaction/tm/DummyTransaction.java#L305</a></div></div></div></blockquote>Interesting! To my excuse that was added recently while I was on vacation :-)</div><div><br></div><div><div>I've just looked at the code and it is broken:</div><div>- the readonly flag is set on prepare with the value returned by last enlisted XAResouce (bad!!)</div><div>- so on commit, if last enlisted XAResource returned r/o status, no commit is called on *any* other enlisted resource (bad! bad! bad!)</div><div><br></div><div><br></div><div><br></div></div><br></body></html>