[hibernate-issues] [Hibernate-JIRA] Commented: (HSEARCH-893) MassIndexer causes a LockObtainFailedException to be thrown when using Infinispan as a directory provider
Tom Waterhouse (JIRA)
noreply at atlassian.com
Tue Sep 6 11:38:02 EDT 2011
[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=43462#comment-43462 ]
Tom Waterhouse commented on HSEARCH-893:
----------------------------------------
I changed each named cache for Lucene to use org.infinispan.transaction.lookup.DummyTransactionManagerLookup and the test passed. Is this what you meant for decoupling the cache from the transaction manager?
> 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
More information about the hibernate-issues
mailing list