JPPF Issue Tracker
star_faded.png
Please log in to bookmark issues
feature_request_small.png
CLOSED  Feature request JPPF-46  -  Missing public API to determine which and how many nodes are idle
Posted Aug 22, 2012 - updated Aug 24, 2012
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
  • Progress
       
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
  • Posted by
    lolo4j
  • Owned by
    Not owned by anyone
  • Category
    Management / Monitoring
  • Resolution
    RESOLVED
  • Priority
    Normal
  • Targetted for
    icon_milestones.png JPPF 3.2
Issue description
Currently, there is no documented way to tell which nodes are idle (not executing a job), apart form connecting to each node's jmx server, retrieving the node's state and looking at its execution status to determine whether its value is the string "Idle".

What we need to do: - in the JPPFNodeState class, implement the execution state and connection status as Enum types - on the server side, maintain the execution state, and add an API in the JPPFDriverAdminMBean to obtain the list of currently Idle/Executing nodes

#2
Comment posted by
lolo4j
Aug 24, 06:50
This feature is now implemented. Changes committed to SVN revision 2340. Documentation updated accordingly: revision 2341

The issue was updated with the following change(s):
  • This issue has been closed
  • The status has been updated, from New 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.