hibernate seems stuck after a lock error from lucenne

mirak · **Joined:** Mon Apr 04, 2011 12:08 pm **Posts:** 32

when I mass index with hibernate search and it crashed because a lock problem, then after that it seems everything is stuck.
Any idea where this could come from ?

could it be a transaction problem ?

I start the MassIndexer with .start() method wich is threaded I think, from inside a dao annotated with @Transaction. The method is ran from inside an action, but can also be programmable through quartz.
I am not sure what happens transaction wise.

Elmer · **Joined:** Mon Apr 11, 2011 7:56 am **Posts:** 38

I guess your connection pool is full, see HSEARCH-598 for more info.

mirak · **Joined:** Mon Apr 04, 2011 12:08 pm **Posts:** 32

thanks

sanne.grinovero · **Posted:** Sat May 14, 2011 6:36 pm

also, the MassIndexer should not be run when the index is being changed by interactive usage (standard events): if you try, the locks will prevent you to corrupt the index but it would basically block other operations.
The intention of the MassIndexer was to quickly upgrade indexes when the application is upgraded (schema / index mapping is changed), or as a tool for data recovery (index is lost/corrupted). I'm going to rework the design a bit to prevent the connection pools problems as in HSEARCH-598 and to make sure you can also run it "freely", i.e. even when the application is running, but this is coming in next version.