"Encountered error parsing message into its DOM representation" and "Unable to read XML from input stream"

[Cantor, Scott]

> While investigating another problem on my production Shibboleth IdP 2.2.1
> (with ECP extension), I noticed that there has been an increased frequency
> of the following error in the IdP's idp-process log:
> 
> 17:06:37.054 - ERROR
> [org.opensaml.ws.message.decoder.BaseMessageDecoder:186] -
> Encountered error parsing message into its DOM representation
> org.opensaml.xml.parse.XMLParserException: Unable to read XML from
> input stream

If you have child threads stacking up waiting, and then disconnecting, it's possible that when they eventually get serviced, they're gone, and so there's no data to read. Nothing really matters log-wise until the deadlock or contention issue is fixed.

I think you have to be looking at moving to a supported version as well. You're many versons back, and using old, unsupported ECP extension code instead of what's built into 2.3.

At a minimum, comparative load testing against your version and 2.3 would be a start.

-- Scott