[hibernate-issues] [Hibernate-JIRA] Resolved: (HSEARCH-284) Be able to configure a LockFactory

[Sanne Grinovero (JIRA)]

     [ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sanne Grinovero resolved HSEARCH-284.
-------------------------------------

    Resolution: Fixed

> Be able to configure a LockFactory
> ----------------------------------
>
>                 Key: HSEARCH-284
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-284
>             Project: Hibernate Search
>          Issue Type: Improvement
>    Affects Versions: 3.0.1.GA
>            Reporter: sam doyle
>            Assignee: Sanne Grinovero
>             Fix For: 3.1.1
>
>
> In a case where an application restarts, crashes, gets killed etc. if there is an existing  Lucene lock it will not be removed on the application restart.
> As a result of this the application itself can be severely impacted.
> After encountering this particular issue and needing to manually remove the lock to resolve the problem I did some searching. It appears this situation is somewhat common and the use of NativeFSLockFactory was the suggested solution.
> Since I don't see where this particular option is configurable with Hibernate Search I have opened this request.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira