Skip to content

Web Service Sender ParseError Invalid byte 1 of 1-byte UTF-8 sequence. #6290

Answered by nicovn
phommata asked this question in Q&A
Discussion options

You must be logged in to vote

Looks like a known bug in Mirth, where Mirth is unable to parse the web service WSDL if the WSDL contains non-ascii standard characters:

`If you get an error message, e.g. “Get Operations fails with Method failed: 500 Internal Server Error” this can be caused by non standard ASCII characters in the WSDL returned by the web service; e.g. accented characters.

The current version of Mirth Connect doesn’t have an option to define the encoding for a web service client - and uses the default operating system encoding (windows-1252 in most cases) which is in fact incorrect (should be UTF-8).

But as a workaround you can override the “default” encoding in your mcservice.vmoptions file.

Please note…

Replies: 2 comments 1 reply

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
1 reply
@phommata
Comment options

Answer selected by phommata
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants