|Re: [jetty-users] Jetty 9.2.3 java.util.concurrent.TimeoutException|
Hi, On Mon, Nov 3, 2014 at 6:00 PM, Rajiv Bandaru <rajivbandaru@xxxxxxxxx> wrote: > Thank you for your response. > > We are in a high load/volume environment and our response times are usually > less than 50ms. Thats the reason why I have 200ms. However, I tried various > idle timeout values, even 30000ms does result in the same exception. If your connection idle timeouts after 30s, it means that either your application does not write data correctly, or your system is overloaded for the configuration you have. You don't provide any other information, so difficult to help. -- Simone Bordet ---- http://cometd.org http://webtide.com http://intalio.com Developer advice, training, services and support from the Jetty & CometD experts. Intalio, the modern way to build business applications.
Back to the top