jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tobias Bocanegra (JIRA)" <j...@apache.org>
Subject [jira] Closed: (JCR-445) repository is locked by WorkspaceJanitor when another workspace is reindexing
Date Wed, 31 May 2006 09:32:30 GMT
     [ http://issues.apache.org/jira/browse/JCR-445?page=all ]
Tobias Bocanegra closed JCR-445:

    Fix Version: 1.1
     Resolution: Fixed

fixed in 410482

please note, that there is still a very small possiblity of a synchronization problem, during
the shutdown perdiod of the repository. if a login on an uninizialied workspace occurss during
shutdown, a NPE could be thrown.

> repository is locked by WorkspaceJanitor when another workspace is reindexing
> -----------------------------------------------------------------------------
>          Key: JCR-445
>          URL: http://issues.apache.org/jira/browse/JCR-445
>      Project: Jackrabbit
>         Type: Bug

>     Versions: 1.0, 1.0.1, 0.9
>  Environment: jackrabbit 410461
>     Reporter: Tobias Bocanegra
>     Assignee: Tobias Bocanegra
>      Fix For: 1.1

> 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

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message