Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Currently when an error occurs in a NodeJS server (eg: Buffer “out of bounds”), the entire server grinds to a halt. Is there a way to configure it such that only the socket on which the error occured gets disconnected leaving the server online and the other connections active? I could use the “uncaughtException” error but then there would be no way of knowing which socket caused the error/crashed. How is this handled typically?
You can use the
try .. catch(err)construct to catch any exceptions occurring within any callback of the the socket, and subsequentlysocket.end(), to disconnect the client if an error occurs. This prevents the entire server from crashing. Obviously for the other “uncaught” errors you’ll have to resort to the “uncaughtException” callback, which does not end the server. Why don’t you read this and this for more answers.