RTO login timeout (Connecting without Service Discovery)

thilinaillangasinghe

Hi,

We have a requirement to connect to RTO by directly specifying destination Host/Port. We are in a different VPC and RTO is in another VPC. RTO VPC has a service end-point for RTO and we have an end-point in our VPC to connect to RTO service end-point.

Issue is, login request is timed out without any response. What could be the reason for it ? What can I do from EMA lib side to narrow down this issue further ? Is this guaranteed to be a network issue ?

wireshark output ( 10.97.188.220 is my ec2 and following shows traffic in/out from our eni to the destination service end-point)

3512 230.719202700 10.97.159.159 → 10.97.188.220 TCP 66 14002 → 58643 [RST, ACK] Seq=8 Ack=136 Win=28672 Len=0 TSval=508901598 TSecr=3609793237
3513 230.719206820 10.97.188.220 → 10.97.159.159 TCP 54 59325 → 14002 [RST] Seq=3 Win=0 Len=0
3514 230.719222819 10.97.159.159 → 10.97.188.220 TCP 66 14002 → 59325 [RST, ACK] Seq=8 Ack=3 Win=7 Len=0 TSval=2110366140 TSecr=3609793237
3515 230.719270554 10.97.159.159 → 10.97.188.220 TCP 73 [TCP ACKed unseen segment] 14002 → 56229 [PSH, ACK] Seq=1 Ack=3 Win=7 Len=7 TSval=508901598 TSecr=3609793237

In realtime-sdk (2.0.6.L1) lib timeout occurs (by returning -1) at following method,

Int64 OmmBaseImpl::rsslReactorDispatchLoop( Int64 timeOut, UInt32 count, bool& bMsgDispRcvd )

loggerMsg
    TimeStamp: 19:55:49.060
    ClientName: ChannelCallbackClient
    Severity: Verbose
    Text:    Attempt to connect using
        1] RSSL_CONN_TYPE_SOCKET
        Channel name Channel_1
        Instance Name Consumer_1_49
        RsslReactor 0x0x7faa18035e70
        InterfaceName
        hostName vpce-08e9789ee940521a5-vpc-endpoint-dns-address
        port 14002
        CompressionType None
        tcpNodelay false
        EnableSessionManagement 0
        reconnectAttemptLimit 10000
        reconnectMinDelay 1000 msec
        reconnectMaxDelay 5000 msec
        connectionPingTimeout 60000 msec
        initializationTimeout 10 sec

loggerMsgEnd

loggerMsg
    TimeStamp: 19:55:49.110
    ClientName: ChannelCallbackClient
    Severity: Verbose
    Text:    Received ChannelOpened on channel Channel_1
        Instance Name Consumer_1_49
loggerMsgEnd

loggerMsg
    TimeStamp: 19:55:49.114
    ClientName: ChannelCallbackClient
    Severity: Verbose
    Text:    Successfully created a Reactor and Channel(s)
        Channel name(s) Channel_1
        Instance Name Consumer_1_49
loggerMsgE

Gurpreet

Hello @thilinaillangasinghe,

It is my understanding that the login endpoint for RDP and hence RTO is only available on the internet and not through VPC. Can you open up a route to https://api.refinitiv.com and try again. Once you login and get an access token, this token will now be used for login to the RTO.