Well If I run the example it actually works. I haven't moved to testing in a multi node environment but my problem is with regards to integration with RxJava <https://github.com/ReactiveX/RxJava> library which I am using to leverage its reactive features.
Within the broker <https://github.com/caricah/iotracah> during initialization at the class <https://github.com/caricah/iotracah/blob/master/core/src/main/java/com/caricah/iotracah/core/init/ServersInitializer.java> on line 379, if I use the created ignite executor the application is not processing the requests however if i substitute with java's default executor on line 380 it works, same thing happens for the default RxJava's io schedular on line 381 as it also works. In isolation the ignite executor service actually works the way its expected however when used within RxJava's schedular it seems not to respond appropriately. And that is the source of my problems. You can actually test the application by running "./gradlew clean install assemble run" and using mosquitto client to subscribe using the command "mosquitto_sub -t /life/# -q 2 -i total-subscriber -u bwire -P power -d" on another terminal. Then just comment out the above lines appropriately to verify. e.g. to test ignite executor enable line 379 to test the default executor enable line 380. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-executor-does-not-working-with-RxJava-as-a-scheduler-tp1543p1545.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
