You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Jukka Zitting (Commented) (JIRA)" <ji...@apache.org> on 2012/02/06 12:51:59 UTC
[jira] [Commented] (JCR-2650) don't silently merge session-local
transient changes with external changes before save().
[ https://issues.apache.org/jira/browse/JCR-2650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13201231#comment-13201231 ]
Jukka Zitting commented on JCR-2650:
------------------------------------
In fact the above deadlock scenario still exists (see JCR-3226). Instead of stateCreated(), this issue fixed the potential problem with the (much more frequent) stateModified() method.
> don't silently merge session-local transient changes with external changes before save().
> -----------------------------------------------------------------------------------------
>
> Key: JCR-2650
> URL: https://issues.apache.org/jira/browse/JCR-2650
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-core
> Reporter: Stefan Guggisberg
> Fix For: 2.2
>
> Attachments: JCR-2650 (cleaned).patch, JCR-2650.patch
>
>
> currently, external changes (i.e. changes committed by other sessions) are silently merged with transient changes. this might potentially cause concurrency issues/inconsistent transient state (see e.g. JCR-2632).
> it would probably be better to isolate transient changes from external changes until they're saved (true copy-on-write).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira