State of EMA Java ?

We are considering moving from RFA to EMA but fail to locate any throttling in EMA, which is important to us.

Any plans to add this?

Is EMA SDK 1.0.x as stable as RFAJ 8.0.x ?

It's just that getting a NPE in Reactor.sendChannelEventCallback() :

...

int retval = reactorChannel.role().channelEventCallback().reactorChannelEventCallback(reactorChannelEvent);

...

is a bit disturbing.

Find more posts tagged with

elektron

elektron-sdk

refinitiv-realtime

rrt

elektron-message-api

ema-api

Accepted answers

greg.lee

With regards to the throttling question, EMA utilizes the open window of the service. EMA has a configuration option name ObeyOpenWindow. When this is set to to true, EMA will utilize the open window size specfied for that service (from the source directory response message). When this is set to false, EMA does not utilize any open window and no throttling occurs.

All comments

pimchaya.wongrukun01

Hello @John.Westi

What are the reproduce steps/source code for the NPE problem?

Do you face the NPE in the latest Elektron
SDK Java(version 1.0.7)? If not, please try to test with it.

greg.lee

The issue you mention is already captured. We are working on a fix and will provide in a future release. The associated JIRA is EMA-791.

pimchaya.wongrukun01

Hello @John.Westi,

What is the purpose of moving from RFA to EMA? Are you using MarketData interfaces(SSL connection) in RFA?

greg.lee

John.Westi

Sounds like it's a known issue (EMA-791) according to Greg Lee.

I'll check if master contains a fix for this.

John.Westi

Hi Pimchaya

We are upgrading an old RFAJ 7.4 app to enhance functionality and to utilise RSSL and OMM.

My understanding is that EMA is the future RFA so we might as well go all the way and using EMA. At least that was our plan until I failed to locate throttling logic and was hit by NPE errors.

Overall I like the idea of turning proprietary code into open source and I'm looking forward to see features like throttling being added.

EXPLORE OUR SITES