[
http://jira.magnolia-cms.com/browse/MAGNOLIA-2489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21587#action_21587
]
Jan Haderka commented on MAGNOLIA-2489:
---------------------------------------
synchronization on locking is not an option. First because it would lock any
other activation, not only on affected subpath, and second because process of
locking and unlocking are in separated methods so we would need a global
semaphores to deal with that.
It seems issue can be mitigated rather simply by letting activation to wait if
the lock can't be obtained and retry number of times in regular intervals. I
have already fix to that effect implemented locally.
> When two different editors try activate same piece of content at nearly same
> time, the latter attemp fails
> ----------------------------------------------------------------------------------------------------------
>
> Key: MAGNOLIA-2489
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2489
> Project: Magnolia
> Issue Type: Improvement
> Reporter: Jan Haderka
> Assignee: Jan Haderka
>
> The activation of single piece of content takes about 2sec. If the another
> activation for same piece of content comes in that time interval, it will
> fail with
> {code}
> Operation not permitted, /path/to/node is locked
> {code}
> perhaps in this case ReceiveFilter should attempt to wait for few secs and
> attempt to activate incoming content again before returning failure back to
> Syndicator.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
