KB Article #178195
Why messages type = REPLY are not reusing existing sessions
Problem
Why messages type = REPLY are not reusing existing network sessions.
All reply (ACK) are done using a new established network session and it affects the sessions counter
Resolution
It is not possible to reuse an existing transfer session for the ACK or reusing a ACK session for a new transfer.
It has been designed like that to ensure a larger compatibility with 3rd party PeSIT monitors.
That being said, it cost in performances and sessions usage (it also
affect the overall bandwidth opening new sessions for the reply messages)
Triggering a batch treatment for a transferred file should be done on the transfer EOT procedure itself and not on the ACK triggered procedure.
The ACK message purpose is for 'delayed / not transfer time linked' application ACK and should not be used to simply say the file has been received ok that is redundant with the transfer EOT procedure already.
Current implementation does not allow to reuse an existing session in the reverse way.