Poornima, for better or for worse, the idle timeout is not actually applied to servlet processing time (by the spec). If you did a write and that blocked for 40s, then Jetty would process the timeout. But while the servlet is processing or doing small fast writes, then the idle timeout does not apply.
Jetty used to apply the timeout and try to interrupt the dispatched thread, but this caused many problems as many frameworks do not correctly handle interrupt and the servlet spec does not support that kind of action. In short, the idle timeout only applies to doing actual IO operations. So a read or a write will timeout if it takes more than 40s... including reading the original request. regards On 23 February 2016 at 01:24, [email protected] <[email protected]> wrote: > I have written a synchronous servlet. Can you answer my question now ? > > Regards, > Poornima. > > > > On 02/22/2016 02:08 AM, Simone Bordet wrote: > >> Hi, >> >> On Thu, Feb 18, 2016 at 7:55 PM, [email protected] >> <[email protected]> wrote: >> >>> Hi, >>> >>> I use jetty 9.3.x. I have set the idleTimeout in jetty-http.xml (in >>> addConnector) to 40000. I have written a servlet which takes 60 seconds >>> to >>> respond. I am still getting the response after 60 seconds instead of the >>> connection getting terminated. >>> >> Depends how you write your servlet, specifically whether it's async or >> not. >> >> > _______________________________________________ > jetty-users mailing list > [email protected] > To change your delivery options, retrieve your password, or unsubscribe > from this list, visit > https://dev.eclipse.org/mailman/listinfo/jetty-users > -- Greg Wilkins <[email protected]> CTO http://webtide.com
_______________________________________________ jetty-users mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/jetty-users
