I guess same issue has been mentioned in the jira. Workaround that, they have mentioned is
This occurs when an encoding like UTF-8 is used, because it takes more than 1 byte to represent a character. When an encoding like latin1 is used, this exception does not occur.
You can try it and check