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
- is related to
-
OPT-1555 Do not start Optimize if the engine version does not match
-
- Done
-