spurious org.springframework.beans.factory.NoSuchBeanDefinitionException

[Cantor, Scott]

> So far I've only ever seen it on our test systems, but they're managed and
> configured the exact same as prod and are only out of sync when we're
> actively working on an update or major config change. The only real
> difference between them is load, the test boxes might sit weeks without
> anybody hitting them.

I think you will eventually find that there's a pre-4.3 jar set or at least one jar sitting in there somewhere, some kind of corrupted warfile or failed upgrade. That parent bean is fairly new I believe.

-- Scott