Hello @red

By default, the EMA API sends all requests registered by the application to the server directly. Your workaround is creating the application layer logic to throttle requests before sending them to EMA which is the suggested way when requesting a lot of items.

Do you mean the problem does not occur if you subscribe to all fields request, but if you use View, the problem occurs?

If so, I recommend you contact the API support team via the "Contact premium support" button on the https://developers.refinitiv.com/en/api-catalog/refinitiv-real-time-opnsrc/rt-sdk-java page.

Alternatively, you may submit this issue to the RTSDK Development team directly via RTSDK - GitHub Issues page.

Hope this helps.

Hello @red

What EMA Java (or RTSDK) version that you are using? Could you please share the snippet code that constructs the View, Batch, and the request message?

Please also enable the XML trace messages. The XML trace contains incoming and outgoing messages between the API and the server, so the messages can help us to verify if the API receives data from the server. You can enable the XML trace messages by setting the XmlTraceToStdOut parameter in the EmaConfig.xml to "1".

You can find more detail on the "EMA Java Logging" section of the Enterprise Message API (EMA) - Configuration Overview article.

hi @wasin.w, thanks for your reply.

I am using the following:

implementation("com.refinitiv.ema:ema:3.6.4.0")

Minimal example code block where I construct a request:

class MarketDataConsumerClient : OmmConsumerClient {
   // NOTE THAT THE CONSUMER NEEDS TO BE CONSTRUCTED BEFORE THIS CODE WORKS
    private var consumer: OmmConsumer? = null
    private val service = "ERT_FD3_LF1"

    private val fieldIds = mapOf(
        "BID" to 22L,
        "ASK" to 25L,
        "BIDSIZE" to 30L,
        "ASKSIZE" to 31L,
        "QUOTIM" to 1025L,
        "QUOTE_DATE" to 3386L
    )


    private fun requestBatchRics(rics: List<String>) {
        val ricArray = EmaFactory.createOmmArray().apply {
            rics.forEach { add(EmaFactory.createOmmArrayEntry().ascii(it)) }
        }
        // The view array allows us to customize what data we are interested in (reduces amount of data received)
        val viewDataArray = EmaFactory.createOmmArray().apply {
            fieldIds.values.forEach { fieldValue -> add(EmaFactory.createOmmArrayEntry().intValue(fieldValue)) }
        }

        val batchList = EmaFactory.createElementList().apply {
            add(EmaFactory.createElementEntry().array(EmaRdm.ENAME_BATCH_ITEM_LIST, ricArray))
            add(EmaFactory.createElementEntry().uintValue(EmaRdm.ENAME_VIEW_TYPE, 1))
            add(EmaFactory.createElementEntry().array(EmaRdm.ENAME_VIEW_DATA, viewDataArray))
        }

        val requestMessage = EmaFactory
            .createReqMsg()
            .serviceName(service)
            .payload(batchList)
        consumer!!.registerClient(requestMessage, this)
    }
}

A trace for a request for a RIC that doesn't sub/send any message:

<!-- rwfMajorVer="14" rwfMinorVer="1" -->
<REQUEST domainType="MARKET_PRICE" streamId="1226" containerType="ELEMENT_LIST" flags="0x446 (HAS_PRIORITY|STREAMING|HAS_QOS|HAS_VIEW)" Qos: Realtime/ConflatedByRateInfo/Static - timeInfo: 0 - rateInfo: 3000 priorityClass="1" priorityCount="1" dataSize="46">
    <key flags="0x03 (HAS_SERVICE_ID|HAS_NAME)" serviceId="253" name="KFM.AX"/>
    <dataBody>
        <elementList flags="0x08 (HAS_STANDARD_DATA)">
            <elementEntry name=":ViewType" dataType="UINT" data="1"/>
            <elementEntry name=":ViewData" dataType="ARRAY">
                <array itemLength="2" primitiveType="INT">
                    <arrayEntry data="22"/>
                    <arrayEntry data="25"/>
                    <arrayEntry data="30"/>
                    <arrayEntry data="31"/>
                    <arrayEntry data="1025"/>
                    <arrayEntry data="3386"/>
                </array>
            </elementEntry>
        </elementList>
    </dataBody>
</REQUEST>

EDIT: the above was just processed - let me make sure I capture output of one that definitely doesn't work.

EDIT 2: This is now working? I have no explanation other than the additional logging is slowing down the requests due to file IO. Your explanation is much appreciated.

Is there a limit on outstanding requests that Refinitiv can process on your end before it throws additional requests away? I added a Thread.sleep(1) between individual RIC requests and everything's working. This is definitely hacky and I do not want to do this.

EDIT 3: The following code block works. Please note the Thread.sleep(1). This is not a viable solution for me, so your help is appreciated. Something is dropping requests/responses.

private fun requestRicsIndividually(rics: List<String>) {
        val viewDataArray = EmaFactory.createOmmArray().apply {
            fieldIds.values.forEach { fieldValue -> add(EmaFactory.createOmmArrayEntry().intValue(fieldValue)) }
        }
        val batchList = EmaFactory.createElementList().apply {
            add(EmaFactory.createElementEntry().uintValue(EmaRdm.ENAME_VIEW_TYPE, 1))
            add(EmaFactory.createElementEntry().array(EmaRdm.ENAME_VIEW_DATA, viewDataArray))
        }
        rics.forEach {
            Thread.sleep(1)
            logger.debug("Requesting ric[$it]")

            val requestMessage = EmaFactory
                .createReqMsg()
                .serviceName(service)
                .payload(batchList)
                .name(it)
            consumer!!.registerClient(requestMessage, this)
        }
    }

Thank you!

@wasin.w My most viable solution thus far is to dynamically create a new OmmConsumer every 500 RICs on the same channel. This seems to work well. Let me know what you think.

Still - I am curious as to why a view affects RIC subscriptions, as it works flawlessly without a view. With a view, it is returning a consistent subset of the RICs requested (unless delaying subscriptions or spreading them out between multiple OmmConsumers).

Red.