Possible stackoverflow in SpringComponentManager#getComponent when exception is thrown and there is no logger available in HstServices

SpringComponentManager#getComponent(String name, String ... addonModuleNames) there can be a stackoverflow because HstServices.getLogger calls SpringComponentManager#getComponent(String name, String ... addonModuleNames) again.

I could not reproduce this locally, but Hudson seems to fail on it. See for example

https://builds.onehippo.org/job/hst%20Trunk/org.onehippo.cms7.hst.components$hst-core/2378/testReport/junit/org.hippoecm.hst.site.container/TestSpringComponentManager/testConditionalBeanRegistration/