Same issue here too.
The index caches always get initialized as default local caches. Neither the default configuration file nor the custom configured is being used.
After a bit of digging into the source code, it seemed an instance of the default cache manager is used all the time which does not take the configuration file into account.
Not sure if it is an issue with the hibernate search part because the suspicious part of the code falls into that.
org.hibernate.search.engine.impl.StandardServiceManager.requestService(Class<? extends ServiceProvider<T>> serviceProviderClass, BuildContext context) always returns a default cache manager.
Couldn't find anything wrong. Can you kindly point in the right direction?
5.2.1 is the version against which this has been encountered.
it seems that it works for somebody: https://community.jboss.org/thread/171622. Do you use Hibernate as JPA provider or do you query the caches directly (as described at https://docs.jboss.org/author/display/ISPN/Querying+Infinispan)? If the latter is true, the property hibernate.search.infinispan.configuration_resourcename cannot be used. You need to specify configuration for individual caches directly in infinispan-distribution.xml that you use to configure your cache. You can find an example of such a configuration files at https://github.com/infinispan/infinispan/blob/master/query/src/test/resources/dynamic-indexing-replication.xml
Thanks a lot for the reply Martin.
The caches are being queried directly and have been trying to use the method intended for Hibernate/JPA.
It is indeed using the same cache manager, the default one which has initialized the caches.
And configuring the ones for Indexing under the same solved the problem.
Thanks again for the clarification.
Tried marking the question as answered but I think me, not being the owner, cant do so.