JPPF Issue Tracker
Please log in to bookmark issues
CLOSED  Bug report JPPF-150  -  Cancelling job from client API results in missing jobEnded() event
Posted May 30, 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
    Not assigned to anyone
  • 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.x
Issue description
When cancelling a job using JPPFClient.cancelJob(String), the jobEnded() event for any registered JobListener is not sent. This does not happen if I use JMXDriverConnectionWrapper.cancelJob(String) instead.

A workaround is to use:
AbstractJPPFClientConnection c = (AbstractJPPFClientConnection) jppfClient.getClientConnection();
Additionally, I noticed that JPPFClient.cancelJob(String) always returns true, which caused by the code in SubmissionManagerClient.cancelJob(String).
Steps to reproduce this issue
  • create a job that lasts sufficiently long (so as to have time to cancel it before it ends)
  • register a JobListener on this job, which prints out each event it receives
  • call JPPFClient.cancelJob(job.getUuid())
  • ==> the job will be cancelled and all events, except jobEnded() will be printed. jobEnded() is never called.

Comment posted by
Jun 02, 09:11
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 New to Closed.
  • This issue's progression has been updated to 100 percent completed.
  • The resolution has been updated, from Not determined to RESOLVED.