JPPF Issue Tracker
star_faded.png
Please log in to bookmark issues
bug_report_small.png
CLOSED  Bug report JPPF-408  -  JPPFClient does not honor remote execution requirement nor start and expiration schedules for broadcast jobs
Posted Aug 01, 2015 - updated Aug 07, 2015
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
    Client
  • Resolution
    RESOLVED
  • Priority
    Normal
  • Reproducability
    Always
  • Severity
    Normal
  • Targetted for
    icon_milestones.png JPPF 5.0.4
Issue description
When a broadcast job is submitted with a start or expiration schedule in its client or server SLA, this schedule is not taken into account, and instead the job starts imediately and/or does not expire.

Additionally, if local execution in the client is enabled, the broadcast job will execute locally, whereas the related documentation states that it doesn't.
Steps to reproduce this issue
  • configure a client with rmeote and local executions both disabled
  • submit a broadcast job with an expiration: job.getClientSLA().setJobExpirationSchedule(new JPPFSchedule(5000L));
==> the job just hangs: it is not executed and never expires

#6
Comment posted by
 lolo4j
Aug 07, 07:19
Fixed in: