OmmProvider.submit seems dead locked on > 2000 RICs

Jianping
Jianping Newcomer
edited 2:58AM in EMA

The server in question registers 2000 RICs, and updates all of them at interval of 0.5s. The 2000 RefreshMsg on registration and 4000 UpdateMsg/s are queued, and OmmProvider.submit-ed in a single thread. It all works fine.

However, when the RIC size is raised to 5000, it gets hanged. The thread dump looks like this:

image.png

Any help would be greatly appreciated.

Jianping

Tagged:

Answers

  • Gurpreet
    Gurpreet admin

    Hello @Jianping

    I would recommend that you enable the OMM Logging for the EMA SDK and upload the log file when this deadlock happens. There might be a status message that your app might have missed. If this is connecting to your local RTMDS, then check the ADS logs for server side message as well.

    You can also try to pace out the subscriptions in a batch size of 1000 each. The batch size is physically limited by the array size in the SDK as described in this previous discussion -

    https://community.developers.refinitiv.com/discussion/15222/batch-size-limit-on-eta-api
  • Jirapongse
    Jirapongse ✭✭✭✭✭

    @Jianping

    Deadlock situations typically involve two threads.

    Could you please provide the full thread dump for analysis?

Categories