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
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.
I may relate to the settings of the Tunnel stream.
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.