You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
we have an issue with the sharingService.exe. Sometimes ports are not released correctly, this leads to HandShake failure when reusing this port.
SharingService: Created Session "userxy's Session2" with ID 3 on port 20600
SharingService: User marcelbax at address xx.xxx.xxx.xx joined session userxy's Session2
SharingService: User marcelbax left session userxy's Session2
SharingService: Session userxy's Session2 closed
SharingService: Created Session "userxy's Session" with ID 4 on port 20600
SharingService: User marcelbax at address xx.xxx.xxx.xx joined session userxy's Session
SharingService: User marcelbax left session userxy's Session
SharingService: Created Session "7535TY" with ID 5 on port 20600
Error: SharingService [..\..\Source\Common\Private\XSocketManagerImpl.cpp (673)]: Failed to create incoming connection on port 20600. Error code: 5
SharingService: Session 7535TY closed
As you can see in the log there is opened a session, closed and an other is opened again.
When closing the second time the session is not correctly closed, SharingService: Session userxy's Session2 closed is not displayed the second time.
After that no connection via 20600 is possible.
Imho it would be better to wait for closing the server before pushing the port back to the pool, so "ill" ports will not be used.
The text was updated successfully, but these errors were encountered:
Hi,
we have an issue with the sharingService.exe. Sometimes ports are not released correctly, this leads to HandShake failure when reusing this port.
As you can see in the log there is opened a session, closed and an other is opened again.
When closing the second time the session is not correctly closed,
SharingService: Session userxy's Session2 closed
is not displayed the second time.After that no connection via 20600 is possible.
Imho it would be better to wait for closing the server before pushing the port back to the pool, so "ill" ports will not be used.
The text was updated successfully, but these errors were encountered: