Error in NodeServices using node-inspector #506

Activity

1. SteveSandersonMS

   closed this as completedin d7d1a04on Jan 20, 2017
2. SteveSandersonMS commented on Jan 20, 2017

   

   SteveSandersonMS

   on Jan 20, 2017

   Member

   More actions

   I was getting a slightly different error message, but I think the same underlying problem, when I tried to repro this. If you have Webpack dev middleware enabled, then it caused problems with debug mode, because when the app first starts up, it often writes an updated main-server.js bundle to disk, which causes the Node process to restart. Then, because connection draining is enabled by default, the new Node instance fails to start, because the old one is still temporarily alive and is holding the debugging port open.

   You could verify that this is the underlying issue simply by commenting out your EnableWebpackDevMiddleware calls in Startup.js. If that makes the problem with the debugger go away, it's the same issue.

   I've now implemented a fix that will be included in the 1.1.0-rc2-final release. Whenever a debug listener is enabled, we bypass connection draining. There's no real disadvantage to doing this, because if you're actively debugging your app, you probably don't mind that requests in other browser tabs could get terminated abruptly when you change source files. It obviously doesn't affect any production scenario, since you would never launch Node with a debugging listener in production.