question

Upvotes
Accepted
Paul.Wuethrich2 avatar image
20 ●7 ●8 ●11

ETA/Reactor RCC Java buffering/ack configuration/logic

We have a Java-based ETA/Reactor client application contributing/posting to RCC in development and are running into failed buffer allocation errors. Our understanding is that these buffers are not being released until we receive an ACK from RCC and ideally we'd like to disable this functionality (i.e. anything associated with guaranteed delivery) as our intent is to not use any queueing (we currently do not have queuing configured) as the throughput requirements will be on the high side. Questions are as follows:

1. We've tested with both 3.3.0 and 3.6.x library versions and we would prefer to stay on the older 3.3.0 version for now but can update to 3.6.x if absolutely required. We have noticed that within 3.6.x we can query the current available buffers whereas we cannot in 3.3.0. So are there material changes between the versions that are required or should consider?

2. We're not understanding how to disable the feature that ties the release of buffers to the receipt of ACKs from RCC


elektronrefinitiv-realtimeelektron-sdkrrteta-api
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.

wasin.w avatar image   wasin.w

Hello @Paul.Wuethrich2

Thank you for your participation in the forum. Is the reply below satisfactory in resolving your query?


If so please can you click the 'Accept' text next to the appropriate reply? This will guide all community members who have a similar question.

Thanks,


AHS

zoya faberov avatar image   zoya faberov

Hello @Paul.Wuethrich2 ,

Please be informed that a reply has been verified as correct in answering the question, and has been marked as such.

Thanks,

-AHS

3 Answers

· Write an Answer
Upvotes
Accepted
Jirapongse avatar image
78.8k ●250 ●52 ●74

@Paul.Wuethrich2

You may try to increase the number of guaranteed output buffers of the TunnelStream, as mentioned in this thread.

In ETA VA, it is in the TunnelStreamOpenOptions.

1626747826438.png


_tunnelStreamOpenOptions.guaranteedOutputBuffers(5000);



1626747826438.png (17.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.

Upvotes
Paul.Wuethrich2 avatar image
20 ●7 ●8 ●11

Thanks - but what about the inherent feature that ties releasing the buffer to receiving an ACK. Is there a way to disable this we see this as a serious problem?

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.

Upvotes
Jirapongse avatar image
78.8k ●250 ●52 ●74

@Paul.Wuethrich2

I may relate to the settings of the Tunnel stream.

1627381740025.png

However, because it is an internal implementation in the ETA Reactor, please directly contact the RDC support team via Contact Premium support to confirm the behavior.

1627381912691.png



1627381740025.png (112.3 KiB)
1627381912691.png (61.2 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.

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.