Re: [jetty-users] Failing to connect with v9.2.2 HttpClient

[Joakim Erdfelt <joakim@xxxxxxxxxxx>]

You starved the executor / threadpool. Simple enough.

Why do you have such a tiny threadpool to begin with?

Our threadpool / executor defaults assume reasonable baselines.

Our defaults:

  Executor impl: QueuedThreadPool

  max threads: 200

  min threads: 8

  idle timeout: 60,000 ms

  backed by: BlockingArrayQueue

These are practical limits based on what is considered a modern baseline from 2010.

Suitable for limited devices of the day (such as J2ME, Raspberry Pi, and Android)

These defaults also perform splendidly for larger systems as well.

Your FixedThreadPool executor is a premature optimization that is harming you.

--

Joakim Erdfelt <joakim@xxxxxxxxxxx>

webtide.com - intalio.com/jetty

Expert advice, services and support from from the Jetty & CometD experts

eclipse.org/jetty - cometd.org