JPPF Issue Tracker
Please log in to bookmark issues
CLOSED  Bug report JPPF-117  -  Task timeout is not working as expected
Posted Jan 21, 2013 - updated Dec 27, 2014
icon_info.png This issue has been closed with status "Closed" and resolution "RESOLVED".
Issue details
  • Type of issue
    Bug report
  • Status
  • Assigned to
  • Progress
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
  • Posted by
  • Owned by
    Not owned by anyone
  • Category
  • Resolution
  • Priority
  • Reproducability
  • Severity
  • Targetted for
    icon_milestones.png JPPF 3.3
Issue description
The timeout of tasks still uses the current time when a task bundle is started as start time. The impact is that some tasks may expire before they even started. This is not the behavior that can be understood in the related ddcoumentation.

We need to decide which behavior should be implemented and to clarify the documentation on this topic.
Steps to reproduce this issue
With a single node and a single processing thread in it (to ensure tasks are processed sequentially in the node), send a job with 2 tasks, where the first task is long-lasting and has no timeout set, and the second has a short timeout < the 1st task duration

Comment posted by
Jan 22, 07:56
Fixed. Changes 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.