Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jetty-users] (Jetty 9.2.13.v20150730) Relationship between threadPool.setIdleTimeout and connector.setIdleTimeout

Thanks for that. It was just as I thought it was from Jetty 8.

I have been questioning a lot of things since I did the upgrade and had a strange problem. I've opened a new thread for it since I have more details now.

On Mon, Sep 7, 2015 at 4:56 PM, Simone Bordet <sbordet@xxxxxxxxxxx> wrote:

On Mon, Sep 7, 2015 at 5:26 AM, Melissa Mifsud
<melissa.anne.mifsud@xxxxxxxxx> wrote:
> Hi,
> I have been trying to investigate what the relationship between the
> idleTimeout settings on:
> QueuedThreadPool.setIdleTimeout
> ServerConnector.setIdleTimeout
> when both are set?

There is no relationship.

The QueuedThreadPool idle timeout specifies how long a thread that has
been pooled can remain idle in the pool before being terminated.
Imagine you had a spike in the traffic load of your server; more
threads were created, but then the load goes back to normal. The
additional threads would stay in the pool for the idle timeout and
then be terminated (one at a time).

The ServerConnector idle timeout specifies how long a TCP connection
that has been created can remain idle (i.e. no bytes traffic on it in
either read or write direction) before being closed.

> I noticed that most of the examples and code I have found sets the
> idleTimeout on the Connector and not on the pool.
> I am using Jetty 9.2.13.v20150730. I set both idleTimeout. Recently I
> changed the values so that:
> QueuedThreadPool.setIdleTimeout(300000)
> Connector.setIdleTimeout(60000)
> I'm wondering if this could cause problems.


Simone Bordet
Developer advice, training, services and support
from the Jetty & CometD experts.
jetty-users mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit


Melissa Anne Mifsud

Back to the top