[
https://issues.apache.org/jira/browse/OAK-1262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13843259#comment-13843259
]
Jukka Zitting commented on OAK-1262:
------------------------------------
Do we still see this issue?
I had a hunch about a potential problem in the way the head state is shared
across threads using a {{volatile}} variable in the {{SegmentNodeStore}}. In
principle this should be correct, as all {{volatile}} reads and writes should
be implicitly synchronized, but to be extra sure I changed the variable to an
{{AtomicReference}} in revision 1548354.
Unfortunately I don't seem to be able to reproduce the problem either before or
after that revision, so there's no way for me to tell whether the change helped.
> observation event is triggered but session sees old content
> -----------------------------------------------------------
>
> Key: OAK-1262
> URL: https://issues.apache.org/jira/browse/OAK-1262
> Project: Jackrabbit Oak
> Issue Type: Bug
> Reporter: Tobias Bocanegra
>
> unfortunately there is not test case yet, but we see sometime the behavior
> that an admin session gets an observation event of a modified property but
> when reading the content still sees the old content.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
