[JCR-2503] inconsistent session and persistent state after ReferentialIntegrityException

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 1.6.2, 2.1
• Fix Version/s: 1.6.2, 2.2
• Component/s: jackrabbit-core
• Environment: win7 / jdk 1.6.0_17 / mvn 2.0.10
• Assignee: Jukka Zitting
• Reporter: Bram de Kruijff
• Created: 18/Feb/10 18:25
• Updated: 23/Sep/11 11:25
• Resolved: 14/May/10 13:46

Description

When a ReferentialIntegrityException occurs in a session it seems that subsequent actions on that session may result in a inconsistent session state AND even inconsistent persistent state. The latter will even make jackrabbit fail to bootstrap an index from that persistent state.

Typical rootcause:

Caused by: org.apache.jackrabbit.core.state.NoSuchItemStateException: ddb9d3ea-59c1-4eb4-a83e-332f646d4f40
at org.apache.jackrabbit.core.state.SharedItemStateManager.getItemState(SharedItemStateManager.java:270)
at org.apache.jackrabbit.core.query.lucene.MultiIndex.createIndex(MultiIndex.java:1082)
at org.apache.jackrabbit.core.query.lucene.MultiIndex.createIndex(MultiIndex.java:1088)
at org.apache.jackrabbit.core.query.lucene.MultiIndex.createInitialIndex(MultiIndex.java:395)

Bootstrap failure:

java.io.IOException: Error indexing workspace
at org.apache.jackrabbit.core.query.lucene.MultiIndex.createInitialIndex(MultiIndex.java:402)
at org.apache.jackrabbit.core.query.lucene.SearchIndex.doInit(SearchIndex.java:465)
at org.apache.jackrabbit.core.query.AbstractQueryHandler.init(AbstractQueryHandler.java:59)
at org.apache.jackrabbit.core.SearchManager.initializeQueryHandler(SearchManager.java:553)

Issue Links

• is related to: JCR-1806 Item not found exception
• is related to: JCR-2290 Potential concurrency issues of Workspace operations
• is related to: JCR-288 inconsistent session state after Item/Session.save() throwing ReferentialIntegrityException