Over time the number of sessions increases slowly, until the maximum memory that can be allocated to the storing of sessions is hit and the application fails. This leads to a discrepancy between the netstat output command and the sessions listed in the logs in debug mode.
I.e. the debug mode show that there are sessions still alive, sessions that the cleaner will not remove:
However, netstat shows no TCP session.
1) This issue could not be reproduced by Support nor Consulting.
2) We thought the best would be to have better debugging to progress, this was logged at
However, if you think it is not the right way to investigate, then please detail what you need.
3) We know that consultants working on that customer network during a visit on-site experienced a lot of networking issues like name conflicts. We tried to reproduce bad networking conditions in a test environment but were still not able to reproduce this session leaking issue.