JPPF Issue Tracker
star_faded.png
Please log in to bookmark issues
bug_report_small.png
CLOSED  Bug report JPPF-274  -  Server-local nodes cannot be managed
Posted May 24, 2014 - updated Mar 28, 2016
icon_info.png This issue has been closed with status "Closed" and resolution "RESOLVED".
Issue details
  • Type of issue
    Bug report
  • 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
  • Reproducability
    Always
  • Severity
    Normal
  • Targetted for
    icon_milestones.png JPPF 4.1.x
Issue description
When a driver is setup with a single, local node, it seems that the node cannot be managed. The node is displayed in the admin console as "null:12192" where the host is null. This prevents any managment operation from working on that node.
Steps to reproduce this issue
  • Configure a driver with jppf.local.node.enabled = true and start the driver
  • Start the admin console
  • ==> the topology view displays the node as null:12192 (or whatever the prot number is)

#4
Comment posted by
lolo4j
May 24, 07:43
There are two things wrong:
  1. the management host was not computed properly, leading to null being sent to the client/console instead
  2. the node provisioning fails for a local node because the driver does not have commons-io.jar in its classpath
#5
Comment posted by
lolo4j
icon_reply.pngMay 24, 07:48, in reply to comment #4
Correction: commons-io is indeed in the driver distribution. It was just missing in my Eclipse launch configuration.
#6
Comment posted by
lolo4j
icon_reply.pngMay 24, 07:53, in reply to comment #5
Well, on the other hand, I just realized that commons-io-2.4.jar is not in the dependencies of the artifacts we publish to maven central (: I registered Bug report JPPF-275 - Dependency on commons-io is missing in maven artifacts for this
#7
Comment posted by
lolo4j
May 24, 08:20
Fixed in: