JPPF Issue Tracker
star_faded.png
Please log in to bookmark issues
bug_report_small.png
CLOSED  Bug report JPPF-164  -  The property jppf.local.execution.enabled not used at client startup
Posted Jul 07, 2013 - updated Jul 07, 2013
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
     lolo4j
  • Category
    Client
  • Resolution
    RESOLVED
  • Priority
    Normal
  • Reproducability
    Always
  • Severity
    Normal
  • Targetted for
    icon_milestones.png JPPF 3.3.4
Issue description
When a JPPF cient starts, it does not lookup for the property "jppf.local.execution.enabled". Thus when it is set to true, local execution is actually not enabled.
Steps to reproduce this issue
  • configure a JPPF client application "jppf.local.execution.enabled = true"
  • do not start any driver or node
  • launch the JPPF client application and submit a job
  • ==> the job does not start, when it should start executing in the client's JVM

#3
Comment posted by
 lolo4j
Jul 07, 09:44
The fix is very simple: in ABstractGenericClient we have the following method:
protected void initPools(final TypedProperties config)
{
  if (debugEnabled) log.debug("initializing connections");
  LinkedBlockingQueue queue = new LinkedBlockingQueue();
  executor = new ThreadPoolExecutor(0, Integer.MAX_VALUE, 60L, TimeUnit.SECONDS, queue, new JPPFThreadFactory("JPPF Client"));
  if (config.getBoolean("jppf.remote.execution.enabled", true)) initRemotePools(config);
}
all we need to do is add this line at the end:
if (config.getBoolean("jppf.local.execution.enabled", false)) setLocalExecutionEnabled(true);
#4
Comment posted by
 lolo4j
Jul 07, 09:52
Fixed. Canges committed to SVN:

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