[
https://issues.jboss.org/browse/WFLY-8954?page=com.atlassian.jira.plugin....
]
Nuno Godinho de Matos commented on WFLY-8954:
---------------------------------------------
Hi Scott, I will see if I can find the eclipse link code point when they start merging the
cloned entities to the server cache. If I find it I can give you a stack trace of when
that happens in weblogic, which we would assume is happening before the on success gets
called and the moment when that happens on wildfly, which should be after the on success
handling. Most likely that will be easiest. And nope, nothing is specific to oracle in the
test case. Only the data sources as you pointed out. The app has other irrelevant
components related to reproducing an issue on XA transactions involving XA Jdbc drivers
... Taking at times too long to publish the committed changes to the database killing the
assurance of happens before relationship between independent serial transactions when Jdbc
XA is used. But that is a different test case that is irrelevant here.
Wildfly 10 with eclipselink Onscucess observer gets stale entity
----------------------------------------------------------------
Key: WFLY-8954
URL:
https://issues.jboss.org/browse/WFLY-8954
Project: WildFly
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 10.0.0.Final
Reporter: Nuno Godinho de Matos
Assignee: Scott Marlow
Hi,
In widlfly there seems to be an important issue concerning CDI events and observing these
events during onsuccess. At least while using eclipselink.
When using wildfly 10.0.0.Final together with eclipselink, if an application modifies an
entity A, fires an event stating entity A has been modified, and an observer consumes this
event during transaction success.
Then the observer will be working with stale entities that do not reflect the
modifications done to the entity.
A sample application for this issue is available in:
https://github.com/99sono/wildfly10-observe-on-success-stale-entity
The widlfly configuration xml for the sample application, is available in the application
itself, as can be seen in the readme documentation.
Many thanks for taking a look.
Kindest regards.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)