[ https://issues.jboss.org/browse/WFLY-8954?page=com.atlassian.jira.plugin.... ] Nuno Godinho de Matos commented on WFLY-8954: --------------------------------------------- Hi Scott, I will try the sample application against the latest 10.1.0.Final build. I would not be surprised that the issue lays somewhere in how ARUJA integrates with eclipselink. But what appears to be happening is that during the ONSUCCESS / ONCOMPELTION observation of an event takes place at a moment in time where changes have been persisted into the database, but the entity clones used by the unit of work have yet to be published to the server session cache. So this leads to many "interesting"/un-ince bugs. So this one, is really a "mess" of a problem, in terms of possible consequences. I will try to test the sample application against the 10.1.0.Final. And if that does not work, I will try to see about 10.0.0.Final with hibernate. What I can confirm is that there is quite a difference of behavior between weblogic transaction management (interceptors) and those in wildfly. Weblogic, will for intances, open a new transaction context implicitly. THe code would not need to be flagged with annotation transaction requires new. IN wildfly, in this scenario the transaction requires new is absolutely need to not get errors stating we are trying to work without transactional context. In any case, i will report back to you on those two variables. Kindest regards. -- This message was sent by Atlassian JIRA (v7.2.3#72005)