[hibernate-issues] [Hibernate-JIRA] Commented: (HSEARCH-893) MassIndexer causes a LockObtainFailedException to be thrown when using Infinispan as a directory provider
[
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-893?pag...
]
Sanne Grinovero commented on HSEARCH-893:
-----------------------------------------
to clarify my previous comment: in short yes what you did is correct.
An alternative solution is to not define the transactionManager configuration in the
default cache, so that it won't be inherited by other caches and configure it only on
those caches which are _not_ being used to store Lucene's index. What you did though
obtains the same end result.
MassIndexer causes a LockObtainFailedException to be thrown when
using Infinispan as a directory provider
---------------------------------------------------------------------------------------------------------
Key: HSEARCH-893
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-893
Project: Hibernate Search
Issue Type: Bug
Components: infinispan, massindexer
Affects Versions: 3.4.0.Final, 3.4.1.Final
Environment: Hibernate Core 3.6.5/Hibernate Search 3.4.0/Infinispan 5.0/Spring
3.0.5
Reporter: Tom Waterhouse
Assignee: Sanne Grinovero
Attachments: infinispan-hsearch-index-lock.zip
When using MassIndexer and FSDirectory all is okay. When using InfinispanDirectory
LockObtainFailedException is thrown.
A test case is attached (MassIndexerTest).
Note that for this test a slightly modified copy of InfinispanDirectoryProvider was
needed, as the Infinispan cache instance we use in production is declared in Spring.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira