Hi Atin sorry but I don't see how this is a bug: the locking system is designed to prevent you from making mistakes and it is very likely doing exactly that.

You will have this exception in these cases:

• it's starting and using an index directory which is being used by another Hibernate Search instance (you should never do this)
• the index directory was used by a previous instance of an Hibernate Search application which was brutally terminated (for example the JVM crashed)
• you're sharing an index directory across multiple instances over NFS or other network shares

You can use network shares but will need to be very careful about NOT sharing the same storage directory across multiple applications. It is generally not a recommended pattern as searches will be slower, and semantics like the Locking are not as reliable - and this is not an Hibernate Search issue but simply the locking most such network filesystems are simply not compliant with the POSIX specifications (Some of them are fine but if you have trouble with the locks chances are that you're not using one of the correct ones).

I am happy to help you on the forums if you can provide more information about your configuration, but I'll reject the issue as this is not actionable. Thanks!

https://forum.hibernate.org/viewforum.php?f=9