quartz scheduler not killed on redeploy

[bernji]

Hi there,

today I found out using probe on my tomcat that the quartz scheduler are not killed on un-/redeploy of my war which uses the es plugin.

I appears that the plugin is not shut down "the nice way". Is there a way to do this? Maybe a service method I could call in the Bootstrap class in the destroy method that is shutting down the elastic search plugin?

Best,
Bernhard

[bernji]

no support in here?

[bernji]

Here is the sollution:
When you declare
elasticSearch.client.mode = "node"
the threads are not killed.
but when you declare
elasticSearch.client.mode = "dataNode"
the threads are killed.

This is because you are only chekcing for mode == "local" and "dataNode" but not for "node". When mode is local or dataNode you call shutdown()

You should fix this because servers get slow when threads are left abandoned when one redeploys.