You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
http.createServer(function (request, response) {
// attaching error handles to requrests and responses
request.on('error', function (err) {
console.error(err);
response.statusCode = 400;
response.end();
});
}).listen(process.env.PORT);
When there is an unhadled exception, the error handler is not triggered for some reason. I tried to debug this with the iisnode debugger, when the exception occurs, but the debugger says that the connection was reset (debugger console: read ECONNRESET). And it doesn't work any more.
I found a post on SO that guided me to clustering, but as I found this is also not supported by the iisnode (according to this )
I'm kind of new to nodejs apps so I am not sure if this is a bug? Or am I missing something?
BTW I am using windows 10 with IIS 10.0.something if that's relevant.
Regards,
Zoli
The text was updated successfully, but these errors were encountered:
Hi,
I created a simple web server like this
When there is an unhadled exception, the error handler is not triggered for some reason. I tried to debug this with the iisnode debugger, when the exception occurs, but the debugger says that the connection was reset (debugger console: read ECONNRESET). And it doesn't work any more.
I found a post on SO that guided me to clustering, but as I found this is also not supported by the iisnode (according to this )
I'm kind of new to nodejs apps so I am not sure if this is a bug? Or am I missing something?
BTW I am using windows 10 with IIS 10.0.something if that's relevant.
Regards,
Zoli
The text was updated successfully, but these errors were encountered: