ETA/Reactor RCC Java buffering/ack configuration/logic

Paul.Wuethrich2
Paul.Wuethrich2 Explorer
in ETA

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


Tagged:

Best Answer

  • Jirapongse
    Jirapongse ✭✭✭✭✭
    Answer ✓

    @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);


Answers

  • Paul.Wuethrich2
    Paul.Wuethrich2 Explorer

    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?

  • Jirapongse
    Jirapongse ✭✭✭✭✭

    @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


Categories