Skip to content

Conversation

SwarajKetan
Copy link

Due to improper scope AuthenticationConnection semaphore lock is acquired more than once when connect() method is called more than once while a connect operation is still in progress. It exhausts the semaphore slot and keeps the other Connect operations waiting until one finishes. Change of scoping will help us acquireclock just before the connect operation begins.

@SwarajKetan SwarajKetan changed the base branch from develop to master August 15, 2021 06:09
@SwarajKetan SwarajKetan changed the title Renci optimize session Renci optimize session issue #861 Aug 15, 2021
@A9G-Data-Droid
Copy link

I have tested this and it works!

@Rob-Hague
Copy link
Collaborator

Thanks! Closing as the AuthenticationConnection semaphore has been removed in #1304

@Rob-Hague Rob-Hague closed this Feb 6, 2024
@WojciechNagorski
Copy link
Collaborator

This issue has been fixed in the 2024.0.0 version.

@WojciechNagorski WojciechNagorski added this to the 2024.0.0 milestone Feb 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants