The maxIdleTime attribute will set a timeout on the socket, so
that if a servlet blocks reading or writing to the connection it
will be timed out.
However, Jetty does not have a timeout that tries to kill a request
that is blocked elsewhere. Mostly because such timeouts are expensive
and can cover over bad code. Also there is an issue of exactly how
you stop such a request? Ie what do you do if interrupt does not work?
how much time do you give the thread to try to handle an interrupt? etc.
etc.
cheers
that if a servlet blocks reading or writing to the connection it
will be timed out.
However, Jetty does not have a timeout that tries to kill a request
that is blocked elsewhere. Mostly because such timeouts are expensive
and can cover over bad code. Also there is an issue of exactly how
you stop such a request? Ie what do you do if interrupt does not work?
how much time do you give the thread to try to handle an interrupt? etc.
etc.
cheers