While testing some stuff for ISPN-1837, I found that the hash configuration for DIST doesn't override properly when using the defineConfiguration method on the DefaultCacheManager. The problem is that the OverrideConfigurationVisitor doesn't copy over the activated value, so when the config is copied it over it doesn't think the hash configuration was touched and subsequently skips it.

The interesting thing is that L1 should also be broken, but because of how the LegacyConfigurationAdaptor works it actually activates L1 no matter what, since it will either enable or disable it.

Also the override works properly if the default has a setting for the hash configuration.

I have a testNG that very easily shows this.