Bug #1522 (closed)
Opened 15 years ago
Closed 15 years ago
Processes are being cleaned up too quickly
Reported by: | jamoore | Owned by: | jamoore |
---|---|---|---|
Priority: | critical | Cc: | dzmacdonald |
Sprint: | n.a. | ||
Total Remaining Time: | n.a. |
Description
With the latest changes to get processor.py working on Windows, something like:
process = sr.acquireProcessor(job, 10) process.wait()
can throw an Ice.ObjectNotExistException since by the time the wait has reached the remote python process, the subprocess is already complete, and everything cleaned up.
Change History (3)
comment:1 Changed 15 years ago by jmoore
comment:2 Changed 15 years ago by jmoore
comment:3 Changed 15 years ago by jmoore
- Resolution set to fixed
- Status changed from new to closed
Along with #1524 this seem to be fine. The glacier issues were certainly a much larger issue.
It's not quite clear what the best method here is:
The last point is quite tricky. The process could be kept alive forever since it's not bound to a session. However, obtaining the results for the process require that the session is alive, and therefore that might be a good time to pull the plug.
In the case of InteractiveProcessors, assuming a user doesn't call setDetach(true), then the death of the calling session will also close the subprocess session.
Note: importer is using setDetach(true)