Websocket API didn't receive response after Service Discovery Call - In client Production environ...

...ment

Hi Team,

Background:

In my client's production environment all of sudden, we stop getting any response from Discovery Service and due to this we don't have any WebSocket server URL and port to which we can connect and get the rate.

This was working fine till last weekend and we are able to retrieve the rate without any issues.

In client production, we are using the service from last 3-4 months without any issues.

Note: In my local test environment, I can see the same issue and not able to retrieve any rate

Questions:

Is this something got broker from Refinitiv side?

Is anyone else who is using WebSokcet API facing the same issue?

Appreciate your comments here.

Find more posts tagged with

websockets

rrto

refinitiv-realtime-optimised

Accepted answers

thomas.abraham

@pradeep.badoni it is because service discovery can't handle chunked rest responses. to fix this issue, replace

if (webResponse.ContentLength > 0)

with if (webResponse.GetResponseHeader("Transfer-Encoding").Equals("chunked") || webResponse.ContentLength > 0)

for more details refer this fix RTSDK-5356 in git

https://github.com/Refinitiv/websocket-api/commit/3f8af94525ad9108e4b68e0bcf47bc7fd0f81fe9

All comments

thomas.abraham

Same issue is happening for me too. It was working fine when I left the office on friday but not working when I am back on monday. One thing I noticed is that inside DiscoverServices() method the webResponse.ContentLength is -1 which fails the if condition if (webResponse.ContentLength > 0). When I commented out that condition it is working fine. But don't know why the webResponse.ContentLength is -1. Must be something that need to be sorted out from the Refinitiv's end.

wasin.w

Hello @pradeep.badoni @thomas.abraham

Could you please try the Service Discovery request with the following curl command? Please replace the <access_token> with your Access Token from the RDP Auth Token service (Note: please notice a space between text 'Bearer' and the access token).

curl --location --request GET 'https://api.refinitiv.com/streaming/pricing/v1/'; \
--header 'Accept: application/json' \
--header 'Authorization: Bearer <access token>'

If you still encounter errors from the curl command, I suggest you contact the RDP support team via https://my.refinitiv.com/ website to help you verify the issue.

Please select the "Pricing - Refinitiv Data Platform" product on the my.refinitiv.com website, and give them the following information:

The machine-id that encounters the problem
The URL endpoint ('https://api.refinitiv.com/streaming/pricing/v1/')
The error response message
Date and time that encounters the problem

Hope this helps.

thomas.abraham

@pradeep.badoni it is because service discovery can't handle chunked rest responses. to fix this issue, replace

if (webResponse.ContentLength > 0)

with if (webResponse.GetResponseHeader("Transfer-Encoding").Equals("chunked") || webResponse.ContentLength > 0)

for more details refer this fix RTSDK-5356 in git

https://github.com/Refinitiv/websocket-api/commit/3f8af94525ad9108e4b68e0bcf47bc7fd0f81fe9

pradeep.badoni

Thanks Everyone to look into it and help to resolve the issue.

EXPLORE OUR SITES