Details
-
Sub-task
-
Resolution: Done
-
L3 - Default
-
None
-
None
Description
AT
- Job Executor is functional
- Make configuration available via application.properties (they are not available via process engine configuration)
Decisions to make
Investigate what other Quarkus tasks use the Quarkus thread pool and decide if it makes sense to create a dedicated thread pool for the Job Executor or integrate the Job Executor into the Quarkus thread pool (Do Engine Job Executor tasks compete with HTTP requests? With what tasks would the Job Executor compete?).
Solution Ideas
- Job executor is managed by the Quarkus extension so that the thread pool of the Quarkus
application is used (ManagedExecutor is used to perform job execution) - Is there a way to spawn another thread pool via Quarkus and use this one?
- Job executor uses a dedicated thread pool
- When we add GraalVM support in the future, is it harder to achieve this with a dedicated thread pool?