JPPF Issue Tracker
star_faded.png
Please log in to bookmark issues
enhancement_small.png
CLOSED  Enhancement JPPF-63  -  Add a separate job SLA for processing on the client side
Posted Sep 07, 2012 - updated Oct 12, 2012
action_vote_minus_faded.png
0
Votes
 action_vote_plus_faded.png
icon_info.png This issue has been closed with status "Closed" and resolution "RESOLVED".
Issue details
  • Type of issue
    Enhancement
  • 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
  • Targetted for
    icon_milestones.png JPPF 3.2
Issue description
As described in Bug report JPPF-61 - Job expiration causes wrong tasks to be returned for the next jobs, a timeout set on a job may cause it to expire in the client instead of in the server. To avoid this, and provide greater flexibility, we propose to have a separate job expiration schedule to be used on the client side.

#7
Comment posted by
lolo4j
Sep 09, 07:35
In fact I'm generalizing this enhancement to a full job SLA dedicated to the client-side processing.

Indeed it makes no sense to use the same execution policy, start time or expiration for the client and the server. Adding a separate client-side SLA will allow many more possibilities, while keeping the same semantics as for the server SLA.
#12
Comment posted by
lolo4j
Sep 23, 18:05
First implementation committed as trunk revision 2418.

Still to do:
#13
Comment posted by
lolo4j
Sep 29, 07:54
Performed a refactoring of the sla APIs, as client-side and server-side SLAs have a different (with a common part) semantic and need to be differentiated. Committed as trunk revision 2433
#14
Comment posted by
lolo4j
Oct 12, 07:05
This is a reminder to also add the client SLA for the configuration of JPPF jobs submitted via the JPPFExecutorService
#15
Comment posted by
lolo4j
Oct 12, 15:06
This enhancement is now implemented. JUnit tests added. Documentation updated.

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