ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Darren Edmonds (JIRA)" <j...@apache.org>
Subject [jira] [Created] (IGNITE-1179) Futures stop working, unknown cause.
Date Fri, 31 Jul 2015 08:45:04 GMT
Darren Edmonds created IGNITE-1179:

             Summary: Futures stop working, unknown cause.
                 Key: IGNITE-1179
                 URL: https://issues.apache.org/jira/browse/IGNITE-1179
             Project: Ignite
          Issue Type: Bug
          Components: compute
            Reporter: Darren Edmonds

Running against Apache Ignite version: 

ignite-core (1.06), ignite-spring (1.06), ignite-indexing (1.06) and ignite-slf4j (1.06).

Originally built application against a Grid Gain version before moving to Apache Ignite -
upgrading to the latest version, break the application and requires some work - trying to
avoid if at all possible but expecting that'll be the suggested option to address issue.

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 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 advise would be appreciated,

Attachement contains:
- 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.

This message was sent by Atlassian JIRA

View raw message