Javascript Websocket Close = Server crash

Question

Hi was trying to send some data back and forth, and I found out that when I closed my client my server crashed...

My Server is Node.JS using the nodejs-websocket library.

Then I found out you had to add this.

window.onbeforeunload = function() {
    connection.close()
}

Is there away around this? Because if someone wanted to crash your server couldn't he just remove that from the JavaScript?

Please keep in mind this is my first time using websockets

Server Side:

var ws = require("nodejs-websocket");
var server = ws.createServer(function(conn){
        console.log("New connection")


        conn.on("end", function(code,reason){
            console.log('Connection Lost')
        });
}).listen(8001);

Error:

events.js:160
      throw er; // Unhandled 'error' event
      ^

Error: read ECONNRESET
    at exports._errnoException (util.js:1018:11)
    at TCP.onread (net.js:568:26)

Uhhh, the problem here is in your server-side code so we need to see that in order to offer you some help. — jfriend00, Sep 06 '17 at 18:39
What does your server output looks like when it shuts down? I can't imagine there not being any error messages that you could share with us. — Slava Eremenko, Sep 06 '17 at 19:22
@workaholic_gangster911 events.js:160 throw er; // Unhandled 'error' event ^ Error: read ECONNRESET at exports._errnoException (util.js:1018:11) at TCP.onread (net.js:568:26) — Simon V. Jackson, Sep 06 '17 at 19:26
@workaholic_gangster911 that's line 160 of some internal Node.js file — robertklep, Sep 06 '17 at 19:33

score 3 · Accepted Answer · answered Sep 06 '17 at 19:33

3

You may just have to listen to connection error events on your socket, and it won't throw an exception (and close your app). At least that's what this answer says: Node js ECONNRESET

Basically, try this first:

var ws = require("nodejs-websocket");
var server = ws.createServer(function(conn){
        console.log("New connection");

        conn.on("error", function(err) {
            console.log("Error caught: ")
            console.log(err.stack)
        });

        conn.on("end", function(code,reason){
            console.log('Connection Lost')
        });
}).listen(8001);

answered Sep 06 '17 at 19:33

Slava Eremenko

2,235
1
11
9

1

The server instance itself may also emit `error` events (https://github.com/sitegui/nodejs-websocket#event-errorerrobj) – robertklep Sep 06 '17 at 19:34
Sometimes the answer is just too damm simple! You right thank you! – Simon V. Jackson Sep 06 '17 at 19:37

Javascript Websocket Close = Server crash

1 Answers1