Running against Apache Ignite version:
ignite-core (1.3.2), ignite-spring (1.3.2), ignite-indexing (1.3.2) and ignite-slf4j (1.3.2).
Originally built application against a Grid Gain version before moving to Apache Ignite.
Web Application feeds jobs to the worker node(s) via it's own internal queue (client only Ignite). After a few thousand jobs have successfully been processed, the worker and server just stop with jobs still waiting in the web server queue. It appears that the worker node is running OK, and logs will show every job is successfully completing the render but the future on the server is not being triggered - loss of connection to node?
I have attached the requested information to the ticket. It's highly likely I've done something wrong rather than this being a bug with Ignite - any advice would be appreciated,
- Server stack
- Worker node stack
- Server log file (simple debug output, no output observed from Ignite set at INFO level nor any exceptions)
- Worker log file (same setup as server log file)
- Ignite configuration files for both server and worker.
- Launch parameters for the java command line and tomcat7 server.