I think we may have goofed a little bit in how we implemented
LockOptions specifically in terms of
org.hibernate.LockOptions#aliasSpecificLockModes
That grew out of the legacy means for specifying lock modes on Query and
Criteria:
setLockMode(String alias, LockMode lockMode);
There is a discus
On Wed, Dec 28, 2011 at 2:21 PM, Guillaume Smet
wrote:
> After our upgrade to 4.0 (from 3.4.1), we've started to have a lot of
> lock errors on our development boxes. I thought it was due to brutal
> kills of the JVM (typically Terminate in Eclipse) but we also have
> them in our CI environment on
Hi,
a lock marker file is created any time an IndexWriter is opened, and
(should be) cleaned up when the IndexWriter is closed.
So if you kill the application without properly closing the
IndexWriter, this problem is expected and you'll have to cleanup the
lock file manually.
With "exclusive_index
