Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

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)

share|improve this question

migrated from Jan 18 '11 at 19:26

This question came from our site for professional and enthusiast programmers.

can this question still be seen on stackoverflow? I asked it there because the answer may be "change the code in the following file and recompile since there is no 'administrative' way to change the timeout limit" – user23398 Jan 18 '11 at 19:44
Couple of questions: A) are you sure it's grizzly's fault (log entry?) and B) was it actually sending data at the time or was it waiting idle while some giant database query grinds? As for being moved, the post will still appear on the original site with a redirect to this site. – DerfK Jan 18 '11 at 20:35
up vote 1 down vote accepted

This line did the trick (for idle timeout): ... ws.getSelectorThread().setKeepAliveTimeoutInSeconds(-1); ...

Where 'ws' is an instance of GrizzlyWebServer

share|improve this answer
Glad you resolved [or created a work around for] this issue. Please be sure to mark your answer as "accepted" when you are able. – jscott Jul 25 '12 at 0:21

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.