JPPF Issue Tracker
star_faded.png
Please log in to bookmark issues
bug_report_small.png
CLOSED  Bug report JPPF-126  -  Job cancelled from the admin console may get stuck in the server queue
Posted Feb 12, 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
     
    		 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
    Server
  • Resolution
    RESOLVED
  • Priority
    High
  • Reproducability
    Rarely
  • Severity
    Critical
  • Targetted for
    icon_milestones.png JPPF 3.3
Issue description
I have noticed that sometimes, when a job is cancelled from the admin GUI, it is not properly cancelled and remains stuck in the server's queue, with a number of remaining tasks = 0.

This may be related to the "cancel-requeue" feature and needs to be investigated properly.
Steps to reproduce this issue
not sure yet what actions lead to the problem

#3
Comment posted by
lolo4j
Feb 12, 09:29
I can now systematically reproduce with the following code: 
@Test(timeout=10000L)
public void testResumeAndCancelSuspendedJob() throws Exception
{
  int nbTasks = 2;
  DriverJobManagementMBean proxy = BaseSetup.getJobManagementProxy(client);
  assertNotNull(proxy);
  JPPFJob job = BaseTestHelper.createJob(getCurrentMethodName(), false, false, nbTasks, LifeCycleTask.class, 5000L);
  job.getSLA().setSuspended(true);
  client.submit(job);
  Thread.sleep(2000L);
  proxy.resumeJob(job.getUuid());
  Thread.sleep(500L);
  proxy.cancelJob(job.getUuid());
  JPPFResultCollector collector = (JPPFResultCollector) job.getResultListener();
  List<JPPFTask> results = collector.waitForResults();
  assertEquals(results.size(), nbTasks);
  Thread.sleep(1000L);
  String[] ids = proxy.getAllJobIds();
  assertNotNull(ids);
  assertEquals("the driver's job queue should be empty", 0, ids.length);
}
#4
Comment posted by
lolo4j
Feb 13, 03:03
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.