> Ok, I remember now. It's not the first time AbstractCacheTest.getDefaultClusteredCacheConfig() has caused problems because it disables state transfer. BTW, doesn't https://issues.jboss.org/browse/ISPN-2842 sound familiar?

yes it sounds. LuceneDirectory is very sensitive... It relies on the fact the cache.get(key) invoked by multiple threads returns a reference to the same object (at least for metadata cache). otherwise you can start having IOE.... eviction, store as binary, and other stuff cannot be enabled for the metadata cache.

> I just ran the core and query test suites with the .stateTransfer().fetchInMemoryState(false) line commented out and I didn't get any failures, so I think we should just remove it. I believe ST was disabled to speed up the tests, but nowadays it doesn't make any difference. If any tests do require ST to be disabled, they can disable it themselves.

like I said, I'm an idiot :) that class uses RAM as directory and not InfinispanDirectory. That's why it is commented. However, some subclasses uses InfinispanDirectory and in that classes I'm enabling the state transfer. that line of code is going to be removed.