Does Dropwizard 3.x Plan to Expose Virtual Thread Configuration for Jersey Resources on Jetty 11?

Direct Answer

No, Dropwizard 3.x does not currently expose a formalized, built-in configuration option to enable virtual thread execution for Jersey resources on Jetty 11.

Confirmed Facts

• Dropwizard 3.x utilizes Jetty 11 with Jakarta EE namespaces.
• Jetty 11 supports experimental virtual threads via Java 21+ Project Loom.
• Configuration for virtual threads must be applied manually, typically via custom executor setup.

Likely Explanation

The lack of native configuration is due to the experimental nature of virtual threads in Jetty 11 and significant compatibility hurdles with existing Dropwizard components, particularly those relying on thread-local state, such as Hibernate session management.

Steps for Current Implementation

1. Identify the Jetty server instance within the Dropwizard bootstrap process.
2. Replace the default executor with a custom executor designed to leverage virtual threads.
3. Thoroughly validate that all thread-local dependent libraries (e.g., Hibernate) function correctly under the virtual thread execution model, likely requiring session-per-virtual-thread patterns.

Missing Diagnostic Detail

What specific session management pattern is employed by the existing Hibernate bundle (e.g., thread-local, injected EntityManager)? This detail is necessary to confirm if a refactoring of session handling is required before virtual threads can be safely adopted.