RTDS 3.5.1 - Unable to access the Realtime data using testclient over web socket port
we are having a client which is recently upgraded to RTDS 3.5.1 with WebSocket enabled, now the client is trying to test the connection using testclient tool in their tets machine over websocket port(not in the RTDS box).
Unfortunately, they are getting the below error message.
telnet to port 15000 is working from test pc to trep/rtds and testclient tool from ads box also working using 15000.
Client has used the RTDS testclient tool installed in the Murex box and they are getting the below error.
Tool/demo_test-client >./testclient -l stdout -ct ws_json2 -p 15000 -dfile RDMFieldDictionary -u murex2 -S IDN_RDF -itemList INR= -h 10.163.21.4
Number of Connection Count = 1
Host: 10.163.21.4 Port: 15000
Setting rmds connection 0x2c5b658
Connection list count is 1
Channel: 1 disconnected. Reason: WSock read fail on HTTP response from server. Connection reset by peer.
Channel: 1 reconnected.
Channel: 1 disconnected. Reason: WSock read fail on HTTP response from server. Connection reset by peer.
Channel: 1 reconnected.
Channel: 1 disconnected. Reason: WSock read fail on HTTP response from server. Connection reset by peer.
Channel: 1 reconnected.
Channel: 1 disconnected. Reason: WSock read fail on HTTP response from server. Connection reset by peer.
Channel: 1 reconnected.
Channel: 1 disconnected. Reason: WSock read fail on HTTP response from server. Connection reset by peer.
Channel: 1 reconnected.
No service status events received after five seconds.
Service events should be returned immediately.
Data cannot be requested until services are available.
Channel: 1 disconnected. Reason: WSock read fail on HTTP response from the server. Connection reset by peer.
I can run it properly.
Then, I run testclient on another machine.
./testclient -l stdout -ct ws_json2 -p 15000 -dfile RDMFieldDictionary -S ELEKTRON_DD -itemList INR= -h 192.168.27.93
It could be a configuration or network issue. The client should run testclient on the RTDS box to verify the configuration. If testclient on the RTDS box can retrieve the data properly, it could be a network issue.
I got the same error if I used an incorrect TCP port, such as 14002 which is an RSSL port.
-bash-4.2$ ./testclient -l stdout -ct ws_json2 -p 14002 -dfile RDMFieldDictionary -S ELEKTRON_DD -itemList INR= -h 192.168.27.93 Number of Connection Count = 1 Host: 192.168.27.93 Port: 14002 Setting connection 0x1a596a8 Connection list count is 1 Channel: 1 disconnected. Reason: WSock read fail on HTTP response from server. Connection reset by peer. Channel: 1 reconnected. Channel: 1 disconnected. Reason: WSock read fail on HTTP response from server. Connection reset by peer. Channel: 1 reconnected. Channel: 1 disconnected. Reason: WSock read fail on HTTP response from server. Connection reset by peer. Channel: 1 reconnected. Channel: 1 disconnected. Reason: WSock read fail on HTTP response from server. Connection reset by peer. Channel: 1 reconnected. Channel: 1 disconnected. Reason: WSock read fail on HTTP response from server. Connection reset by peer. Channel: 1 reconnected.
The client can directly contact the RTDS support team via MyRefinitiv (https://my.refinitiv.com/content/mytr/en/helpandsupport.html) to verify the problem.