On 26-11-10 15:21, Patricia Shanahan wrote:
What worries me a little is the state the operating system keeps on
terminated processes. We know of the SO_REUSEADDR issue, but you seem
to experience the non-release of resources on process termination.
formally a OS bug, but if so is something we need to workaround. How
definate are you on your reports where you have problems rerunning a
test caused by the OS not releasing resources on VM exit?
I see two issues here:
1. Terminating every VM.
A working termination is a firm requirement before bypassing orderly
teardown can be attempted.
2. Deleting any temporary files.
Empirically, a Ctrl-C termination often leaves the system in a state in
which subsequent tests fail.
Any idea which VM receives this Ctrl-C? The ant VM, the harness master,
or any random process? There is no such concept as process group leader
under windows is there?
Gr.Sim
--
QCG, Software voor het MKB, 071-5890970, http://www.qcg.nl
Quality Consultancy Group b.v., Leiderdorp, Kvk Den Haag: 28088397
