Nodejs and express server closes connection after 2 minutes

Question

Im using Express 4.X and node js 0.12.

One of my routes is for file uploading and processing and for some of the files the upload and process takes more than the 2 minutes default timeout. I have tried to settimeout to values more than 2 minutes but its just not working, the server closes connection exactly after 2 minutes every time.

server.timeout = 60 * 60 * 1000; // still closes after 2 minutes
server.on('connection', function(socket) {
  socket.setTimeout(700 * 1000); // still closes after 2 minutes
});

res.setTimeout(0);// still closes after 2 minutes
req.setTimeout(0);// still closes after 2 minutes
res.connection.setTimeout(0);// still closes after 2 minutes

The connect-timeout middleware is not helped either, it just keeps closing the connection after exactly 2 minutes. Tried changing the node version to older version but with no success. Tried all the variations found online, but the connection still closes...

Possible duplicate of [Express.js Response Timeout](http://stackoverflow.com/questions/21708208/express-js-response-timeout) — Ionut Necula, Oct 01 '15 at 08:19
Tried that as-well, connect middleware results in the same 2 minute timeout... — Dima Grossman, Oct 01 '15 at 08:24
Sorry, not quite sure what you want me to read there. As i've already told, I have tried all their suggestions and none of them works. — Dima Grossman, Oct 01 '15 at 08:28
If you're using Express 4.X where timeout middleware has been removed so need to manually add it. You did that? — Ionut Necula, Oct 01 '15 at 08:29
Yes I did, added the connect-timeout middleware. The same issue persists... — Dima Grossman, Oct 01 '15 at 08:30
@scopsy Are you sure , is it a server-side issue? Because some browsers' http timeouts are 120000ms and some 300000ms. — İlker Korkut, Oct 01 '15 at 09:07

score 16 · Answer 1 · edited May 23 '17 at 12:34

16

server.setTimeout() is the method that sets the HTTP connection timeout for all connections.

The 2 minutes are default.

UPDATED ANSWER

Try this:

var express = require('express');
var http = require('http');

var app = module.exports.app = express();
var server = http.createServer(app);
server.setTimeout(10*60*1000); // 10 * 60 seconds * 1000 msecs
server.listen(appConfig.port, function () {
    var logger = app.get('logger');
    logger.info('**** STARTING SERVER ****');
});

Or this:

http.request(url).setTimeout()

Also, it can be a browser issue. Read this.

edited May 23 '17 at 12:34

Community

1
1

answered Oct 01 '15 at 08:32

Ionut Necula

11,107
4
45
69

Tried that still closes connection after 120000ms – Dima Grossman Oct 01 '15 at 08:37

score 2 · Answer 2 · edited May 05 '17 at 18:55

2

how about:

server.on('connection', function(socket) {
  socket.setTimeout(5 * 60 * 1000);
  socket.once('timeout', function() {
    process.nextTick(socket.destroy);
  });
});

edited May 05 '17 at 18:55

Sebyddd

4,305
2
39
43

answered Oct 01 '15 at 08:34

num8er

18,604
3
43
57

As mentioned, the timeout middleware is not working as expected the connection closes after 2 minutes. – Dima Grossman Oct 01 '15 at 08:41
I saw it, so I was updating my answer, check now (: – num8er Oct 01 '15 at 08:42
Nope, still the same :( It's made me crazy, and the craziest part that before a month a go the socket.setTimeout() did fix thaht and suddenly 2 days ago it returned with no reason at all. – Dima Grossman Oct 01 '15 at 08:50
You want to close connection after 700 seconds? – num8er Oct 01 '15 at 08:51
I just want to make the default 2 minute timeout change to anything that will work (about 5 min is fine.) – Dima Grossman Oct 01 '15 at 08:53
scopsy, how about checking my answer? (: – num8er Oct 01 '15 at 09:06
1

The issue was with browser-sync all the time... it opened parallel socket to the request which i guess had internal timeout of 2 minutes regardless of the server config. After switching it off the initial socket.setTimeout(600 * 60 * 1000); works perfectly. – Dima Grossman Oct 01 '15 at 09:36
1

Thanks god, spent around 4 hours on that :( – Dima Grossman Oct 01 '15 at 09:39

score 1 · Accepted Answer · answered Oct 01 '15 at 09:32

After a few hours of trying every answer available I had run an inspection with fiddler for that request. Turns out that in my development environment im using browser-sync for auto refreshing the browser window on any change. In fiddler i noticed that a long with the upload POST request browser-sync tied it to a socket connection which had 2 minute timeout.

after switched off the browser-sync proxy the very first solution worked like a charm.

server.on('connection', function(socket) {
  socket.setTimeout(600 * 60 * 1000); // now works perfectly...
})

Nodejs and express server closes connection after 2 minutes

3 Answers3

Linked