You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Need a way to limit jersey-server-managed-async-executor thread pool size in helidon mp
Environment Details
Helidon Version:1.4.1
Helidon MP
JDK version: 1.8
OS: ubuntu
Docker version (if applicable):
Problem Description
We are using AsyncResponse with helidon-mp and want to see if there is any performance improvement if we use same shared thread pool across the app. So want to know if there is a way to replace this jersey async thread pool.
Steps to reproduce
Start helidon-mp server and make any get request and see the thread count by connecting jvisualvm
The text was updated successfully, but these errors were encountered:
The PR (one for master will follow shortly) adds support to configure the managed async executor service.
You can configure both the default and async executor services through the usual configuration mechanisms, example using META-INF/microprofile-config.properties:
# configure custom prefix for Jersey executor service (server)
server.executor-service.thread-name-prefix=jersey-
# configure custom prefix for Jersey async executor service (server)
server.jersey.async-executor-service.thread-name-prefix=jersey-async
Need a way to limit jersey-server-managed-async-executor thread pool size in helidon mp
Environment Details
Problem Description
We are using AsyncResponse with helidon-mp and want to see if there is any performance improvement if we use same shared thread pool across the app. So want to know if there is a way to replace this jersey async thread pool.
Steps to reproduce
Start helidon-mp server and make any get request and see the thread count by connecting jvisualvm
The text was updated successfully, but these errors were encountered: