Uploaded image for project: 'camunda BPM'
  1. camunda BPM
  2. CAM-11410 Camunda Engine Quarkus Extension
  3. CAM-13634

Job Executor is functional

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: L3 - Default L3 - Default
    • 7.16.0, 7.16.0-alpha4
    • None
    • quarkus
    • None

      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

      1. 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)
      2. Is there a way to spawn another thread pool via Quarkus and use this one?
      3. 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?

        This is the controller panel for Smart Panels app

              nikola.koevski Nikola Koevski
              tassilo.weidner Tassilo Weidner
              Nikola Koevski Nikola Koevski
              Tassilo Weidner Tassilo Weidner
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: