JPPF Issue Tracker
star_faded.png
Please log in to bookmark issues
feature_request_small.png
CLOSED  Feature request JPPF-526  -  Enable NIO-based recovery/heartbeat mechanism
Posted Mar 03, 2018 - updated Jul 09, 2018
action_vote_minus_faded.png
0
Votes
 action_vote_plus_faded.png
icon_info.png This issue has been closed with status "Closed" and resolution "RESOLVED".
Issue details
  • Type of issue
    Feature request
  • Status
     
    		 Closed
  • Assigned to
    lolo4j
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
  • Posted by
    lolo4j
  • Owned by
    Not owned by anyone
  • Category
    Networking
  • Resolution
    RESOLVED
  • Priority
    Normal
  • Targetted for
    icon_milestones.png JPPF 6.0
Issue description
Currently, the recovery mechanism uses a connection to a separate driver port. We propose to rewrite it so that it uses the non-blocking NIO based communications, which will allow it to use the same port as for nodes and clients connections. It will then be a matter of enbling it or not.

#3
Comment posted by
lolo4j
Jul 06, 07:41
The state model used on the server-side is wrong and needs significant rafactoring, therefore I'm reopening this issue

The issue was updated with the following change(s):
  • The status has been updated, from Closed to New.
  • This issue has been reopened
  • The resolution has been updated, from RESOLVED to Not determined.