Hi Andy, On Mon, 2018-07-30 at 14:32 -0700, Andreas Schaefer wrote: > Hi > > For SLING-7768 I created two unit test classes > (org.apache.sling.resourceresolver, branch: feature/SLING-7768) that > test the basic etc mapping behaving directly with MapEntries and one > through the Resource Resolver which also includes tests using > resolve(). > > During my tests I ran into an issue with the /etc/map mapping that > led to an issue where Sling became unresponsive and luckily can be > fixed by changing the path to the /etc/map in the Resource Resolver > Factory configuration. It might be good to provide a configuration > settings where certain paths like the one from Composum can be > excluded from the mapping to avoid loosing access to composum due to > a misconfiguration in the mapping.
Do these issues appear only with the new interpolation code? If that's not the case, please file a separate SLING issue as we should prevent it from happening. In any case, relying on configuration is not a definitive solution, we must avoid Sling locking up. Thanks, Robert
