Unexpected character encountered while parsing value

[SteveGregory]

I am getting the following error when requesting log data via the SboRestProvider

"Unexpected character encountered while parsing value"

It is happening on about 10% of logs.

Has anyone seen this before?

[JeffBowman]

Hi Steven,

Any way you can turn on Trace level logging in Smart Connector as well as turning on CspClient logging (assuming SboRestProvider) or EwsClient logging (assuming SoapRestProvider). I am wondering what SBO is actually returning.

Regards,

-Jeff

[JeffBowman · Accepted solution]

Hi Steven,

I looked into this, and I believe it has to do with the amount of trend data that is being read by the server and then cached in the In-Memory cache in Smart Connector.

What happens is that every time Trends Samples are requested, Smart Connector will send requests for that range of values and save them in the In-Memory cache. These values that are saved in the In-Memory cache are saved permanently. As you can imagine over time, these caches can get quite gigantic per trend log. I am thinking that eventually, it gets so huge that the Json Serializer cannot deserialize the whole object, and we end up with this error, also may explain issue with certain time ranges never coming back, perhaps saving the data into the cache doesn’t happen after a certain size, and it is pulling out stale data. (but somehow deserializes OK)

In any case, the Rest Providers (both EWS and SOAP), likely will have the same issue as they both cache trend samples from EBO.

I am working on a ‘fix’ that will only save retrieved trend samples for only 5 minutes before removing them. That way, it should be there long enough to finish any ‘paging’ a client wants, but at the same time, removing them as to not let the in-memory cache get gigantic, and become un-manageable.

This release should be available today or tomorrow.

Regards,

-Jeff