Unexpected character error

While harvesting a customer data a following errors occur in the logs and causes the harvest to end prematurely:

ERROR oldingsRequestHelper Error has been occurred at JsonParser while reading data from response. Message: Unexpected character ('s' (code 115)): was expecting a colon to separate field name and value

ERROR oldingsRequestHelper Error has been occurred at JsonParser while reading data from response. Message: Unexpected character ('u' (code 117)): was expecting a colon to separate field name and value

ERROR oldingsRequestHelper Error has been occurred at JsonParser while reading data from response. Message: Still have 47 undecoded bytes, should not call 'feedInput'

While this is obviously a problem with the data, the system should handle it gracefully. The issue seems to be similar to MODOAIPMH-345.

Acceptance criteria

• Investigate possible option of addressing the issue in RMB or outside

• Document findings

• Resolve the issue if possible or create development stories if solution is very involving.

Functional Verification:

Verify that "ERROR oldingsRequestHelper Error has been occurred at JsonParser while reading data from response. " doesn't appear in the logs. - VK

Regression testing:
MMZ: The initial harvest has been run three times in the kiwi-bugfest environment after the hotfix was deployed on March 4th, March 5th and March 6th. Each harvest takes ~16 hours and harvests 8,057,158 records as reported in the bugfest channel. No regression found. Performance and consistency has been improved.

For the smoke test please use tests that are less taxing on the system:
C13784 List records in marc21_withholdings format with start and end date