<div dir="ltr">Some update, here is the latest logs I got while the test failed:<div><a href="https://paste.fedoraproject.org/paste/Yy8CuDvgqzX1RazON6Cmag">https://paste.fedoraproject.org/paste/Yy8CuDvgqzX1RazON6Cmag</a><br></div><div><br></div><div>I haven't time to dig further today, but see in the middle that lovely stack trace:</div><div><div><br></div><div><i>18:01:59,012 ERROR [org.infinispan.transaction.impl.TransactionCoordinator] (default task-35) ISPN000255: Error while processing prepare: org.infinispan.transaction.WriteSkewException: Write skew detected on key itest-rest-feed~Local DMR~/subsystem=datasources/xa-data-source=testXaDs for transaction TransactionImple < ac, BasicAction: 0:ffffc0a8000c:-5784e282:59f75acd:b4 status: ActionStatus.RUNNING ></i></div><div><i><span style="white-space:pre"> </span>at org.infinispan.transaction.impl.WriteSkewHelper.performWriteSkewCheckAndReturnNewVersions(WriteSkewHelper.java:66)</i></div><div><i><span style="white-space:pre"> </span>at org.infinispan.interceptors.locking.ClusteringDependentLogic$AbstractClusteringDependentLogic.clusteredCreateNewVersionsAndCheckForWriteSkews(ClusteringDependentLogic.java:261)</i></div></div><div><i><br></i></div><div>I have no idea why it wasn't displayed before, and it is now. </div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Oct 30, 2017 at 1:15 PM, Joel Takvorian <span dir="ltr"><<a href="mailto:jtakvori@redhat.com" target="_blank">jtakvori@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">I've seen the same error just once (out of 5 or 6 tries), and, coincidentally, had the same error notified "<span style="font-size:12.8px">Failed to store notification: {"type":"RESOURCE_ADDED" etc.</span>" with "MethodNotAllowed" at the very same moment, that is, just when the testRemoveXaDatasource test runs.<div>That's maybe a trail to investigate, maybe it betrays some server-side malfunction. I don't know if it's possible to see server-side logs during agent itests, but it would probably help. I don't know why this error happens.</div><div><br></div><div>When I run tests successfully, I also see from times to times this error, but it's distributed randomly in tests, and fortunately or not (rather not), tests pass.</div></div>
</blockquote></div><br></div>