Ex: Re: spurious org.springframework.beans.factory.NoSuchBeanDefinitionException

[Paul B. Henson]

> From: Cantor, Scott
> Sent: Tuesday, September 12, 2023 5:56 AM
>
> a cluster and only one server is implicated). I would obviously blame Tomcat
> if you happened to use it, but I haven't really seen that kind of corruption
> with Jetty.

We've been a jetty shop for a while now.

> Were it me I would probably move the bean up into global.xml and that way
> it would fail at startup or not at all. It's waiting to fail because the beans aren't
> created until the interceptor flow actually runs for the first time.

Ah, interesting.

> But something is wrong with your deployment I would say.

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.

Rechecking the logs, it does seem like the failure was the first attempted login, even though the service had been up about a week. Next time it happens I'll see if I can correlate something to it. At least it's not in prod, so far.

Thanks as always for the insight.