This repository was archived by the owner on Apr 8, 2020. It is now read-only.
Repository navigation
This repository was archived by the owner on Apr 8, 2020. It is now read-only.
Socket hosting model not working #110
Description
I faced issue with newly created Socket hosting model. It not respond for any requests. I not really sure what exact goes wrong. It could be enviroment issue or so.
My machine is win10 x64 with latest updates.
Steps to reproduce
- Open ReactGrid sample
- Specify Socket hosting model by adding
services.AddNodeServices(new NodeServicesOptions { HostingModel = NodeHostingModel.Socket });to yourConfigureServicesmethod. - Run
dotnet runcommand - Try to open localhost:5000
Expected behaivior
Page rendered
Actual behaivior
Page stuck in infinite load
_Note_:
If run under old fashion Http hosting model everything work perfect.
_UPD_:
after long long wait for response i recieve following error:
System.IO.IOException: Pipe is broken.
at System.IO.Pipes.PipeStream.CheckWriteOperations()
at System.IO.Pipes.PipeStream.WriteAsync(Byte[] buffer, Int32 offset, Int32 count, CancellationToken cancellationToken)
at Microsoft.AspNetCore.NodeServices.HostingModels.VirtualConnections.VirtualConnectionClient.<WriteAsync>d__19.MoveNext() in C:\dev\Source\Repos\NodeServices\src\Microsoft.AspNetCore.NodeServices\HostingModels\VirtualConnections\VirtualConnectionClient.cs:line 188
Activity
SteveSandersonMS commentedon Jun 7, 2016
Thanks for pointing this out.
In my final commit I'd missed out the
PipeOptions.Asynchronousoption that's needed on Windows for the named sockets transport not to just hang. Fixed now.ManuelDeLeon commentedon Jun 18, 2016
Is the fix for this one out? I keep getting
One or more errors occurred. (Pipe is broken.)intermittently (no error log or stack trace)SteveSandersonMS commentedon Jun 21, 2016
Yes, the original issue reported by @laskoviymishka - that it never works - is fixed and was released as
beta-000004.If you have a scenario where it fails intermittently, that must be something different.
Based on your description, I'm pretty sure your intermittent issue is the same as #128, hence not reopening this issue. Let's keep any discussion about the intermittent thing in #128.