[JCR-445] repository is locked by WorkspaceJanitor when another workspace is reindexing

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.9, 1.0, 1.0.1
• Fix Version/s: 1.1
• Environment: jackrabbit 410461
• Assignee: Tobias Bocanegra
• Reporter: Tobias Bocanegra
• Created: 31/May/06 15:58
• Updated: 31/May/06 16:31
• Resolved: 31/May/06 16:31

Description

when the searchindex is corrupt or missing, it is rebuilt lazily after initialization of a workspace. usually by the first login on that workspace. during this time, the workspaceinfo is locked. unfortunately, the workspace janitor locks the repository and checks all workspace infos, if they can be disposed. in this case, no other access to the repository can be performed until the searchindex is initialized (which can take some time).

T1 -> WS1.login -> WS initializing
Janitor -> lock repo -> scan -> try lock WS1
T2 -> WS2.login -> must wait for T1