Re: Detecting whether a job has been stopped by the user but JobExecutor hasn't terminated yet?

Thanks Jason, Carsten. The cancel path that I see exercised is as follows: client -> jobManager.stopJobById(jobId) JobManagerImpl.stopJobById(jobId): -> this.stopJobById(jobId, true) JobManagerImpl.stopJobById(jobId, forward): lookup job for jobId lookup

Re: Detecting whether a job has been stopped by the user but JobExecutor hasn't terminated yet?

I believe I understand what you are looking for. It's an event that you are look for that will indicate that the job has been requested to stop, but not necessarily stopped. I haven't looked at the code in question but a job should be persisting it's state in the JCR. Whenever a change to the

Detecting whether a job has been stopped by the user but JobExecutor hasn't terminated yet?

Hi, In essence I'm trying to detect the in-progress state of a job being stopped. I see in the sling-event implementation that calling jobHandler.stopJobById() eventually works its way down to calling jobHandler.stop(), setting a flag in the JobHandler. The JobExecutor is responsible for