ThreadExecutor | Implement executors on your application

So after digging through the source for flask-socketIO, I discovered that socketIO likes to hog threads. This means you have to monkey patch it yourself into using another either using gevent or eventlet. this post explains it quite well and lead me to the fix to my bug.

It looks like the problem is that it can't connect to 15.206.28.47 during startup.

You problem is here:

Just reposting the answer of @M.Deinum to mark this as the correct answer, because it helped me a lot.

Then you have 2 instances of the service, one proxied for the async the other not. You probably have a ContextLoaderListener loading the same componetns as the DispatcherServlet effectivly duplicating bean instances

The problem was, that I used component-scan for the same package in spring-mvc-servlet.xml and applicationContext.xml

For the error I can infer that the tables aren't properly created (either not at all or using the wrong scripts). For Quartz, you need to create the tables using the db scripts for you database type, which you can find in the quartz download.

Here is a similar case: https://groups.google.com/forum/#!topic/axonframework/IlWZ0UHK2hk

If you think that the script is OK, please try to create the table directly in your database.

In case that it still does not work you can go to the next step and check the configuration. Maybe the tablePrefix that you are using is not well interpreted. Try to use the default QRTZ_.

Here is an setup example with a lower version of Quartz.

http://www.opencodez.com/java/quartz-scheduler-with-spring-boot.htm

Let me know if it works!

Finally I get it working the following way:

• I refused from using Spring's SchedulerFactoryBean on a client, but instead I directly create an instance of StdSchedulerFactory from quartz library (then it properly creates an instance of RemoteScheduler): new StdSchedulerFactory(). It properly connects to a server quartz instance.

• Due to I cannot obtain an instance of StdSchedulerFactory from SchedulerFactoryBean I just pass both to beans where it is needed. So on a client app SchedulerFactoryBean is null, and on a server app StdSchedulerFactory is null.

• Job schedule part is the same for both factories as all I do with them is obtain scheduler:

No,

You don't know in what state the Hashset might be during add by another Thread. There might be fundamental changes ongoing, like splitting of buckets, so that contains may return false during the adding by another thread, even if the element would be there in a singlethreaded HashSet. In that case you would try to add an element a second time.

Even Worse Scenario: contains might get into an endless loop or throw an exception because of an temporary invalid state of the HashSet in the memory used by the two threads at the same time.

I see no repetition in your code. To reduce boilerplate code, try a lambda:

As per suggestion by Claus, i made the following changes to my main method and it is working as expected now. Previously i was using the below code for initializing my context and starting up routes and thus JVM was stopping it's execution :