JPPF Issue Tracker
star_faded.png
Please log in to bookmark issues
enhancement_small.png
OPEN  Enhancement JPPF-611  -  Document the values limits and validity in the constructors of JPPFSchedule
Posted Dec 03, 2019 - updated Dec 03, 2019
action_vote_minus_faded.png
0
Votes
action_vote_plus_faded.png
Issue details
  • Type of issue
    Enhancement
  • Status
     
    New
  • Assigned to
    Not assigned to anyone
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
  • Posted by
     lolo4j
  • Owned by
    Not owned by anyone
  • Category
    Documentation
  • Resolution
    Not determined
  • Priority
    Normal
  • Targetted for
    icon_milestones.png JPPF 6.1.4
Issue description
The constructor JPPFSchedule(long millis) does not specify what happens when you specify 0 or less. This can lead to misinterpretation of the resulting behavior. For instance, the following code:
Task<?> task = ...;
task.setTimeoutSchedule(new JPPFSchedule(0));
means that the task will expire immediately, however a value of 0 or less for the timeout could also mean that it never expires. This needs to be clarified in the kavadoc of JPPFSchedule