Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Socket connection fix: destroy() used instead of abort() #674

Merged
merged 1 commit into from
May 12, 2023

Conversation

rajat-dlt
Copy link
Contributor

While testing the fabric-node-SDK, found that the connections were not getting reused creating more connections in the pool.

While debugging the issue further found that the issue is the connection was not getting destroyed. The request.abort() method was deprecated for a really long time too, so it makes sense this could be changed.

Thus, this minor code change fixes this issue and we're able to decrease the number of active GRPC connections on the network.

Signed-off-by: Rajat Sharma <Rajat16.Sharma@ril.com>
Signed-off-by: Akshat Khandelwal <akshat.khandelwal@ril.com>
@rajat-dlt rajat-dlt requested a review from a team as a code owner May 11, 2023 10:55
@rajat-dlt
Copy link
Contributor Author

@bestbeforetoday,

This is the fix I was mentioning. This has really helped our team in case of high load on the CA.

Issue: #672

Copy link
Member

@bestbeforetoday bestbeforetoday left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. Thank you for the contribution.

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.

2 participants