Regarding unintentional disconnection of EMA threads

kei.oodate
kei.oodate Newcomer
edited January 20 in EMA

We detected disconnections in several EMA threads in our system.

Thread #1
Jan 20 0:06, 09:15 (JST)

Thread #2
Jan 20 01:25 (JST)

——————-
EMA 3.7.x series

  • Problem: connection timeouts occur in certain server configurations.
    • Detail: connection timeouts occur frequently in environments with high network latency when clients connect to the Elektron Data Platform.
    • Workaround: temporary workaround by extending the timeout settings.
    • FIX: optimised timeout handling in 3.8.x.

EMA 3.8.0

  • Problem: resource contention in multi-threaded environments.
    • Details: under certain conditions, multiple threads could use the same message buffer, resulting in memory corruption.
    • FIX: improved resource management in 3.8.1.

——————-

I have found that some bugs have been reported in some versions, is today's our timeout error due to a bug?

The EMA version we are using are as follows;

Real-Time-SDK-2.1.0.L1.linux
ema3.7.0.L1.linux
eta3.7.0.L1.linux


Regards,

Tagged:

Answers

  • Jirapongse
    Jirapongse ✭✭✭✭✭

    @kei.oodate

    Thank you for reaching out to us.

    With this limited information, we can't confirm that the cause of the disconnections. We need the API and server log to verify what the problem is.

    However, normally Developer Community Forum is for how-to/general questions but your question seems to be more complex and requires investigation e.g. review source code, configuration, try to reproduce the problem etc. I recommend you raise a query through the premium support service, as you are a named user of that service you should see a link "Contact Premium Support" when you are logged into the developer portal.

Categories