[jboss-jira] [JBoss JIRA] (WFLY-8954) Wildfly 10 with eclipselink Onscucess observer gets stale entity

[Nuno Godinho de Matos (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-8954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13457440#comment-13457440 ] 

Nuno Godinho de Matos edited comment on WFLY-8954 at 9/1/17 9:08 AM:
---------------------------------------------------------------------

No. 

The issue not solved!
I have a system test where this issue can still be reproduced.
I can no longer reproduce it using the sample application, but we do have a scenario in a system test where after refreshing the entity we get different data than what we have in the server session cache.

Not good...

Actually, good.
The fix is most likely working perfectly. The issue I am looking at is a incorrectly named event class, that was leading for my dirty "state" check to be run against a the wrong entity field.
However, the refresh action is being redundant. That is a very good indication.
I believe my impression above is nothing but a false negative.
We are still in the clear for now...

Changes are so far looking good.
I have taken the dirty code that was specific to wildfly onobsever bug from our code, and I will see  if the CI system tests are fine all accross.


NOTE:
- I will be opening a new wildfly JIRA related to the unregister connection problem mentioned on a wildfly thread.
{panel}
java.lang.IllegalStateException: IJ000152: Trying to return an unknown connection: org.jboss.jca.adapters.jdbc.jdk7.WrappedConnectionJDK7 at 40a9ad99
{panel}

This issue is not addressed by this fix.
Thanks.


was (Author: nuno.godinhomatos):
No. 

The issue not solved!
I have a system test where this issue can still be reproduced.
I can no longer reproduce it using the sample application, but we do have a scenario in a system test where after refreshing the entity we get different data than what we have in the server session cache.

Not good...

Actually, good.
The fix is most likely working perfectly. The issue I am looking at is a incorrectly named event class, that was leading for my dirty "state" check to be run against a the wrong entity field.
However, the refresh action is being redundant. That is a very good indication.
I believe my impression above is nothing but a false negative.
We are still in the clear for now...




> 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)