Runtime exception upon jetty restart on load

[Cantor, Scott]

It's impossible for this to be "transitory", it's an issue with Java's restrictions in newer versions and it either happens or it doesn’t, but the issue is/was inside the Warning interceptor, so it only happens when that runs.

Having said that, we know it was a Spring reflection bug and it's long fixed. I have not seen the issue since, and I have no idea how somebody would encounter it now. We have a canary unit test in place so that we'd know if Spring had the issue ever again, and they don't.

The original closed bug [1]
The new one somebody filed [2]

I use that flow, and it hasn't ever failed like this in recent memory since the Spring bug was fixed, so I have no doubt that it's environmental/corruption of some sort. But at this point, "try 5.x" is the only practical advice I have, and that likely won't help since the latest report about it was on 5.0.

If a member runs into it, I'll do more digging with them, there's probably a localized "habit" that's incorrect in some way and must be causing it.

-- Scott

[1] https://shibboleth.atlassian.net/browse/IDP-1901
[2] https://shibboleth.atlassian.net/browse/IDP-2212