Databases
StackOverflow2013
Postsdbo
POnode.js sockets.io disconnecting every ~25 seconds (heartbeat-related)
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POnode.js sockets.io disconnecting every ~25 seconds (heartbeat-related)
    primarykey
    data
    text
    <p>I'm trying to set up a node.js server, using socket.io. The problem I'm seeing is that my server is disconnecting+reconnecting the client every 25 seconds.</p> <p>Here's my server code:</p> <pre><code>var io = require('socket.io').listen(5876); io.sockets.on('connection', function (socket) { console.log("New connection established"); socket.on('disconnect', function() { console.log("A client has disconnected."); }); } </code></pre> <p>My client connects using the socket.io.js distribution. As I understand it (apparently incorrectly), I need my client to send a "heartbeat" (a message of "::2") every 15 seconds to prevent the server from thinking the connection is dead and disconnecting it. Basically:</p> <pre><code>&lt;script src="socket.io.js"&gt;&lt;/script&gt; &lt;script&gt; var socket = io.connect('http://localhost:5876'); socket.on('connect', function(data) { console.log("Connected to server."); setInterval(function() { socket.emit("::2"); console.log("sent heartbeat"); }, 15000); // schedule a heartbeat for every 15 seconds }); &lt;/script&gt; </code></pre> <p>But the client is still getting disconnected+reconnected every 25 seconds (excluding the very first 25th-second-tick).</p> <p>The node.js server console log looks like this (may have cut out some earlier identical connect/disconnect phases, as it was echoing every 25 seconds):</p> <pre><code>New connection established debug - emitting heartbeat for client 652791160849839915 debug - websocket writing 2:: debug - set heartbeat timeout for client 652791160849839915 debug - got heartbeat packet debug - cleared heartbeat timeout for client 652791160849839915 debug - set heartbeat interval for client 652791160849839915 info - transport end debug - set close timeout for client 652791160849839915 debug - cleared close timeout for client 652791160849839915 debug - cleared heartbeat interval for client 652791160849839915 A client has disconnected. debug - discarding transport debug - client authorized info - handshake authorized 5961067041159055274 debug - setting request GET /socket.io/1/websocket/5961067041159055274 debug - set heartbeat interval for client 5961067041159055274 debug - client authorized for debug - websocket writing 1:: New connection established </code></pre> <p>How can I stop my server from disconnecting+reconnecting the client every 25 seconds?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USJosh1billion
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POnode.js sockets.io disconnecting every ~25 seconds (heartbeat-related)
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POnode.js sockets.io disconnecting every ~25 seconds (heartbeat-related)
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POnode.js sockets.io disconnecting every ~25 seconds (heartbeat-related)
      1. This table or related slice is empty.
      1. VTUpMod
    1. COas far as i know you dont need to manually send heartbeat packets as this is handled by socket.io. Try checking the connection and disconnection events after taking out your manual heartbeat calls.
      singulars
      1. POnode.js sockets.io disconnecting every ~25 seconds (heartbeat-related)
      1. USf0x
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload