Multiple errors are observed while executing cloud connector services concurrently.For some SaaS back ends, errors such as “Read timed out” and “Premature end of Content” are observed while invoking cloud connector services at the same time. This issue is found in the Apache HTTP library, which is currently used in CloudStreams.

This issue is resolved.

Null JSON response is not supported by CloudStreams server.If a REST service returns Null as a JSON response, CloudStreams does not recognize or parse the Null JSON response.

This issue is resolved.

CloudStreams Analytics dashboard does not display all the event records for a given date and time.In the CloudStreams Analytics dashboard, the grid in the Event tab does not show all the records for a given date and time. This is because MashZone NextGen considers date columns as dimension columns, as far as aggregation is concerned.

This issue is resolved.

Provider charts in the API Usage tab of the CloudStreams Analytics dashboard also display data for inbound invocations.The provider charts should display data corresponding to the outbound (cloud connector service) invocations only. However, the charts also display data for inbound invocations, with the provider names being displayed as blank values.

This issue is resolved.

Cloud connector services, which allow multiple operations/objects selection, do not persist duplicate operations/objects in the cloud connector service node.

From v10.1, the CloudStreams server allows one resource/operation that can take/return multiple operations/objects in the request or response. For example, in the OData connector, you can select an operation as changeset, which allows you to select multiple operations/objects. For the changeset operation, if you select a combination of “create” and “Account” multiple times, even then it does not get stored in the cloud connector service node.

This issue is resolved.

CloudStreams fails to parse a response when the response formatter/builder is configured as“binary”, and the request Accept header is set to “application/json”.

When the response formatter/builder for a cloud connector service is configured to “binary”, and the Accept header is configured to “application/json”, CloudStreams fails to parse the resulting back end response.

This issue is resolved.