Uploaded image for project: 'Camunda Optimize'
  1. Camunda Optimize
  2. OPT-1657

shutdown Optimize JVM on config error

XMLWordPrintable

    • Icon: Bug Report Bug Report
    • Resolution: Fixed
    • Icon: L3 - Default L3 - Default
    • 2.3.0
    • None
    • backend
    • None

      Currently on any severe spring context error the jetty server get's killed but the Optimize jvm still runs.
      This is due to zombie quartz threads, see attached screenshot. We need to revisit how quartz get's initialized and why it's not bound to die with the application context.

        This is the controller panel for Smart Panels app

          1. Selection_009.png
            Selection_009.png
            101 kB

            [OPT-1657] shutdown Optimize JVM on config error

            There are no comments yet on this issue.

              Unassigned Unassigned
              sebastian.bathke Sebastian Bathke
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: