Is it possible to change the parameter value?

@Hirou_Tanaka

Changing these values can help the disconnection issue due to buffer overflow condition in ADS.

First, you need to make sure that the data stopped because ADS cut the connection due to overflow condition. You can verify this from ADS log file.

Typically, ADS will cut the connection due to overflow condition when the client is a slow consumer. The client is a slow consumer when it is unable to handle all data sent by ADS fast enough. Then, the unsent data will be kept in the buffer. When the buffer is full, ADS will cut the connection. Therefore, you may need to verify the application logic to make sure that it runs as fast as possible.

These values can be changed. Please contact your ADS administrator to verify and change these values.

Increasing these values causes ADS requiring more memory.

*ads*guranteedOutputBuffers : 500
*ads*maxOutputBuffers: 1500
*ads*poolSize : 100000
*ads*maxMounts : 100

For example, you set an ADS to support 100 mounts (maxMounts), each with 500 guaranteedOutputBuffers using the
RSSL protocol (buffer size of 6144). You configured a pool to allow up to 100 mounts to borrow up to 1000 extra buffers each (poolSize: 100000).
Assume all 100 mounts are active and the entire pool has been borrowed. The memory requirement is:

• Per mount: 500 (guaranteedOutputBuffers) * 100 (number of mounts, here maxMounts) * 6144 bytes = 307 Mbytes
• Pool: 100000 (poolSize) * 6144 bytes = 614 Mbytes
• Total: 921 Mbytes