[ https://issues.jboss.org/browse/WFLY-8954?page=com.atlassian.jira.plugin.... ] Nuno Godinho de Matos commented on WFLY-8954: --------------------------------------------- On wildfly 10.1.0.0.Final with eclipselink, the problem persists. {panel} 2017-06-21 18:39:47,993 INFO [wildfly.bug.onsuccess.facade.ModifyEntityAndFireEventFacade] (default task-35) We will now modify the entity: db.model.SomeEntity@4e2224a0 we will toogle the text to either true or false 2017-06-21 18:39:48,005 INFO [wildfly.bug.onsuccess.facade.AbstractSomeEntityChangeEventObserverFacade] (default task-35) START: TEST VALIDATION - FOR FIRED EVENT: wildfly.bug.onsuccess.event.SomeEntityChangeAEvent 2017-06-21 18:39:48,008 INFO [wildfly.bug.onsuccess.facade.AbstractSomeEntityChangeEventObserverFacade] (default task-35) Before Refresh value was: false, After Refresh: true. Value on entity passed by event object as new value was: true 2017-06-21 18:39:48,009 ERROR [wildfly.bug.onsuccess.facade.AbstractSomeEntityChangeEventObserverFacade] (default task-35) Wildfly ON_SUCCESS handling observing stale entity that does not match what transaction persisted. EntityMode before refresh: false And After Refresh: true For Equipment: 1 <---------------------- NOTE: here the code is detecting that entity is stale. 2017-06-21 18:39:48,009 INFO [wildfly.bug.onsuccess.facade.AbstractSomeEntityChangeEventObserverFacade] (default task-35) ENDED: TEST VALIDATION - FOR FIRED EVENT: wildfly.bug.onsuccess.event.SomeEntityChangeAEvent {panel} I will see what is the outcome when using hibernate. The domain model should in this case be trivial enough to not have any problems switching the persistence provider. -- This message was sent by Atlassian JIRA (v7.2.3#72005)