Hello,

our client implementation seems to create so many sessions that the server (implemented on an actual machine) reaches its maximum setting and becomes slower. Is there a good way to track the client session creation from the client code since the server is not our product and cannot be changed?

Edit: Since there seem to be only one session available per client: can it be that the session of the previous run was not closed properly? Do we need to do manual steps to clean up the session on the server before disconnecting the client?
In which cases a new session will be created by the client? Will it notify the server to remove the old one? The session timeout which lets the server remove past inactive sessions is proposed to be an hour by the documentation, which could be too long if several restarts happen fast.

Thanks in advance!

Jun