Task #1957 (closed)
Opened 14 years ago
Closed 14 years ago
Correct Job.message and status usage
Reported by: | jamoore | Owned by: | jamoore |
---|---|---|---|
Priority: | n.a. | Milestone: | OMERO-Beta4.2 |
Component: | n.a. | Version: | n.a. |
Keywords: | n.a. | Cc: | |
Resources: | n.a. | Referenced By: | n.a. |
References: | n.a. | Remaining Time: | 0.0d |
Sprint: | 2010-03-05 (4) |
Description (last modified by jmoore)
Currently, the use of the "message" field and the closed status of jobs is somewhat lax. This causes issues trying to determine, for example, which scripts have properly been parsed (see #1321)
This could also be improved by adding a query method for open jobs to the processor API, and if no one is actively using it, then it must be closed. (This goes along with #2003 in that a job will then probably only be valid for a single invocation)
Change History (3)
comment:1 Changed 14 years ago by jmoore
- Status changed from new to assigned
comment:2 Changed 14 years ago by jmoore
- Description modified (diff)
comment:3 Changed 14 years ago by jmoore
- Remaining Time changed from 0.5 to 0
- Resolution set to fixed
- Status changed from assigned to closed
(In [6308]) fix #1957 - job handling is now cleaner (also see #1857)
Includes new ProcessorCallback method for requesting
the currently running jobs, as well as two new JobHandle methods.