[
https://issues.jboss.org/browse/WFLY-8954?page=com.atlassian.jira.plugin....
]
Nuno Godinho de Matos commented on WFLY-8954:
---------------------------------------------
Hi,
Ok, so I have done a commit that on first testing seems to address the bug.
This commit can be checked upon:
https://github.com/99sono/wildfly/commit/727c652e001d172a8fe2b41cac42fec2...
I have not actually tried to patch my widfly 10.1.0.Final nor have I run any of our system
tests to validate that this is ok.
I see if I get a window of opportunity for this tomorrow.
One thing that is not clear to me.
Is there any need to "unregister" from the
javax.transaction.TransactionSynchronizationRegistry?
Or is the specification somehow detailing that the container is responsible of cleaning up
its state once the transaction reaches the end of its life?
The JPA persistence layer therefore must register but not necessarily unregister?
I have written no code for doing such a de-registration.
Nor have I found any hint on the eclipselink code for the need of doing this.
Since, in any case, the TransactionSynchronizationRegistry seems to only offer APIs to put
resources and register but not for the opposite operation, I am under the impression that
the logic implemented should be safe and not lead to any unexpected leaks.
I await your feedback.
Kindest regards.
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)