[JCR-1117] Bundle cache is not rolled back when the storage of a ChangeLog fails

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.3, 1.4, 1.5, 1.5.2, 1.5.3, 1.5.4
• Fix Version/s: 1.5.5
• Component/s: jackrabbit-core
• Assignee: Unassigned
• Reporter: Martijn Hendriks
• Created: 10/Sep/07 13:38
• Updated: 29/Apr/09 07:50
• Resolved: 02/Mar/09 08:49

Description

The bundle cache in the bundle persistence managers is not restored to its old state when the AbstractBundlePersistenceManager.store(ChangeLog changeLog) method throws an exception. If, for instance, the storage of references fails then the AbstractBundlePersistenceManager.putBundle(NodePropBundle bundle) method has already been called for all modified bundles. Because of the connection rollback, the bundle cache will be out-of-sync with the persistent state. As a result, the SharedItemStateManager will have an incorrect view of the persistent state.
Furthermore, if the blockOnConnectionLoss property is set to true, then the BundleDbPersistenceManager can be caught in an infinite loop because of invalid SQL inserts because of an incorrect bundle cache; see attached stacktrace.

Issue Links

• is related to: JCR-1806 Item not found exception