question

Upvotes
Accepted
40 2 1 6

Elektron API TRCC Certificate validation error

I have a C++ program that posts RIC data to the TRCC using the Elektron SDK. v3.10.3. We've been running an automated posting service 24/7 for over a year. Saturday morning all posts began failing due to what appears to be a certificate error. I made no changes to the code at this time and my IT department says no facility changes were made.

The error occurs during the call to the OmmConsumer constructor. Here is the exception info:

Exception Type='OmmInvalidUsageException', Text='login failed (timed out after waiting 45000 milliseconds) for contrib1-amers1.platform.refinitiv.com:443)'

The program captures the SDK logging messages. Below is an example message. This text repeats several times until the attempt times out after 45 seconds.

Any ideas?

Naomi at the help desk is researching server issues but she said I should post to the API forum. Even if this turns out to be a facility issue on one end or the other, are there any workarounds?

Thanks, Jeff


loggerMsg

TimeStamp: 13:51:04.161

ClientName: ChannelCallbackClient

Severity: Warning

Text: Received ChannelDownReconnecting event on channel Channel_2

Instance Name Consumer_1_1

RsslReactor 0x0000000001E06020

RsslChannel 0x0000000001E06020

Error Id -1

Internal sysError 0

Error Location C:\Jenkins\workspace\ESDKCore_RCDEV\OS\VS140-64\rcdev\source\esdk\Cpp-C\Eta\Impl\Reactor\rsslReactorWorker.c:1132

Error Text <C:\Jenkins\workspace\ESDKCore_RCDEV\OS\VS140-64\rcdev\source\esdk\Cpp-C\Eta\Impl\Transport\ripcsslutils.c:1788> Certificate validation err

: Hostname mismatchOpenSSL Error string: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:ssl\statem\statem_clnt.c:1925:

loggerMsgEnd


elektronrefinitiv-realtimeelektron-sdkema-apirrtelektron-message-api
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.

Hi @jeff.birkel

Can you please confirm the exact version of the ElektronSDK version and EMA version you are using - I don't recognise v3.10.3

Are the post still failing or did this occur on Saturday only?


Upvote
Accepted
40 2 1 6

@umer.nalla

I just checked my email and there was a message from Refinitiv notifying me that there was a server-side certificate error. Mystery solved.

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
40 2 1 6

@umer.nalla

Apologies. It's version 1.3.1.0

The error persisted for at least 48 hours, from early Saturday morning until at least end of day yesterday (Monday.) As of this morning it is working again. I made no changes and I have no explanation for the change.

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
25.3k 87 12 25

Hi @jeff.birkel

If it was a time-limited scenario then it is most likely an issue with the RCC system or the related Authentication system. I will ask the RCC dev team if they are aware of any such issues over the weekend.

EMA has various recovery mechanisms in place - including the ability to use a ChannelSet and provide more than one Channel to try and connect to. If you have been provided with more than one contrib server address, I would recommend you create a ChannelSet if you are not already doing so.

Some articles you may find useful - (not RCC specific)

Enterprise Message API (EMA) - Configuration Overview | Refinitiv Developers

The Mechanics of EMA Connection and Item Recovery | Refinitiv Developers


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.

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.