How to change Grizzly web server’s timeout from 5 minutes to 30 minutes

timeoutweb

I'm using Grizzly web server version 1.9.27. This server is used to provide clients with large amounts of data (over HTTPS, if that's relevant). Currently the server timeouts after 5 minutes. In other words, if a user is downloading a large amount of data, after 5 minutes, the HTTP(S) request processor is interrupted by Grizzly.

I need to increase it to at least 30 minutes.

I can't find any configuration file or any relevant information on Google to raise this timeout.

Any ideas?
Thanks

EDIT : (in response to DerfK) just checked the data and am seeing two different 'timeout' scenarios:

1- Server receives a request, asks the data manager to get the data. The data manager takes more than 5 minutes…during this time, there is no traffic between Grizzly and client.

2- Data server returns massive amounts of data which is transmitted to the client, but takes more than five minutes (because there is so much data).

First priority is solving problem 1, timeout when the connection is idle.

(I had to remove tag 'Grizzly' because I don't have enough points to create a new tag. I apparently do have enough points to create grizzly tag in stackoverflow…where this question was originally posted)

Best Answer

This code did the trick (for idle timeout):

GrizzlyWebServer ws;

ws.
   getSelectorThread().
   setKeepAliveTimeoutInSeconds(-1);

Related Solutions

IIS FTP service – download timeouts and restarts getting the data twice

Try downloading the file from the server itself and then try downloading the file from the same network as the server. If it works on the server then you may have a network issue, if it works from the network then you may have a firewall or router issue.

Nginx proxy_read_timeout vs. proxy_connect_timeout

I was actually unable to reproduce this on:

2011/08/20 20:08:43 [notice] 8925#0: nginx/0.8.53
2011/08/20 20:08:43 [notice] 8925#0: built by gcc 4.1.2 20080704 (Red Hat 4.1.2-48)
2011/08/20 20:08:43 [notice] 8925#0: OS: Linux 2.6.39.1-x86_64-linode19

I set this up in my nginx.conf:

proxy_connect_timeout   10;
proxy_send_timeout      15;
proxy_read_timeout      20;

I then setup two test servers. One that would just timeout on the SYN, and one that would accept connections but never respond:

upstream dev_edge {
  server 127.0.0.1:2280 max_fails=0 fail_timeout=0s; # SYN timeout
  server 10.4.1.1:22 max_fails=0 fail_timeout=0s; # accept but never responds
}

Then I sent in one test connection:

[m4@ben conf]$ telnet localhost 2480
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
GET / HTTP/1.1
Host: localhost

HTTP/1.1 504 Gateway Time-out
Server: nginx
Date: Sun, 21 Aug 2011 03:12:03 GMT
Content-Type: text/html
Content-Length: 176
Connection: keep-alive

Then watched error_log which showed this:

2011/08/20 20:11:43 [error] 8927#0: *1 upstream timed out (110: Connection timed out) while connecting to upstream, client: 127.0.0.1, server: ben.dev.b0.lt, request: "GET / HTTP/1.1", upstream: "http://10.4.1.1:22/", host: "localhost"

then:

2011/08/20 20:12:03 [error] 8927#0: *1 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 127.0.0.1, server: ben.dev.b0.lt, request: "GET / HTTP/1.1", upstream: "http://127.0.0.1:2280/", host: "localhost"

And then the access.log which has the expected 30s timeout (10+20):

504:32.931:10.003, 20.008:.:176 1 127.0.0.1 localrhost - [20/Aug/2011:20:12:03 -0700] "GET / HTTP/1.1" "-" "-" "-" dev_edge 10.4.1.1:22, 127.0.0.1:2280 -

Here is the log format I'm using which includes the individual upstream timeouts:

log_format  edge  '$status:$request_time:$upstream_response_time:$pipe:$body_bytes_sent $connection $remote_addr $host $remote_user [$time_local] "$request" "$http_referer" "$http_user_agent" "$http_x_forwarded_for" $edge $upstream_addr $upstream_cache_status';

Best Answer

Related Solutions

IIS FTP service – download timeouts and restarts getting the data twice

Nginx proxy_read_timeout vs. proxy_connect_timeout

Related Topic