如何在Jetty 9.2.24 HttpClient中添加线程池？Jetty9替代方案咨询

Hey there! I totally get the frustration when familiar methods get removed in framework updates—let's fix this thread pool issue for your Jetty 9.2.24 HttpClient right away.

Why the Method Got Removed #

Jetty 9 refactored the HttpClient's threading model to rely on Java's standard Executor interface instead of a direct ThreadPool dependency. This change makes the HttpClient far more flexible: you can now use Jetty's own thread pools or any JDK Executor implementation (like ThreadPoolExecutor) based on your needs.

Your Updated Implementation #

Since QueuedThreadPool already implements the Executor interface, you just need to swap out setThreadPool() with setExecutor(). Here's how to adjust your original code:

// 1. Create and configure your custom thread pool exactly as before
QueuedThreadPool queuedThreadpool = new QueuedThreadPool(5);
queuedThreadpool.setMinThreads(2);
queuedThreadpool.setName("HttpClient");

// Optional but recommended: Start the thread pool explicitly
// (HttpClient will start it automatically if you skip this, but manual start gives you better control)
queuedThreadpool.start();

// 2. Initialize HttpClient and set the executor instead of thread pool
HttpClient httpClient = new HttpClient();
httpClient.setExecutor(queuedThreadpool); // This replaces the old setThreadPool() call

// Add any other HttpClient configurations you need here...

// 3. Start the HttpClient as usual
httpClient.start();

Cleaner Approach with HttpClientBuilder #

Jetty 9.2 introduced HttpClientBuilder for more readable, fluent configuration. You can set the executor directly in the builder chain:

QueuedThreadPool queuedThreadpool = new QueuedThreadPool(5);
queuedThreadpool.setMinThreads(2);
queuedThreadpool.setName("HttpClient");
queuedThreadpool.start();

HttpClient httpClient = HttpClientBuilder.create()
    .executor(queuedThreadpool)
    // Add other configs like followRedirects(), setMaxRedirects(), etc.
    .build();

httpClient.start();

Quick Lifecycle Notes #

• If you're using Jetty's QueuedThreadPool, calling httpClient.stop() will automatically shut down the thread pool for you.
• If you switch to a custom JDK Executor (like ThreadPoolExecutor), you'll need to handle its shutdown manually after stopping the HttpClient.

内容的提问来源于stack exchange，提问作者Dipankar Dey