JPPF Issue Tracker
star_faded.png
Please log in to bookmark issues
bug_report_small.png
CLOSED  Bug report JPPF-477  -  Clarify usage of 'jppf.discovery.enabled" and "jppf.remote.execution enabled" in client config
Posted Sep 23, 2016 - updated Sep 30, 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
    Documentation
  • Resolution
    RESOLVED
  • Priority
    Normal
  • Reproducability
    Always
  • Severity
    Normal
  • Targetted for
    icon_milestones.png JPPF 5.2.2
Issue description
From this forum post.

In Configurtion > Client and administration console configuration, we should be more clear as to the effects of 'jppf.discovery.enabled" vs. "jppf.remote.execution enabled", as the docuemntation is slightly confusing/ambiguous.

We could add something like: "jppf.discovery.enabled" toggles beween automatic discovery via UDP multicast (when true) and manually defined connections in the configuration (when false), whereas "jppf.remote.execution.enabled = false" disables both.
Steps to reproduce this issue
N/A

#3
Comment posted by
lolo4j
Sep 30, 10:36
Fixed in: