-
-
Notifications
You must be signed in to change notification settings - Fork 26
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
Returned by server pipeName is null #20
Comments
I able to mitigate the problem by adding a random delay before ConnectAsync:
|
Thanks for the problem and detailed description. Yes, indeed, the main pipe of the server accepts requests one at a time, and there may be problems with simultaneous requests from several clients. Comments for correction (to me in the future or anyone who wants to do this):
I'll get into this after checking out this PR - #19 because it changes the code a lot. |
Describe the bug
We are sporadically seeing the following exception when connecting > 1 pipeclient with pipeClient.ConnectAsync()
System.InvalidOperationException: Connection failed: Returned by server pipeName is null at H.Pipes.PipeClient
1.GetConnectionPipeName(CancellationToken cancellationToken)at H.Pipes.PipeClient
1.GetConnectionPipeName(CancellationToken cancellationToken) at H.Pipes.PipeClient
1.ConnectAsync(CancellationToken cancellationToken)`Clients are connected in a relatively short time, the problem is already visible with 3 clients, but does not happen all the time.
Steps to reproduce the bug
Create pipe server
Create multiple pipe clients
Expected behavior
All pipe clients connect normally and without ab exception
Screenshots
No response
NuGet package version
Platform
Console
IDE
Other
Additional context
No response
The text was updated successfully, but these errors were encountered: