A simple idea, but it might help:
Try to add logging middleware to your requests, which would also append
something you can recognize. Something
like https://github.com/villadora/express-bunyan-logger.
Then you might be able to compare which requests came in but are not
finishing, and so
Are you using webpack and sass-loader? On the request that hangs, are there
two or more places that import SCSS files? There are several issues posted
like this (server hangs, no error/warning):
https://github.com/jtangelder/sass-loader/issues/99
--
Job board: http://jobs.nodejs.org/
New
Thanks Isen. This worked perfectly.
On Friday, 24 July 2015 23:23:47 UTC+5:30, Isen Ng wrote:
On the Parse JS changelog:
https://parse.com/docs/downloads
Removed the concept of the concept of the current user when running in
node.js Current users can be enabled in node with
Hello Rob. I'm not using webpack nor sass.
Zladuric, I'm logging the connections and I found one service that usually
is involved with the problem, however when I restart the application, I
create a request with the same logged data, but the problem does not
reproduce. Strange, right? Not be
