JPPF Issue Tracker
star_faded.png
Please log in to bookmark issues
feature_request_small.png
CLOSED  Feature request JPPF-26  -  Enable node management via the driver connection
Posted Aug 08, 2012 - updated Jan 19, 2013
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
     lolo4j
  • Category
    Management / Monitoring
  • Resolution
    RESOLVED
  • Priority
    High
  • Targetted for
    icon_milestones.png JPPF 3.3
Issue description
From this forum thread: http://www.jppf.org/forums/index.php/topic,1618.0.html - point 2) The idea is that when the nodes are reachable from the driver, but not from the client, to enable the client to monitor and manage the nodes nonetheless, by forwarding jmx requests and notifications via the driver.

This implies several particular problems:
  • forwarding of JMX requests and handling of results
  • how to handle MBean proxies
  • how to handle notification listeners and notifications

#1
Comment posted by
 lolo4j
Aug 08, 22:35
http://weblogs.java.net/blog/emcmanus/archive/2007/02/cascading_its_a_1.html

Server can act as JMX proxy forwarding JMX traffic to JPPFNode. JMX ObjectName with prefix: nodeId
#5
Comment posted by
 lolo4j
Aug 22, 06:12
The article provides a good idea of the kind of design we should adopt. However, it uses APIs from the OpenDMK project, which seems pretty dormant now, it hasn't been updated since 2008.
#7
Comment posted by
 lolo4j
Jan 01, 19:48
Committed trunk revision 2592.

The simplest solution I found was to create a driver MBean that will forward JMX requests to the nodes, based on a node selector, so that requests may be delegated to any number of nodes at once. I defined 3 types of selectors: "all nodes" to forward the request to all the nodes currently attached to the server, execution-policy based selector, and a selector that takes a list of node uuids.

The MBean interface provides both generic method ("invoke", "getAttribute", "setAttribute") so it will work with any node MBean including custom ones, and specific methods that delegate to the corresponding methods of JPPFNodeAdminMBean

What remains to do is the registration of notfiication listeners and the handling of notifications.
#17
Comment posted by
 lolo4j
Jan 18, 14:46
Dispatching of the notifications is now implemented and JUnit-tested. Documentation has been updated.

Changes committed to SVN trunk revision 2599

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