Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Soap Calls Fail with Invalid UTF-8 middle byte error



SOAP calls intermittently fail with an 'Invalid UTF-8 middle byte' error.

Error Messages

com.ctc.wstx.exc.WstxIOException: Invalid UTF-8 middle byte 0x2d (at char #1415, byte #127)

Steps to Reproduce

Not Applicable - intermittent.

Root Cause

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"?>


<?xml version="1.0" encoding="ISO-8859-1"?>

Pega uses this header to determine the appropriate character encoding to use.

Published February 16, 2018 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us