Jetty IdleTimeout

Question

I go from jetty7.6 to berth-9.2. I see that the idletimeout value for mooring is reduced by 10 times.

At berth-7.6

<Set name="maxIdleTime">300000</Set> 

At berth-9.2:

 <Set name="idleTimeout"><Property name="http.timeout" default="30000"/></Set> 

Why?

And because of this, I constantly fall below the exception:

 WARN:oejs.HttpChannel:qtp607635164-14195: Commit failed java.util.concurrent.TimeoutException: Idle timeout expired: 30000/30000 ms at org.eclipse.jetty.io.IdleTimeout.checkIdleTimeout(IdleTimeout.java:156) at org.eclipse.jetty.io.IdleTimeout$1.run(IdleTimeout.java:50) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266).......... 

Thanks Anui

Answer 1

put this in your ${jetty.base}/start.ini

 http.timeout=300000 

which will restore your previous expectations.

It has been changed from a default of 5 minutes to 30 seconds as a timeout, simply because it is the best choice for most websites.

Answer 2

Using Jetty 9.4 and HTTPS, the above solution does not work. To fix this, I found an undocumented option that does not appear in .ini files:

jetty.ssl.idleTimeout=180000

Add this to your Jetty settings. start.d/<whatever>.ini or start.ini .

Answer 3

Correct setting

 ## Connector idle timeout in milliseconds # jetty.ssl.idleTimeout=30000 

This can be found in the ssl.mod file.