Tomcat error popping up on rotation servers in rapid succession

[Cantor, Scott]

On 6/13/17, 7:57 PM, "users on behalf of Botsford, Benjamin T" <users-bounces at shibboleth.net on behalf of ben.botsford at austin.utexas.edu> wrote:

> Earlier today, two of our three Shibboleth IdP servers went down in rapid succession, seemingly for the same reason. I originally
> suspected it was a metadata error since we've seen a few of those recently, but it appears to have been Tomcat-related.

If that's just Apache, those are just logs of it failing to contact the container, that doesn't implicate anything other than the container not responding. Same error you'd probably get if you stopped one.

> These aren't terribly abnormal errors, I understand. What's confusing us is why this would have happened on two separate
> servers within minutes of one another (it doesn't seem to be load-related).

If there's nothing in the logs that matter I don't really know how anybody would be able to tell that.

>  Could this be caused by a response type or a string included in a response, maybe?

I don't trust Tomcat so anything's possible, but I seriously doubt it.

-- Scott