You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Julian Reschke (Resolved) (JIRA)" <ji...@apache.org> on 2011/11/07 18:44:51 UTC
[jira] [Resolved] (JCR-3139) missing sync in
InternalVersionManagerImpl.externalUpdate can cause
ConcurrentModificationException
[ https://issues.apache.org/jira/browse/JCR-3139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julian Reschke resolved JCR-3139.
---------------------------------
Resolution: Fixed
trunk: 1198827, 2.2: 1198836
> missing sync in InternalVersionManagerImpl.externalUpdate can cause ConcurrentModificationException
> ---------------------------------------------------------------------------------------------------
>
> Key: JCR-3139
> URL: https://issues.apache.org/jira/browse/JCR-3139
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-core, versioning
> Reporter: Julian Reschke
> Assignee: Julian Reschke
> Fix For: 2.2.10, 2.4
>
>
> In
> for (Map.Entry<ItemId, InternalVersionItem> entry : versionItems.entrySet()) {
> if (changes.has(entry.getKey())) {
> items.add(entry.getValue());
> }
> }
> we need to sync on versionItems, I believe.
--
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