question

Upvotes
1 0 3 4

RFA 8.2.1 issues recovering after RTC disconnect (due to container recycle)

We are having issues with an internal built applications requesting market data. The threads are getting snarled up when using RFA Jave 8.2.1 after RTC has a sudden disconnect or the rtc cloud container gets recycled. What it appears to be doing is that the threads are hanging onto the old connection so at this point instead of recovering or moving to a new rtc instance it trys to continue making requests over the dead/timeout connection that no longer exists and the thread continues to fill until it eventually runs out of memory. Is there something we can do to fix this?


1728665934548.png

#technologyrfa-api
1728665934548.png (20.7 KiB)
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

1 Answer

· Write an Answer
Upvotes
86.8k 294 53 79

@MM

Thank you for reaching out to us.

Under the hood, API uses a ping mechanism to detect the connection and server status. It should be able to detect this issue and then recover the connection.

However, I found you have submitted this issue to the API support team and the support team is working on this issue.


icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.