JPPF Issue Tracker
star_faded.png
Please log in to bookmark issues
bug_report_small.png
CLOSED  Bug report JPPF-263  -  The cancel upon client disconnect attribute is not working
Posted May 12, 2014 - updated May 15, 2014
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
  • Estimated time
    Not estimated
  • Category
    Server
  • Resolution
    RESOLVED
  • Priority
    High
  • Reproducability
    Always
  • Severity
    Normal
  • Targetted for
    icon_milestones.png JPPF 4.1.1
Issue description
When a job has getSLA().setCancelUponClientDisconnect(false), the server cancels the job nonetheless when the client is terminated.
Steps to reproduce this issue
  • Configure a node and a driver with load balancing using "nodethreads" load balancing algorithm with multiplicator = 1
  • Submit a job with 100 tasks that wait each a couple of seconds, with a JobListener where the jobReturned() notification prints when the first batch of tasks has been executed
  • When the JobListener.jobReturned() prints its message, kill the client
==> the job terminates and isq removed from the server queue

#3
Comment posted by
 lolo4j
May 14, 00:31
Fixed in:
#5
Comment posted by
 lolo4j
May 15, 06:09
The fix is causing server-side job expiration to fail

The issue was updated with the following change(s):
  • The status has been updated, from Closed to New.
  • This issue has been reopened
  • The resolution has been updated, from RESOLVED to Not determined.
#6
Comment posted by
 lolo4j
May 15, 07:28
Fixed in: