New posts are disabled while we improve the user experience.

You can browse the site, or for urgent issues, raise a query at MyAccount.

question

Upvotes
39 0 4 10

Unable to find valid ceritication path to requested target (RTO (Real Time Optimizid))

Hello,


I am trying to establish an RTO v2 connection using WebSocket with Java. I downloaded the class named "MarketPriceRdpGwClientCredAuth" from the following GitHub link: [https://github.com/Refinitiv/websocket-api/blob/master/Applications/Examples/RDP/java/MarketPriceRdpGwClientCredAuth.java](https://github.com/Refinitiv/websocket-api/blob/master/Applications/Examples/RDP/java/MarketPriceRdpGwClientCredAuth.java), and I attempted to run it with the parameters below.

However, I am encountering the following error:


1-2.jpg


To verify whether I can connect successfully, I also tried to connect using the RTO v2 tool from Speed Guide, but I received the same error:


3.jpg


Could there be an issue with my license information, or am I doing something incorrectly?


Thanks.

#technology#productema-apirefinitiv-realtime-optimisedspeedguide
3.jpg (61.9 KiB)
1-2.jpg (105.4 KiB)
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Upvote
28k 68 18 14

Hello @SelcukYAPICI

Please check the solution of this Certificate issue on the EMA Proxy Connection old post.

icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Hello Wasin,


As you suggested, I captured the traffic using Fiddler. Based on this traffic, I received the output (file is added new 10.txt) from the following address ("https://api.refinitiv.com/auth/oauth2/v2/token"). Does this indicate that my license information is correct? Or is there something else I should check?

new-10.txt (28.3 KiB)
Upvotes
25.1k 68 15 21

Hello @SelcukYAPICI,

Your account information is correct and the application can successfully get a valid token, as shown in your logs. It may be that the debugging proxy that you are using is blocking the websocket requests. At this time, I would suggest to initiate a direct connection without a proxy.

icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Upvotes
39 0 4 10

Hi @Gurpreet,


As you mentioned, I commented out the code that enabled the requests to pass through the proxy. The logs that appear in the console are as attached below. As far as I can see, there hasn't been any change. What do you recommend?

new 12.txt


new-12.txt (27.6 KiB)
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Upvotes
39 0 4 10

Hi @wasin.w,


I made some improvements, but they were not sufficient, as I am still encountering the following error. For some reason, I cannot progress beyond obtaining the token. On the Fiddler side, I can only see the process up to the point where the token is retrieved. Do you have any advice for this situation?


new 11.txt


1729681800661.png



1729681800661.png (320.3 KiB)
new-11.txt (3.5 KiB)
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

The log indicates that it couldn't establish a websocket connection to wss://127.0.0.1:443/WebSocket.

2024-10-23 14:00:56.807021700 Connecting to WebSocket wss://127.0.0.1:443/WebSocket for session1...
2024-10-23 14:00:56.823976400 Connect error for session1:com.neovisionaries.ws.client.WebSocketException: Failed to connect to '127.0.0.1:443': Connection refused: connect
2024-10-23 14:01:01.834688700 Connect error for session1:com.neovisionaries.ws.client.WebSocketException: Failed to connect to '127.0.0.1:443': Connection refused: connect
2024-10-23 14:01:06.838580700 Connect error for session1:com.neovisionaries.ws.client.WebSocketException: Failed to connect to '127.0.0.1:443': Connection refused: connect

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.