Skip to content

Bug 574883 - Job.getJobManager().join(family) doesn't wait for a re-scheduled job #148

@jukzi

Description

@jukzi

@iloveeclipse
the problem is that join() uses non-synchronized jobListeners :

JobManager.endJob(InternalJob, IStatus, boolean) notifies

  1. "done" and then
  2. "scheduled".

Between the two calls it looks to the listener like there is no more job scheduled.

A way to fix this might be to extend the "synchronized (lock)" block in endJob() around "done" and "schedule".
However somehow it sounds also dangerous/unwanted to synchronize around 3rd party calls.
JobManager.schedule() and JobManager.nextJob() also synchronize on lock so that those would wait till listeners returned.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions