[
https://issues.apache.org/jira/browse/JCRVLT-647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated JCRVLT-647:
-----------------------------------
Fix Version/s: (was: 3.6.2)
Resolution: Invalid
Status: Resolved (was: Patch Available)
The problem is not the save() shortly after a {{ConstraintViolationException}}
(which is fine) but rather after a {{InvalidItemStateException}}. For the
latter case just retrying the save() does never(!) succeed, so the proper fix
is tracked with JCRVLT-648.
> Restore old intermediate save() interval after failed saves
> -----------------------------------------------------------
>
> Key: JCRVLT-647
> URL: https://issues.apache.org/jira/browse/JCRVLT-647
> Project: Jackrabbit FileVault
> Issue Type: Improvement
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Priority: Major
>
> With the fix for JCRVLT-646 also the {{Session.save()}} interval was reduced
> after a failed {{Session.save()}} attempt. So after a save failure a new save
> was triggered around 10 nodes later.
> For certain edge cases this increases the chance for mid-air conflicts (as
> each save() itself may trigger event listeners writing to the JCR as well).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
