Soap Calls Fail with Invalid UTF-8 middle byte error
SOAP calls intermittently fail with an 'Invalid UTF-8 middle byte' error.
com.ctc.wstx.exc.WstxIOException: Invalid UTF-8 middle byte 0x2d (at char #1415, byte #127)
Steps to Reproduce
Not Applicable - intermittent.
This appears to be a character encoding issue with the content associated with this soap call.
The initiator of the call is not sending its content encoded in UTF-8, but Pega is attempting to decode it in UTF-8.
Ensure that the incoming SOAP XML has a properly formed header such as:
<?xml version="1.0" encoding="UTF-8"?> or
<?xml version="1.0" encoding="ISO-8859-1"?> Pega uses this header to determine the appropriate character encoding to use.
0% found this useful