On 2010-06-14, Stefan Bodewig wrote: > And then there is bug 46805 which claims that even useAvailable=true > doesn't fix a hanging process on Windows and suggests that we destroy > the process instance and not close the process' streams explicitly at > all. I have no test cases for this bug and can't reproduce it myself.
> process.destroy makes Ant lose output from the forked process, so it > doesn't seem a viable option. > Not closing the streams doesn't seem to do any harm on Windows but I > can't confirm that it helps in any way. I did see some issues on the > only Linux box I can reach right now, but that may be due to other > problems (other exec stuff fails there as well). Tested on a "real" machine now and not closing streams doesn't seem to cause any problems on Linux either. "doesn't seem" because there always is a possibility of a race-condition that I just haven't hit. Stefan --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
