RTO with EMA: evetual login success after many timeout messages

Hi everyone,

I have a test RTO environment with a valid client id and secret credentials (I use RTO v2 authentication with EMA).

Here is my config (programmatic, not using Emaconfig.xml):

 Map elementMap = EmaFactory.createMap();
        ElementList elementList = EmaFactory.createElementList();
        ElementList innerElementList = EmaFactory.createElementList();

        innerElementList.add(EmaFactory.createElementEntry().ascii("Channel", "Subscription_Channel_RTO_5d179423-1ee9-454a-a7a7-61d6b48d2eb2"));
        elementMap.add(EmaFactory.createMapEntry().keyAscii("Subscription_Consumer_RTO_5d179423-1ee9-454a-a7a7-61d6b48d2eb2", MapEntry.MapAction.ADD, innerElementList));
        innerElementList.clear();

        elementList.add(EmaFactory.createElementEntry().map("ConsumerList", elementMap));
        elementMap.clear();

        Map configDb = EmaFactory.createMap();
        configDb.add(EmaFactory.createMapEntry().keyAscii("ConsumerGroup", MapEntry.MapAction.ADD, elementList));
        elementList.clear();

//     ChannelType::RSSL_ENCRYPTED - Https tunnel connection type, RTO does not support other channel types
        innerElementList.add(EmaFactory.createElementEntry().ascii("ChannelType", "ChannelType::RSSL_ENCRYPTED"));
        innerElementList.add(EmaFactory.createElementEntry().ascii("CompressionType", "CompressionType::None"));
        innerElementList.add(EmaFactory.createElementEntry().intValue("GuaranteedOutputBuffers", 5000));

        innerElementList.add(EmaFactory.createElementEntry().ascii("Location", "eu-west-1"));

        innerElementList.add(EmaFactory.createElementEntry().intValue("EnableSessionManagement", 1));
        if (logger.isTraceEnabled()) {
            innerElementList.add(EmaFactory.createElementEntry().intValue("XmlTraceToStdout", 1));
        }
        elementMap.add(EmaFactory.createMapEntry().keyAscii(channelName, MapEntry.MapAction.ADD, innerElementList));
        innerElementList.clear();
        elementList.add(EmaFactory.createElementEntry().map("ChannelList", elementMap));
        elementMap.clear();

        configDb.add(EmaFactory.createMapEntry().keyAscii("ChannelGroup", MapEntry.MapAction.ADD, elementList));
        elementList.clear();
        return configDb;

When I run this config multiple times, I arbitrary recieve either:

1. The repeating login failure message:

2024-03-25 13:46:08:915  WARN pool-1-thread-5 access.OmmConsumerImpl:619 - loggerMsg
    ClientName: ChannelCallbackClient
    Severity: Warning
    Text:    Received ChannelDownReconnecting event on channel Subscription_Channel_RTO_5d179423-1ee9-454a-a7a7-61d6b48d2eb2
    RsslReactor @36beee46
    RsslChannel @78a56fbe
    Error Id 0
    Internal sysError 0
    Error Location Reactor.processWorkerEvent
    Error text Error - exceeded initialization timeout (5 s)
loggerMsgEnd

ending with :

invalid usage: Exception Type='OmmInvalidUsageException', Text='login failed (timed out after waiting 45000 milliseconds) for ', Error Code='-4052'

2. Or I receive login success message:

<loggerMsg
    ClientName: ChannelCallbackClient
    Severity: Warning
    Text:    Received ChannelDownReconnecting event on channel Subscription_Channel_RTO_96e798fc-8dd4-48c5-83a6-0e3b269967c0
    RsslReactor @557c7e5
    RsslChannel @1297d6e8
    Error Id 0
    Internal sysError 0
    Error Location Reactor.processWorkerEvent
    Error text Error - exceeded initialization timeout (5 s)
loggerMsgEnd>

The success and fail scenarios are arbitrary between one run and another!

Can you provide some additional info on why this is (or at least seems to me) arbitrary?

Thank you

Find more posts tagged with

java

rrto

ema-api

#technology

Accepted answers

Jirapongse

@DimAngelNX

Thank you for reaching out to us.

Typically, the error indicates that the application is unable to connect to the server. This could be the server or network issue.

You may try another location, such as eu-central-1. Please share the full configuration code and the version of EMA used by the application.

All comments

Jirapongse

@DimAngelNX

Thank you for reaching out to us.

Typically, the error indicates that the application is unable to connect to the server. This could be the server or network issue.

You may try another location, such as eu-central-1. Please share the full configuration code and the version of EMA used by the application.

DimAngelNX

In addition to my first post, here is the DEBUG level log:

2024-03-25 15:55:55:501  INFO pool-1-thread-1 access.OmmConsumerImpl:127 - loggerMsg
    ClientName: EmaConfig
    Severity: Info
    Text:    Missing, unreadable or empty file configuration, path=[C:\Users\dimitar.angelov\Desktop\Neoxam\Projects\Git\realtime2\refinitivdatafeed\EmaConfig.xml]
loggerMsgEnd


2024-03-25 15:55:55:800 DEBUG pool-1-thread-1 protocol.RequestAddCookies:123 - CookieSpec selected: default
2024-03-25 15:55:55:807 DEBUG pool-1-thread-1 protocol.RequestAuthCache:77 - Auth cache not set in the context
2024-03-25 15:55:55:808 DEBUG pool-1-thread-1 conn.PoolingHttpClientConnectionManager:267 - Connection request: [route: {s}->https://api.refinitiv.com:443][total available: 0; route allocated: 0 of 2; total allocated: 0 of 20]
2024-03-25 15:55:55:816 DEBUG pool-1-thread-1 conn.PoolingHttpClientConnectionManager:312 - Connection leased: [id: 0][route: {s}->https://api.refinitiv.com:443][total available: 0; route allocated: 1 of 2; total allocated: 1 of 20]
2024-03-25 15:55:55:817 DEBUG pool-1-thread-1 execchain.MainClientExec:234 - Opening connection {s}->https://api.refinitiv.com:443
2024-03-25 15:55:55:819 DEBUG pool-1-thread-1 conn.DefaultHttpClientConnectionOperator:139 - Connecting to api.refinitiv.com/99.83.242.11:443
2024-03-25 15:55:55:819 DEBUG pool-1-thread-1 ssl.SSLConnectionSocketFactory:366 - Connecting socket to api.refinitiv.com/99.83.242.11:443 with timeout 0
2024-03-25 15:55:55:841 DEBUG pool-1-thread-1 ssl.SSLConnectionSocketFactory:430 - Enabled protocols: [TLSv1.2]
2024-03-25 15:55:55:841 DEBUG pool-1-thread-1 ssl.SSLConnectionSocketFactory:431 - Enabled cipher suites:[TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384, TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384, TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256, TLS_DHE_RSA_WITH_AES_256_GCM_SHA384, TLS_DHE_DSS_WITH_AES_256_GCM_SHA384, TLS_DHE_RSA_WITH_AES_128_GCM_SHA256, TLS_DHE_DSS_WITH_AES_128_GCM_SHA256, TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384, TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256, TLS_DHE_RSA_WITH_AES_256_CBC_SHA256, TLS_DHE_DSS_WITH_AES_256_CBC_SHA256, TLS_DHE_RSA_WITH_AES_128_CBC_SHA256, TLS_DHE_DSS_WITH_AES_128_CBC_SHA256, TLS_ECDH_ECDSA_WITH_AES_256_GCM_SHA384, TLS_ECDH_RSA_WITH_AES_256_GCM_SHA384, TLS_ECDH_ECDSA_WITH_AES_128_GCM_SHA256, TLS_ECDH_RSA_WITH_AES_128_GCM_SHA256, TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA384, TLS_ECDH_RSA_WITH_AES_256_CBC_SHA384, TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA256, TLS_ECDH_RSA_WITH_AES_128_CBC_SHA256, TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA, TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_DSS_WITH_AES_256_CBC_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_DSS_WITH_AES_128_CBC_SHA, TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA, TLS_ECDH_RSA_WITH_AES_256_CBC_SHA, TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA, TLS_ECDH_RSA_WITH_AES_128_CBC_SHA, TLS_RSA_WITH_AES_256_GCM_SHA384, TLS_RSA_WITH_AES_128_GCM_SHA256, TLS_RSA_WITH_AES_256_CBC_SHA256, TLS_RSA_WITH_AES_128_CBC_SHA256, TLS_RSA_WITH_AES_256_CBC_SHA, TLS_RSA_WITH_AES_128_CBC_SHA, TLS_EMPTY_RENEGOTIATION_INFO_SCSV]
2024-03-25 15:55:55:842 DEBUG pool-1-thread-1 ssl.SSLConnectionSocketFactory:435 - Starting handshake
2024-03-25 15:55:55:993 DEBUG pool-1-thread-1 ssl.SSLConnectionSocketFactory:465 - Secure session established
2024-03-25 15:55:55:994 DEBUG pool-1-thread-1 ssl.SSLConnectionSocketFactory:466 -  negotiated protocol: TLSv1.2
2024-03-25 15:55:55:994 DEBUG pool-1-thread-1 ssl.SSLConnectionSocketFactory:467 -  negotiated cipher suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
2024-03-25 15:55:55:994 DEBUG pool-1-thread-1 ssl.SSLConnectionSocketFactory:475 -  peer principal: CN=api.refinitiv.com, O=REFINITIV US LLC, ST=New York, C=US
2024-03-25 15:55:55:994 DEBUG pool-1-thread-1 ssl.SSLConnectionSocketFactory:484 -  peer alternative names: [api.refinitiv.com, ap-southeast-1-api.refinitiv.com, eu-west-1-api.refinitiv.com, us-east-1-api.refinitiv.com]
2024-03-25 15:55:55:995 DEBUG pool-1-thread-1 ssl.SSLConnectionSocketFactory:488 -  issuer principal: CN=COMODO RSA Organization Validation Secure Server CA, O=COMODO CA Limited, L=Salford, ST=Greater Manchester, C=GB
2024-03-25 15:55:55:997 DEBUG pool-1-thread-1 conn.DefaultHttpClientConnectionOperator:146 - Connection established 10.33.2.130:54167<->99.83.242.11:443
2024-03-25 15:55:55:997 DEBUG pool-1-thread-1 conn.DefaultManagedHttpClientConnection:88 - http-outgoing-0: set socket timeout to 45000
2024-03-25 15:55:55:997 DEBUG pool-1-thread-1 execchain.MainClientExec:255 - Executing request POST /auth/oauth2/v2/token HTTP/1.1
2024-03-25 15:55:55:997 DEBUG pool-1-thread-1 execchain.MainClientExec:260 - Target auth state: UNCHALLENGED
2024-03-25 15:55:55:998 DEBUG pool-1-thread-1 execchain.MainClientExec:266 - Proxy auth state: UNCHALLENGED
2024-03-25 15:55:55:999 DEBUG pool-1-thread-1 http.headers:133 - http-outgoing-0 >> POST /auth/oauth2/v2/token HTTP/1.1
2024-03-25 15:55:55:999 DEBUG pool-1-thread-1 http.headers:136 - http-outgoing-0 >> Content-Length: 141
2024-03-25 15:55:55:999 DEBUG pool-1-thread-1 http.headers:136 - http-outgoing-0 >> Content-Type: application/x-www-form-urlencoded; charset=UTF-8
2024-03-25 15:55:55:999 DEBUG pool-1-thread-1 http.headers:136 - http-outgoing-0 >> Host: api.refinitiv.com
2024-03-25 15:55:55:999 DEBUG pool-1-thread-1 http.headers:136 - http-outgoing-0 >> Connection: Keep-Alive
2024-03-25 15:55:55:999 DEBUG pool-1-thread-1 http.headers:136 - http-outgoing-0 >> User-Agent: Apache-HttpClient/4.5.14 (Java/1.8.0_312)
2024-03-25 15:55:55:999 DEBUG pool-1-thread-1 http.headers:136 - http-outgoing-0 >> Accept-Encoding: gzip,deflate
2024-03-25 15:55:55:999 DEBUG pool-1-thread-1 http.wire:73 - http-outgoing-0 >> "POST /auth/oauth2/v2/token HTTP/1.1[\r][\n]"
2024-03-25 15:55:55:999 DEBUG pool-1-thread-1 http.wire:73 - http-outgoing-0 >> "Content-Length: 141[\r][\n]"
2024-03-25 15:55:56:000 DEBUG pool-1-thread-1 http.wire:73 - http-outgoing-0 >> "Content-Type: application/x-www-form-urlencoded; charset=UTF-8[\r][\n]"
2024-03-25 15:55:56:000 DEBUG pool-1-thread-1 http.wire:73 - http-outgoing-0 >> "Host: api.refinitiv.com[\r][\n]"
2024-03-25 15:55:56:000 DEBUG pool-1-thread-1 http.wire:73 - http-outgoing-0 >> "Connection: Keep-Alive[\r][\n]"
2024-03-25 15:55:56:000 DEBUG pool-1-thread-1 http.wire:73 - http-outgoing-0 >> "User-Agent: Apache-HttpClient/4.5.14 (Java/1.8.0_312)[\r][\n]"
2024-03-25 15:55:56:000 DEBUG pool-1-thread-1 http.wire:73 - http-outgoing-0 >> "Accept-Encoding: gzip,deflate[\r][\n]"
2024-03-25 15:55:56:000 DEBUG pool-1-thread-1 http.wire:73 - http-outgoing-0 >> "[\r][\n]"
2024-03-25 15:55:56:000 DEBUG pool-1-thread-1 http.wire:87 - http-outgoing-0 >> "grant_type=client_credentials&client_id=GE-QTEKECPVOCCE&scope=trapi.streaming.pricing.read&client_secret=0d3f84d4-a82b-4657-8183-2103edd9ee64"
2024-03-25 15:55:56:216 DEBUG pool-1-thread-1 http.wire:73 - http-outgoing-0 << "HTTP/1.1 200 OK[\r][\n]"
2024-03-25 15:55:56:216 DEBUG pool-1-thread-1 http.wire:73 - http-outgoing-0 << "Date: Mon, 25 Mar 2024 14:55:56 GMT[\r][\n]"
2024-03-25 15:55:56:217 DEBUG pool-1-thread-1 http.wire:73 - http-outgoing-0 << "Content-Type: application/json[\r][\n]"
2024-03-25 15:55:56:217 DEBUG pool-1-thread-1 http.wire:73 - http-outgoing-0 << "Content-Length: 90[\r][\n]"
2024-03-25 15:55:56:217 DEBUG pool-1-thread-1 http.wire:73 - http-outgoing-0 << "Connection: keep-alive[\r][\n]"
2024-03-25 15:55:56:217 DEBUG pool-1-thread-1 http.wire:73 - http-outgoing-0 << "X-Amzn-Trace-Id: Root=1-6601907c-0a0e872272d31e03217251f4[\r][\n]"
2024-03-25 15:55:56:217 DEBUG pool-1-thread-1 http.wire:73 - http-outgoing-0 << "X-Served-By: region=eu-west-1; cid=809c49694c1c49fab06a8c3ea6b2d754[\r][\n]"
2024-03-25 15:55:56:218 DEBUG pool-1-thread-1 http.wire:73 - http-outgoing-0 << "X-Tr-Requestid: 391c7d8a-5632-4f43-91cc-7f27661a0453[\r][\n]"
2024-03-25 15:55:56:218 DEBUG pool-1-thread-1 http.wire:73 - http-outgoing-0 << "[\r][\n]"
2024-03-25 15:55:56:218 DEBUG pool-1-thread-1 http.wire:87 - http-outgoing-0 << "{ "expires_in":7199, "token_type":"Bearer", "access_token":"xtsaIXki90CGuNsoUotI9xwDnysO"}"
2024-03-25 15:55:56:221 DEBUG pool-1-thread-1 http.headers:122 - http-outgoing-0 << HTTP/1.1 200 OK
2024-03-25 15:55:56:221 DEBUG pool-1-thread-1 http.headers:125 - http-outgoing-0 << Date: Mon, 25 Mar 2024 14:55:56 GMT
2024-03-25 15:55:56:221 DEBUG pool-1-thread-1 http.headers:125 - http-outgoing-0 << Content-Type: application/json
2024-03-25 15:55:56:227 DEBUG pool-1-thread-1 http.headers:125 - http-outgoing-0 << Content-Length: 90
2024-03-25 15:55:56:227 DEBUG pool-1-thread-1 http.headers:125 - http-outgoing-0 << Connection: keep-alive
2024-03-25 15:55:56:227 DEBUG pool-1-thread-1 http.headers:125 - http-outgoing-0 << X-Amzn-Trace-Id: Root=1-6601907c-0a0e872272d31e03217251f4
2024-03-25 15:55:56:227 DEBUG pool-1-thread-1 http.headers:125 - http-outgoing-0 << X-Served-By: region=eu-west-1; cid=809c49694c1c49fab06a8c3ea6b2d754
2024-03-25 15:55:56:227 DEBUG pool-1-thread-1 http.headers:125 - http-outgoing-0 << X-Tr-Requestid: 391c7d8a-5632-4f43-91cc-7f27661a0453
2024-03-25 15:55:56:229 DEBUG pool-1-thread-1 execchain.MainClientExec:285 - Connection can be kept alive indefinitely
2024-03-25 15:55:56:233 DEBUG pool-1-thread-1 conn.PoolingHttpClientConnectionManager:344 - Connection [id: 0][route: {s}->https://api.refinitiv.com:443] can be kept alive indefinitely
2024-03-25 15:55:56:233 DEBUG pool-1-thread-1 conn.DefaultManagedHttpClientConnection:88 - http-outgoing-0: set socket timeout to 0
2024-03-25 15:55:56:234 DEBUG pool-1-thread-1 conn.PoolingHttpClientConnectionManager:351 - Connection released: [id: 0][route: {s}->https://api.refinitiv.com:443][total available: 1; route allocated: 1 of 2; total allocated: 1 of 20]
2024-03-25 15:55:56:236 DEBUG pool-1-thread-1 conn.PoolingHttpClientConnectionManager:411 - Connection manager is shutting down
2024-03-25 15:55:56:237 DEBUG pool-1-thread-1 conn.DefaultManagedHttpClientConnection:79 - http-outgoing-0: Close connection
2024-03-25 15:55:56:238 DEBUG pool-1-thread-1 conn.PoolingHttpClientConnectionManager:434 - Connection manager shut down
2024-03-25 15:55:56:239 DEBUG pool-1-thread-1 protocol.RequestAddCookies:123 - CookieSpec selected: default
2024-03-25 15:55:56:239 DEBUG pool-1-thread-1 protocol.RequestAuthCache:77 - Auth cache not set in the context
2024-03-25 15:55:56:239 DEBUG pool-1-thread-1 conn.PoolingHttpClientConnectionManager:267 - Connection request: [route: {s}->https://api.refinitiv.com:443][total available: 0; route allocated: 0 of 2; total allocated: 0 of 20]
2024-03-25 15:55:56:239 DEBUG pool-1-thread-1 conn.PoolingHttpClientConnectionManager:312 - Connection leased: [id: 1][route: {s}->https://api.refinitiv.com:443][total available: 0; route allocated: 1 of 2; total allocated: 1 of 20]
2024-03-25 15:55:56:239 DEBUG pool-1-thread-1 execchain.MainClientExec:234 - Opening connection {s}->https://api.refinitiv.com:443
2024-03-25 15:55:56:240 DEBUG pool-1-thread-1 conn.DefaultHttpClientConnectionOperator:139 - Connecting to api.refinitiv.com/99.83.242.11:443
2024-03-25 15:55:56:240 DEBUG pool-1-thread-1 ssl.SSLConnectionSocketFactory:366 - Connecting socket to api.refinitiv.com/99.83.242.11:443 with timeout 0
2024-03-25 15:55:56:246 DEBUG pool-1-thread-1 ssl.SSLConnectionSocketFactory:430 - Enabled protocols: [TLSv1.2]
2024-03-25 15:55:56:246 DEBUG pool-1-thread-1 ssl.SSLConnectionSocketFactory:431 - Enabled cipher suites:[TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384, TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384, TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256, TLS_DHE_RSA_WITH_AES_256_GCM_SHA384, TLS_DHE_DSS_WITH_AES_256_GCM_SHA384, TLS_DHE_RSA_WITH_AES_128_GCM_SHA256, TLS_DHE_DSS_WITH_AES_128_GCM_SHA256, TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384, TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256, TLS_DHE_RSA_WITH_AES_256_CBC_SHA256, TLS_DHE_DSS_WITH_AES_256_CBC_SHA256, TLS_DHE_RSA_WITH_AES_128_CBC_SHA256, TLS_DHE_DSS_WITH_AES_128_CBC_SHA256, TLS_ECDH_ECDSA_WITH_AES_256_GCM_SHA384, TLS_ECDH_RSA_WITH_AES_256_GCM_SHA384, TLS_ECDH_ECDSA_WITH_AES_128_GCM_SHA256, TLS_ECDH_RSA_WITH_AES_128_GCM_SHA256, TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA384, TLS_ECDH_RSA_WITH_AES_256_CBC_SHA384, TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA256, TLS_ECDH_RSA_WITH_AES_128_CBC_SHA256, TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA, TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_DSS_WITH_AES_256_CBC_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_DSS_WITH_AES_128_CBC_SHA, TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA, TLS_ECDH_RSA_WITH_AES_256_CBC_SHA, TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA, TLS_ECDH_RSA_WITH_AES_128_CBC_SHA, TLS_RSA_WITH_AES_256_GCM_SHA384, TLS_RSA_WITH_AES_128_GCM_SHA256, TLS_RSA_WITH_AES_256_CBC_SHA256, TLS_RSA_WITH_AES_128_CBC_SHA256, TLS_RSA_WITH_AES_256_CBC_SHA, TLS_RSA_WITH_AES_128_CBC_SHA, TLS_EMPTY_RENEGOTIATION_INFO_SCSV]
2024-03-25 15:55:56:246 DEBUG pool-1-thread-1 ssl.SSLConnectionSocketFactory:435 - Starting handshake
2024-03-25 15:55:56:285 DEBUG pool-1-thread-1 ssl.SSLConnectionSocketFactory:465 - Secure session established
2024-03-25 15:55:56:285 DEBUG pool-1-thread-1 ssl.SSLConnectionSocketFactory:466 -  negotiated protocol: TLSv1.2
2024-03-25 15:55:56:286 DEBUG pool-1-thread-1 ssl.SSLConnectionSocketFactory:467 -  negotiated cipher suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
2024-03-25 15:55:56:286 DEBUG pool-1-thread-1 ssl.SSLConnectionSocketFactory:475 -  peer principal: CN=api.refinitiv.com, O=REFINITIV US LLC, ST=New York, C=US
2024-03-25 15:55:56:286 DEBUG pool-1-thread-1 ssl.SSLConnectionSocketFactory:484 -  peer alternative names: [api.refinitiv.com, ap-southeast-1-api.refinitiv.com, eu-west-1-api.refinitiv.com, us-east-1-api.refinitiv.com]
2024-03-25 15:55:56:286 DEBUG pool-1-thread-1 ssl.SSLConnectionSocketFactory:488 -  issuer principal: CN=COMODO RSA Organization Validation Secure Server CA, O=COMODO CA Limited, L=Salford, ST=Greater Manchester, C=GB
2024-03-25 15:55:56:286 DEBUG pool-1-thread-1 conn.DefaultHttpClientConnectionOperator:146 - Connection established 10.33.2.130:54169<->99.83.242.11:443
2024-03-25 15:55:56:286 DEBUG pool-1-thread-1 conn.DefaultManagedHttpClientConnection:88 - http-outgoing-1: set socket timeout to 45000
2024-03-25 15:55:56:287 DEBUG pool-1-thread-1 execchain.MainClientExec:255 - Executing request GET /streaming/pricing/v1/?dataformat=rwf&transport=tcp HTTP/1.1
2024-03-25 15:55:56:287 DEBUG pool-1-thread-1 execchain.MainClientExec:266 - Proxy auth state: UNCHALLENGED
2024-03-25 15:55:56:287 DEBUG pool-1-thread-1 http.headers:133 - http-outgoing-1 >> GET /streaming/pricing/v1/?dataformat=rwf&transport=tcp HTTP/1.1
2024-03-25 15:55:56:287 DEBUG pool-1-thread-1 http.headers:136 - http-outgoing-1 >> Authorization: Bearer xtsaIXki90CGuNsoUotI9xwDnysO
2024-03-25 15:55:56:287 DEBUG pool-1-thread-1 http.headers:136 - http-outgoing-1 >> Host: api.refinitiv.com
2024-03-25 15:55:56:287 DEBUG pool-1-thread-1 http.headers:136 - http-outgoing-1 >> Connection: Keep-Alive
2024-03-25 15:55:56:287 DEBUG pool-1-thread-1 http.headers:136 - http-outgoing-1 >> User-Agent: Apache-HttpClient/4.5.14 (Java/1.8.0_312)
2024-03-25 15:55:56:287 DEBUG pool-1-thread-1 http.headers:136 - http-outgoing-1 >> Accept-Encoding: gzip,deflate
2024-03-25 15:55:56:287 DEBUG pool-1-thread-1 http.wire:73 - http-outgoing-1 >> "GET /streaming/pricing/v1/?dataformat=rwf&transport=tcp HTTP/1.1[\r][\n]"
2024-03-25 15:55:56:287 DEBUG pool-1-thread-1 http.wire:73 - http-outgoing-1 >> "Authorization: Bearer xtsaIXki90CGuNsoUotI9xwDnysO[\r][\n]"
2024-03-25 15:55:56:288 DEBUG pool-1-thread-1 http.wire:73 - http-outgoing-1 >> "Host: api.refinitiv.com[\r][\n]"
2024-03-25 15:55:56:288 DEBUG pool-1-thread-1 http.wire:73 - http-outgoing-1 >> "Connection: Keep-Alive[\r][\n]"
2024-03-25 15:55:56:288 DEBUG pool-1-thread-1 http.wire:73 - http-outgoing-1 >> "User-Agent: Apache-HttpClient/4.5.14 (Java/1.8.0_312)[\r][\n]"
2024-03-25 15:55:56:288 DEBUG pool-1-thread-1 http.wire:73 - http-outgoing-1 >> "Accept-Encoding: gzip,deflate[\r][\n]"
2024-03-25 15:55:56:288 DEBUG pool-1-thread-1 http.wire:73 - http-outgoing-1 >> "[\r][\n]"
2024-03-25 15:55:56:555 DEBUG pool-1-thread-1 http.wire:73 - http-outgoing-1 << "HTTP/1.1 200 OK[\r][\n]"
2024-03-25 15:55:56:556 DEBUG pool-1-thread-1 http.wire:73 - http-outgoing-1 << "Date: Mon, 25 Mar 2024 14:55:56 GMT[\r][\n]"
2024-03-25 15:55:56:556 DEBUG pool-1-thread-1 http.wire:73 - http-outgoing-1 << "Content-Type: application/json; charset=utf-8[\r][\n]"
2024-03-25 15:55:56:556 DEBUG pool-1-thread-1 http.wire:73 - http-outgoing-1 << "Content-Length: 319[\r][\n]"
2024-03-25 15:55:56:557 DEBUG pool-1-thread-1 http.wire:73 - http-outgoing-1 << "Connection: keep-alive[\r][\n]"
2024-03-25 15:55:56:557 DEBUG pool-1-thread-1 http.wire:73 - http-outgoing-1 << "Access-Control-Allow-Origin: *[\r][\n]"
2024-03-25 15:55:56:557 DEBUG pool-1-thread-1 http.wire:73 - http-outgoing-1 << "Access-Control-Expose-Headers: content-encoding, content-length, x-tr-requestid, x-tr-correlationid[\r][\n]"
2024-03-25 15:55:56:557 DEBUG pool-1-thread-1 http.wire:73 - http-outgoing-1 << "Content-Encoding: gzip[\r][\n]"
2024-03-25 15:55:56:557 DEBUG pool-1-thread-1 http.wire:73 - http-outgoing-1 << "X-Amzn-Trace-Id: Root=1-6601907c-478ac7c6442705630e91229f[\r][\n]"
2024-03-25 15:55:56:558 DEBUG pool-1-thread-1 http.wire:73 - http-outgoing-1 << "X-Served-By: region=eu-west-1; cid=809c49694c1c49fab06a8c3ea6b2d754[\r][\n]"
2024-03-25 15:55:56:558 DEBUG pool-1-thread-1 http.wire:73 - http-outgoing-1 << "X-Tr-Requestid: 78a4dd8c-caac-4191-a2dd-2c3d9bd3489a[\r][\n]"
2024-03-25 15:55:56:558 DEBUG pool-1-thread-1 http.wire:73 - http-outgoing-1 << "[\r][\n]"
2024-03-25 15:55:56:558 DEBUG pool-1-thread-1 http.wire:73 - http-outgoing-1 << "[0x1f][0x8b][0x8][0x0][0x0][0x0][0x0][0x0][0x0][0xff][0xbc][0x95][0xc1]n[0xc3] [0xc][0x86][0xdf][0xc5]g[0xa8]Z[0xb6]S[0x1e]`/Q[0xf5][0xe0]%t[0xb3][0xd4][0x0]2N"[0xad][0xea][0xbb]O[0xd5][0xb4]6[0xc9]N#[0xc0][0xd1](F[0x9f][0xfd][\n]"
2024-03-25 15:55:56:558 DEBUG pool-1-thread-1 http.wire:73 - http-outgoing-1 << "W[0x88][0x96]Gjm[0x84][0xe6]x[0x85][0xe0]Y[0xa0]9[0xbc][0xee][0xf7]F[0xc1][0xc5][0xb7]([0xe4][0x1d]4G[0xc0][0xa0][0x9d]g[0xf9][0xb4][0x18]E[0x1f][0x10]N[\n]"
2024-03-25 15:55:56:559 DEBUG pool-1-thread-1 http.wire:73 - http-outgoing-1 << "[0x84][0xd1][0xc5][0x9f][0x6][0x90]6[0x80][0x82][0xc0]~[0xa4][0xce]24[0x80]S[0x4][0x5][0xd6]u[0xc1][0x93][0xbb][0xb1][0xbc]@[0xe3][0x14][0xf5]A[0xc7]~[0xe7][0x83]PO_[0xb6][0xd3][0x81][0xa9]%[0xf7][0xa1]1[0xd0][0x8e][0xed][0x99][0x1c][0x9][0x8d];g[0x5][0x14]t([0xf8][0xe6][0xb9]G[0xb9][0xc3][0xf0]t[0x86][0xd3]M[0xfd][0x3]W[0xad]N[0xde][0xb3][0xc][0xf0]Rk[0x80]<[0xb8][0xa6](n[0xf4][0xc3]6=f[0x17]T[0xd0]c[0x81][0xab]V'i[0xfb]^[0xf]PV[0x8f][0xec][0xb8][0x5][0xf5][0xb0][0x83]n[0xad][0x13][0xc6]K[0x92][0x1c][0xf3][0xf6][0xd2]j,Q[0xd5][0xa2]N[0xd8][0xf3][0x1f][0xf4][0x82]R[0xe4]F-+[0xc4]d[0x13][0x15][0x8f][0xde][\n]"
2024-03-25 15:55:56:559 DEBUG pool-1-thread-1 http.wire:87 - http-outgoing-1 << "*[0xfc]B[0xaa]g[0x91][0xb6][0xd9][0x19]qY[0x3]2A[0x16][0xcc]~[0x88]:[0xf9][0x99]x[0xf4][0x96][0xce]~[0x6][0xa9][0x9e]E[0xc2]Z[0x97][0xc4][0x5][0xb3][0xcf][0x7]Y!{[0xb3]!{S+{3[0xcf][0xde]lX[0xab][0xa9][0x95][0xfd]v[0xc8][0x8d][0xd9][0x9f]n[0xdf][0x1][0x0][0x0][0xff][0xff][0xac],)qQ[0xc][0x0][0x0]"
2024-03-25 15:55:56:559 DEBUG pool-1-thread-1 http.headers:122 - http-outgoing-1 << HTTP/1.1 200 OK
2024-03-25 15:55:56:559 DEBUG pool-1-thread-1 http.headers:125 - http-outgoing-1 << Date: Mon, 25 Mar 2024 14:55:56 GMT
2024-03-25 15:55:56:559 DEBUG pool-1-thread-1 http.headers:125 - http-outgoing-1 << Content-Type: application/json; charset=utf-8
2024-03-25 15:55:56:560 DEBUG pool-1-thread-1 http.headers:125 - http-outgoing-1 << Content-Length: 319
2024-03-25 15:55:56:561 DEBUG pool-1-thread-1 http.headers:125 - http-outgoing-1 << Connection: keep-alive
2024-03-25 15:55:56:561 DEBUG pool-1-thread-1 http.headers:125 - http-outgoing-1 << Access-Control-Allow-Origin: *
2024-03-25 15:55:56:561 DEBUG pool-1-thread-1 http.headers:125 - http-outgoing-1 << Access-Control-Expose-Headers: content-encoding, content-length, x-tr-requestid, x-tr-correlationid
2024-03-25 15:55:56:562 DEBUG pool-1-thread-1 http.headers:125 - http-outgoing-1 << Content-Encoding: gzip
2024-03-25 15:55:56:562 DEBUG pool-1-thread-1 http.headers:125 - http-outgoing-1 << X-Amzn-Trace-Id: Root=1-6601907c-478ac7c6442705630e91229f
2024-03-25 15:55:56:562 DEBUG pool-1-thread-1 http.headers:125 - http-outgoing-1 << X-Served-By: region=eu-west-1; cid=809c49694c1c49fab06a8c3ea6b2d754
2024-03-25 15:55:56:562 DEBUG pool-1-thread-1 http.headers:125 - http-outgoing-1 << X-Tr-Requestid: 78a4dd8c-caac-4191-a2dd-2c3d9bd3489a
2024-03-25 15:55:56:563 DEBUG pool-1-thread-1 execchain.MainClientExec:285 - Connection can be kept alive indefinitely
2024-03-25 15:55:56:566 DEBUG pool-1-thread-1 conn.PoolingHttpClientConnectionManager:344 - Connection [id: 1][route: {s}->https://api.refinitiv.com:443] can be kept alive indefinitely
2024-03-25 15:55:56:566 DEBUG pool-1-thread-1 conn.DefaultManagedHttpClientConnection:88 - http-outgoing-1: set socket timeout to 0
2024-03-25 15:55:56:566 DEBUG pool-1-thread-1 conn.PoolingHttpClientConnectionManager:351 - Connection released: [id: 1][route: {s}->https://api.refinitiv.com:443][total available: 1; route allocated: 1 of 2; total allocated: 1 of 20]
2024-03-25 15:55:56:569 DEBUG pool-1-thread-1 conn.PoolingHttpClientConnectionManager:411 - Connection manager is shutting down
2024-03-25 15:55:56:569 DEBUG pool-1-thread-1 conn.DefaultManagedHttpClientConnection:79 - http-outgoing-1: Close connection
2024-03-25 15:55:56:569 DEBUG pool-1-thread-1 conn.PoolingHttpClientConnectionManager:434 - Connection manager shut down
2024-03-25 15:56:01:633  WARN pool-1-thread-1 access.OmmConsumerImpl:619 - loggerMsg
    ClientName: ChannelCallbackClient
    Severity: Warning
    Text:    Received ChannelDownReconnecting event on channel Subscription_Channel_RTO_3cc3cc8e-9b7e-4573-b5ef-28be9ac6f4ce
    RsslReactor @44776ede
    RsslChannel @78e2573a
    Error Id 0
    Internal sysError 0
    Error Location Reactor.processWorkerEvent
    Error text Error - exceeded initialization timeout (5 s)
loggerMsgEnd


2024-03-25 15:56:07:745  WARN pool-1-thread-1 access.OmmConsumerImpl:619 - loggerMsg
    ClientName: ChannelCallbackClient
    Severity: Warning
    Text:    Received ChannelDownReconnecting event on channel Subscription_Channel_RTO_3cc3cc8e-9b7e-4573-b5ef-28be9ac6f4ce
    RsslReactor @44776ede
    RsslChannel @1e52f59
    Error Id 0
    Internal sysError 0
    Error Location Reactor.processWorkerEvent
    Error text Error - exceeded initialization timeout (5 s)
loggerMsgEnd


2024-03-25 15:56:14:839  WARN pool-1-thread-1 access.OmmConsumerImpl:619 - loggerMsg
    ClientName: ChannelCallbackClient
    Severity: Warning
    Text:    Received ChannelDownReconnecting event on channel Subscription_Channel_RTO_3cc3cc8e-9b7e-4573-b5ef-28be9ac6f4ce
    RsslReactor @44776ede
    RsslChannel @729d92c1
    Error Id 0
    Internal sysError 0
    Error Location Reactor.processWorkerEvent
    Error text Error - exceeded initialization timeout (5 s)
loggerMsgEnd


2024-03-25 15:56:23:909  WARN pool-1-thread-1 access.OmmConsumerImpl:619 - loggerMsg
    ClientName: ChannelCallbackClient
    Severity: Warning
    Text:    Received ChannelDownReconnecting event on channel Subscription_Channel_RTO_3cc3cc8e-9b7e-4573-b5ef-28be9ac6f4ce
    RsslReactor @44776ede
    RsslChannel @d6303d2
    Error Id 0
    Internal sysError 0
    Error Location Reactor.processWorkerEvent
    Error text Error - exceeded initialization timeout (5 s)
loggerMsgEnd


2024-03-25 15:56:34:308  WARN pool-1-thread-1 access.OmmConsumerImpl:619 - loggerMsg
    ClientName: ChannelCallbackClient
    Severity: Warning
    Text:    Received ChannelDownReconnecting event on channel Subscription_Channel_RTO_3cc3cc8e-9b7e-4573-b5ef-28be9ac6f4ce
    RsslReactor @44776ede
    RsslChannel @67d2cec3
    Error Id 0
    Internal sysError 0
    Error Location Reactor.processWorkerEvent
    Error text Error - exceeded initialization timeout (5 s)
loggerMsgEnd


2024-03-25 15:56:41:622 ERROR pool-1-thread-1 access.OmmConsumerImpl:1717 - loggerMsg
    ClientName: Subscription_Consumer_RTO_3cc3cc8e-9b7e-4573-b5ef-28be9ac6f4ce_1
    Severity: Error
    Text:    login failed (timed out after waiting 45000 milliseconds) for 
loggerMsgEnd


2024-03-25 15:56:41:624 ERROR pool-1-thread-1 access.OmmConsumerImpl:675 - loggerMsg
    ClientName: ChannelCallbackClient
    Severity: Error
    Text:    Received ChannelDown event on channel Subscription_Channel_RTO_3cc3cc8e-9b7e-4573-b5ef-28be9ac6f4ce
    Instance Name Subscription_Consumer_RTO_3cc3cc8e-9b7e-4573-b5ef-28be9ac6f4ce_1
    RsslReactor @44776ede
    RsslChannel @4418d64f
    Error Id 0
    Internal sysError 0
    Error Location Reactor.processWorkerEvent
    Error text Error - exceeded initialization timeout (5 s)
loggerMsgEnd


2024-03-25 15:56:45:537 ERROR pool-1-thread-1 rto.RefinitivRTOSource:301 - Cannot start connector for client Id [GE-QTEKECPVOCCE], consumer [Subscription_Consumer_RTO_3cc3cc8e-9b7e-4573-b5ef-28be9ac6f4ce] , invalid usage: Exception Type='OmmInvalidUsageException', Text='login failed (timed out after waiting 45000 milliseconds) for ', Error Code='-4052'

EXPLORE OUR SITES