shutdown Optimize JVM on config error

XMLWordPrintable

    • Type: Bug Report
    • Resolution: Fixed
    • Priority: L3 - Default
    • 2.3.0
    • Affects Version/s: None
    • Component/s: 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.

            Assignee:
            Unassigned
            Reporter:
            Sebastian Bathke
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: