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
Hello,
I use the quarkus-smallrye-graphql extension in my project and I've noticed that it uses Vert.x worker threads. My use-case requires me to use my own ExecutorService for the worker threads (I want to decorate the Runnabe/Callable before execution). From what I understand, Quarkus initializes Vert.x in the VertxCoreRecorder class with default QuarkusExecutorFactory used in VertxBuilder. QuarkusExecutorFactory implements ExecutorServiceFactory, which is part of Vert.x SPI.
Is it possible to override the default QuarkusExecutorFactory in Vert.x configuration somehow?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
I use the quarkus-smallrye-graphql extension in my project and I've noticed that it uses Vert.x worker threads. My use-case requires me to use my own ExecutorService for the worker threads (I want to decorate the Runnabe/Callable before execution). From what I understand, Quarkus initializes Vert.x in the VertxCoreRecorder class with default QuarkusExecutorFactory used in VertxBuilder. QuarkusExecutorFactory implements ExecutorServiceFactory, which is part of Vert.x SPI.
Is it possible to override the default QuarkusExecutorFactory in Vert.x configuration somehow?
Beta Was this translation helpful? Give feedback.
All reactions