Default FailFast configuration leading to intermittent failures in spring wiring

[Cantor, Scott]

> Why spring and tomcat allows a call to a JMX Bean to lazily create the
> application when the overall startup hasn't been completed is a mystery to
> me. We can't be the only company using tomcat and JMX to monitor it so I
> am surprised I couldn't google up any similar instances. Is there something
> unusual about the way shibboleth uses spring/springflow?

I don't think so, esp. in the current releases, it's using the provided XML config schema from SWF. Some of our MVC stuff is a bit more manual than most I guess.

Our web application context loader is extended in a few ways, but not really in order to play any games with the order of things, it's just to get properties loaded.

> Looks like I found my problem and a workaround (don't query
> Catalina:j2eeType=Servlet,name=default,*). We had recently added more
> monitoring to all of the newly affected nodes; had I been thinking I might
> have noticed the correlation sooner.

I'll put something in the wiki about it. I would say there's a bug in all that somewhere.

-- Scott