{"action":"created","issue":{"url":"https://api.github.com/repos/nodejs/node/issues/3508","labels_url":"https://api.github.com/repos/nodejs/node/issues/3508/labels{/name}","comments_url":"https://api.github.com/repos/nodejs/node/issues/3508/comments","events_url":"https://api.github.com/repos/nodejs/node/issues/3508/events","html_url":"https://github.com/nodejs/node/issues/3508","id":113156503,"number":3508,"title":"Problematic socket.parser.resume() error","user":{"login":"binarybehemoth","id":15277380,"avatar_url":"https://avatars.githubusercontent.com/u/15277380?v=3","gravatar_id":"","url":"https://api.github.com/users/binarybehemoth","html_url":"https://github.com/binarybehemoth","followers_url":"https://api.github.com/users/binarybehemoth/followers","following_url":"https://api.github.com/users/binarybehemoth/following{/other_user}","gists_url":"https://api.github.com/users/binarybehemoth/gists{/gist_id}","starred_url":"https://api.github.com/users/binarybehemoth/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/binarybehemoth/subscriptions","organizations_url":"https://api.github.com/users/binarybehemoth/orgs","repos_url":"https://api.github.com/users/binarybehemoth/repos","events_url":"https://api.github.com/users/binarybehemoth/events{/privacy}","received_events_url":"https://api.github.com/users/binarybehemoth/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/nodejs/node/labels/http","name":"http","color":"c7def8"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":9,"created_at":"2015-10-24T12:10:32Z","updated_at":"2015-11-02T04:29:24Z","closed_at":null,"body":"This bug has been crashing my node.js server for the past one week. On average it seems to occur every 12 hours. Normally when an error occurs in node.js, node.js will tell you the line number and your source file that lead to the error. However, this error is so weird that it does not let me know where the error originates from in my source codes. I can't even find _http_server.js within the entire project and node modules. As such, I have been unable to pinpoint and eliminate the bug.\r\n\r\nWithout the stack trace module 'longjohn', I would get the following error message:\r\nsocket.parser.resume()\r\ncannot read property resume of null (_http_server.js:442)\r\n......\r\n\r\n\r\nAfter I installed 'longjohn', I obtained the following error message:\r\n\r\nTypeError: Cannot read property 'resume' of null\r\n    at socketOnDrain (_http_server.js:442:20)\r\n    at ServerResponse.updateOutgoingData [as _onPendingData] (_http_server.js:270:14)\r\n    at ServerResponse.OutgoingMessage._send (_http_outgoing.js:128:14)\r\n    at ServerResponse.OutgoingMessage.write (_http_outgoing.js:470:16)\r\n    at ReadStream.ondata (_stream_readable.js:525:20)\r\n    at emitOne (events.js:77:13)\r\n    at ReadStream.emit (events.js:169:7)\r\n    at readableAddChunk (_stream_readable.js:146:16)\r\n    at ReadStream.Readable.push (_stream_readable.js:110:10)\r\n    at onread (fs.js:1744:12)\r\n    at FSReqWrap.wrapper [as oncomplete] (fs.js:576:17)\r\n    at ReadStream.Readable.on (_stream_readable.js:655:33)\r\n    at ReadStream.Readable.pipe (_stream_readable.js:522:7)\r\n    at SendStream.stream (C:\\XXXX\\node_modules\\express\\node_modules\\send\\lib\\send.js:533:10)\r\n    at SendStream.send (C:\\XXXX\\node_modules\\express\\node_modules\\send\\lib\\send.js:480:8)\r\n    at C:\\XXXX\\node_modules\\express\\node_modules\\send\\lib\\send.js:392:10\r\n    at FSReqWrap.oncomplete (fs.js:82:15)\r\n    worker 1760 died\r\n\r\nThe problem only occurs on my production server (ovh, Windows Hyper-V, node v4.2.1) and not on my local development computer (Windows 10, node v4.2.0).\r\n\r\nIt is worthwhile mentioning that I am using socket.io. I am also using an external service called Global Counter that displays the number of online users. I am running setInterval() in one of the workers to remove expired records.\r\n\r\nCould someone tell me the meaning of these error messages, how the error occurs, and how I should solve it?"},"comment":{"url":"https://api.github.com/repos/nodejs/node/issues/comments/152909857","html_url":"https://github.com/nodejs/node/issues/3508#issuecomment-152909857","issue_url":"https://api.github.com/repos/nodejs/node/issues/3508","id":152909857,"user":{"login":"binarybehemoth","id":15277380,"avatar_url":"https://avatars.githubusercontent.com/u/15277380?v=3","gravatar_id":"","url":"https://api.github.com/users/binarybehemoth","html_url":"https://github.com/binarybehemoth","followers_url":"https://api.github.com/users/binarybehemoth/followers","following_url":"https://api.github.com/users/binarybehemoth/following{/other_user}","gists_url":"https://api.github.com/users/binarybehemoth/gists{/gist_id}","starred_url":"https://api.github.com/users/binarybehemoth/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/binarybehemoth/subscriptions","organizations_url":"https://api.github.com/users/binarybehemoth/orgs","repos_url":"https://api.github.com/users/binarybehemoth/repos","events_url":"https://api.github.com/users/binarybehemoth/events{/privacy}","received_events_url":"https://api.github.com/users/binarybehemoth/received_events","type":"User","site_admin":false},"created_at":"2015-11-02T04:29:24Z","updated_at":"2015-11-02T04:29:24Z","body":"Has the issue been addressed? I tried using v5.0.0 and the problem was still there. When can I obtain the fixed version?"}}