JPPF Issue Tracker
Please log in to bookmark issues
CLOSED  Bug report JPPF-172  -  Failover in the client is not working
Posted Jul 26, 2013 - updated Dec 27, 2014
icon_info.png This issue has been closed with status "Closed" and resolution "RESOLVED".
Issue details
  • Type of issue
    Bug report
  • Status
  • Assigned to
  • Progress
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
  • Posted by
  • Owned by
    Not owned by anyone
  • Category
  • Resolution
  • Priority
  • Reproducability
  • Severity
  • Targetted for
    icon_milestones.png JPPF 3.3.x
Issue description
When a client is connected to two servers or more, and when a job is submitted to one of the servers, if the server crashes or the connection is broken, the job is not resubmitted to an other server.

I noticed that if the crashed server is restarted soon enough (before the delay specified by the client config property reconnect.max.time), the job is sent again to that server.
Steps to reproduce this issue
  • start 2 servers, each with one node attached
  • start a client that connects to these two servers and submits a job with at least one task that is sufficently long-lasting
  • while the job is executing, kill the server to which the job is submitted
==> the job is never re-submitted to the other server

Comment posted by
Jul 27, 07:22
Fixed. Changes committed to SVN:

The issue was updated with the following change(s):
  • This issue has been closed
  • The status has been updated, from Confirmed to Closed.
  • This issue's progression has been updated to 100 percent completed.
  • The resolution has been updated, from Not determined to RESOLVED.
  • Information about the user working on this issue has been changed, from lolo4j to Not being worked on.