Skip to content

Conversation

@OndroMih
Copy link
Contributor

@OndroMih OndroMih commented Jan 2, 2026

This requires a new release of Grizzly 5.0, with this merged: eclipse-ee4j/glassfish-grizzly#2271

Adds support for a new "virtual" argument to thread pools - if true, GlassFish will switch to the built-in virtual thread pool provided by Grizzly.
Also allow specifying a class for the thread pool directly in the create-threadpool admin command.
Support monitoring for virtual threads.
Run monitoring test suite also for virtual threads.

Requires Grizzly snapshot build until Grizzly 5.0 is released.
Apply virtual threads by setting the thread pool class name to "org.glassfish.grizzly.threadpool.VirtualThreadExecutorService"

To do:
- the "Load defaults" button in Admin Console doesn't work - it doesn't restore the default class name to use platform threads
- enable virtual threads by a checkbox or allow selecting class name from a drop down from the 2 known types. Asadmin could support another argument that specifies the type of the pool instead of classname
- enable to reset to defaults, either by an empty class name or by the load defaults button in Admin Console
- monitoring doesn't work for the virtual threads pool

License headers
Change the impl to only use a single default thread pool classname. When classname is empty or default value, then decide based on virtual argument, do not set another classname.
@OndroMih OndroMih force-pushed the ondromih-2025-12-virtual-threads-grizzly branch from 401ca7d to 454e28d Compare January 4, 2026 13:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants