EMA - channel DOWN

Hello,

I am facing an issue while making snapshot with EMA. I am connected to ads that gives me the RT values I need for.
The issue is linked to the number of products I send to the ads: around 75,000. When around 30,000, my application doesn't send anything anymore to the ads and the requests are stacked on my side. When I investigate in the EMA source code, I find that when reaching around 30,000 requests, my ReactorChannel becomes in state DOWN and then all new requests are stacked in the unsent queue.
Do you have an idea why this is happening?
Is there any limit somewhere regarding the number of requests to send through a channel?

Thanks in advance.

Find more posts tagged with

elektron

reactor

elektron-sdk

refinitiv-realtime

rrt

elektron-message-api

ema-api

Accepted answers

pimchaya.wongrukun01

According to the Github raised by the client, https://github.com/thomsonreuters/Elektron-SDK/issues/41

The development team suggested that to request a large number of items, GuaranteedOutputBuffer should be increased. For example, the EMA Java performance example (emajconsperf) uses a GuaranteedOutputBuffer setting of 50000 to accommodate the large number of item requests.

All comments

pimchaya.wongrukun01

Hello @TD_BNP

Have you tried the latest EMA version shipped with Elektron SDK - Java - 1.1.1 package yet?

If the problem still occurs with the latest version, you
should contact EMA development team who can help you to fix EMA or provide the
workaround for this problem. Please contact EMA development team directly via https://github.com/thomsonreuters/Elektron-SDK/issues
then click "New issue" button to raise your problem to EMA development
team.

TD_BNP

Hello @Pimchaya.Wongrukun,

I am actually using the SDK 1.1.1. So I will raise a ticket diretly via github.

Thanks.

pimchaya.wongrukun01

According to the Github raised by the client, https://github.com/thomsonreuters/Elektron-SDK/issues/41

pimchaya.wongrukun01

Hello @TD_BNP

Sorry. I have deleted
your replies accidentally. Anyway, I have added the answer from the
Github which I think it solves your problem. If not, please add the
solution that you have made to fix the problem. This will guide other
members who face the same problem.

Thanks.

EXPLORE OUR SITES