WinHttpException: The connection with the server was terminated abnormally #128
Comments
|
Thanks for reporting this. I haven't personally been able to repro it, so if you are able to provide any repro steps (even if the repro is still intermittent) that would be great. My best guess is that it looks like this issue: https://github.com/dotnet/corefx/issues/4934 The good news is that this problem should no longer matter once we change NodeService's default transport from To try this out now:
Does this issue go away if you do that? If the error still occurs, please post the updated stack trace, as it will certainly at least be different with this change. |
|
It works when I run |
|
Repro for first issue: https://drive.google.com/file/d/0B0xPA49vdefIMk9hUk1FZHFJRjg/view?usp=sharing (it's basically the default Angular 2 app plus karma) To repro the second one just add |
|
I just got the same |
|
Thanks for posting the repro project. I tried it, and I'm afraid it didn't repro in my environment. I ran it both via As for the intermittent failures (both the
Please try this: You can disable NodeService's file watching by amending the code you added to Now Of course, now, after you've made a change, it won't show up in the server-side rendering results until you restart the app entirely. So this is not really what you want, but at least it helps to diagnose what causes the failures. If this change does fix it, then the good news is that the intermittent failures will not happen in production. They are just an artifact of how you have set up your dev machine. So you can either disable whatever is running in the background (VS add in, test runner, or whatever), or you can keep it running and just reload the page whenever it triggers a request failure.
That's completely different - that's is an error message coming back from Angular. Please review anything you've put in your Angular startup file (e.g., |
Update: I figured out how to reproduce this error. It is a problem in the templates. I'll find a fix. |
|
The The original issue, however, remains open. I'm waiting for feedback on whether disabling the file watcher resolves the intermittent failures. @ManuelDeLeon, please let me know when you have a chance to try it. |
|
Adding Upgrading to 0.1.9 seems to get rid of
I need to test for that. |
|
I'm still trying to figure this one out. I set up a file watcher, started the server and got the pipe broken error plus: I restarted the server and got the same pipe broken message and the following: The file watcher reported a whole bunch of files changed in the node_modules folder: I'll probably have to setup some kind of security auditing to see which process is modifying the files. |
You could try https://technet.microsoft.com/en-us/sysinternals/processmonitor |
|
It took me a while to get a good log since it doesn't happen always. I created a new Angular 2 project and added Here's the Process Monitor log file: Only |
|
Curious.. I haven't been able to run the React-Redux template in Socket mode either (on my Win7 PC). I always get either "Pipe is broken." or "Bad Gateway" http response. |
|
Same issue here. Installed |
|
|
System details: I've been able to reproduce the error for my case.
So it seems that 404 causes the problem. The following is the error I get when updating the app while running. |
|
Thanks for your repro steps. Do you definitely get the As far as I can tell, you'd only get the As for the requests hanging if Webpack compilation fails, this is now fixed. Please update your copy of More generally: Most people on this thread are probably aware, but the |
|
What about |
|
That's the Right now, I'm aware of the following:
|
|
@ManuelDeLeon Also, thanks for posting that process monitor log. Unfortunately it doesn't pinpoint a cause, because your console output says that the modified file was The spreadsheet you gave shows only two incidents of that file being accessed, and both times it was just being read (not written) by Also, your spreadsheet shows that the last write time for Maybe it's possible that nothing is actually writing to that file, and maybe Node's |
|
@SteveSandersonMS Thanks for the response. Yes, by purely following these steps I can get that error. So if I try to re-run the application (Run with Debugging or without from VS 2015) will get the Haven't tried any other options/repro steps yet, nor searched more on the issue, will probably look in the upcoming days and come up if something needs to be reported (will give a try to update the |
That's strange - I don't know why that would happen, and I can't repro it. Invoking "Run [with debugging]" from VS doesn't cause such an issue on my machine. Is it possible you have some VS extension installed that writes files when you invoke "run"? Maybe something that tries to compile TypeScript or run Webpack? What happens once you've updated to the latest |
|
So I just had this issue and noticed it happened when I change main: './App/main.ts' to app: './App/main.ts' in webpack.config.js in the angular 2 template project, this dosn't line up with what you guys are describing but it might be a possible reason for it happening |
|
Based on all the comments here, I've completely rewritten how the Node instance lifetimes are managed, how processes are restarted, and how file changes are watched for:
Hopefully, the combination of these two enhancements will avoid the Node processes getting killed prematurely (if an RPC call is still in flight) or unexpectedly (if To get the update: Upgrade to Note that a lot of low-level stuff has changed, so consider beta-000007 to be very much a "preview", so if you hit trouble please downgrade to About this thread: This is a long thread, and basically all of it is now obsolete, because so much has now changed. If you're just arriving here, please disregard all the comments above as they probably don't apply in your situation. To minimise confusion, I'll close this issue now. For any further connection troubles now, please post a new issue describing the problem and how to reproduce it. Any similarity with events or error messages described above is purely coincidental :) |
|
@antmdvs Hope you don't mind that I removed your comment. Trying to keep the last item in this thread the one I posted above, to avoid confusion. As per above, please file a new issue if there's still a problem after you update. |
This happens on an Angular app in both Win8.1 and Win10. The problem is intermittent and we haven't figured out how to reproduce it but it happens quite often. Here's the error page:
The text was updated successfully, but these errors were encountered: