Hello @emir.subasic

Could you please let us know the following information?

• The version of RFA .Net API that you are using.
• The RFA configurations.
• Did you find any memory growth issues when the problem occur?

This issue may be a slow consumer problem ( i.e. the application cannot keep up with the update rate and the messages are filing up in the RFA event queue). You can find more detail regarding a slow consumer problem via the following old posts:

• RFA EventQueue - Log Queue depth - How to log the current queue depth periodically
• Latency problem of Update Message

Hi,

No noticeable memory growth issues.

RFA v8.1

RFA Config

\Connections\Connection_RSSL\connectionType = "RSSL"

\Connections\Connection_RSSL\rsslPort = "14002"

\Connections\Connection_RSSL\hostName = "127.0.0.1"

\Logger\AppLogger\fileLoggerEnabled = true

\Logger\AppLogger\windowsLoggerEnabled = false

\Logger\ComponentLoggers\Connections\messageFile = "RFA8_Connections"

\Logger\ComponentLoggers\RSSL_Adapter\messageFile = "RFA8_RSSL_Adapter"

\Logger\ComponentLoggers\RSSL_Cons_Adapter\messageFile = "RFA8_RSSL_Cons_Adapter"

\Logger\ComponentLoggers\RSSL_Prov_Adapter\messageFile = "RFA8_RSSL_Prov_Adapter"

\Logger\ComponentLoggers\SessionCore\messageFile = "RFA8_SessionLayer"

\Logger\ComponentLoggers\Static\messageFile = "RFA8_MsgFile"

\Sessions\Session1\connectionList = "Connection_RSSL"

I will look at creating a secondary queue to deal with all responses and to remove all processing logic from the ProcessEvent method.

Thanks

Emir

Hi,

This indeed looked like a slow consumer issue.

Our new implementation is handling this much better now.

As a suggestion, it might be worthwhile to create an explicit code example that is high performant in the examples section so to avoid these kind of questions in the future.

Thanks