Failed to convert to UTF8 in RmtesBufferImpl::toString()

leonardo.pupacic

Hello,

We're receiving the above noted messages via OmmInvalidUsageException thrown when processing rmtes fields on some of the RICs in Market Price domain. The code in question is as follows:

…

auto [item, _] = m_rmtes_values.try_emplace(field.getFieldId()); // Create new RmtesBuffer or return the existing, for a given field id.

item-second.apply(field.getRmtes());

return item->second.toString().c_str();

This gets executed only if following is true:

field.getCode() != refinitiv::ema::access::Data::BlankEnum && field.getLoadType() == refinitiv::ema::access::DataType::RmtesEnum

SDK version: Release Real-Time-SDK-2.2.3.L1 · Refinitiv/Real-Time-SDK

I've attached the messages which are causing the exception. Can you please review and advise if there is an issue with the field processing as outlined, or if there is an issue within the SDK?

rmtes.exceptions.txt

Uploaded Apr 1, 202543.94 KB

Explanation of content in attached file:

The field ID which caused the exception e.g. field 3, with the content and length of the field (obtained by field.getLoad().getAsHex().c_buf() and field.getLoad().getAsHex().length()) e.g. Rmtes : 'Adeia Ord Shs' (14) :

2025-03-31 17:15:05.871 Error <140040275490560> Exception parsing field 3 : Rmtes : 'Adeia Ord Shs' (14) : Exception Type='OmmInvalidUsageException', Text='Failed to convert to UTF8 in RmtesBufferImpl::toString(). Reason: RSSL_RET_FAILURE', ErrorCode='-1'

The RIC and message domain type which contained the problematic field:

2025-03-31 17:15:05.871 Error <140040275490560> DEBUG: 8OZsg.STp (MarketPrice Domain)

The content of message (obtained by message.getAsHex().asRawHexString()):

2025-03-31 17:15:05.871 Error <140040275490560> DEBUG:
002c 0206 0000 5674 81fa 0400 0000 ce09

…

Another copy of message content (obtained by std::string(message.getAsHex().c_buf(), message.getAsHex().length())):

2025-03-31 17:15:05.871 Error <140040275490560> DEBUG:
^@,^B^F^@^@Vt<81><FA>^D^@^@^@<CE> ^@^@^B^@%^F^C^A^A3<81><C0> …

Jirapongse

@leonardo.pupacic

Thank you for the detailed information.

It looks like to be a content issue.

I subscribed those RICs via the desktop application and found invalid characters in those fields.

I will raise this issue to the content support team on your behalf to verify the values in those fields.

Jirapongse

Jirapongse

Apr 3, 2025

@leonardo.pupacic

Thank you for the detailed information.

It looks like to be a content issue.

I subscribed those RICs via the desktop application and found invalid characters in those fields.

https://us.v-cdn.net/6038239/uploads/76KEQ400QMXQ/image.png

https://us.v-cdn.net/6038239/uploads/D3WQE5XVICY3/image.png

I will raise this issue to the content support team on your behalf to verify the values in those fields.

The case number is 14612130.