On Mon, 11 Jul 2005, Leo Simons <[EMAIL PROTECTED]> wrote: > Stefan Bodewig wrote: >> On Mon, 11 Jul 2005, Leo Simons <[EMAIL PROTECTED]> wrote: >> >>>I suspect that using any JVM for which Ant's Execute takes a >>>different approach (ie not using Runtime.exec) makes the problem >>>"go away". >> >> Hmm, have you run your tests with the equivalent of <exec>'s >> vmlauncher="false"? I.e. force Execute to use the ShellLauncher >> even if it is on JDK > 1.2? > > I have now. It doesn't help. But it does give a new bit of info -- > the /bin/sh process created by the ShellLauncher stalls as well,
Likely some thread waiting for the process to read or the process waiting for Ant to write something. There have been some process deadlocks due to streams getting read too early or written too late. You are certainly using Ant's CVS HEAD, aren't you? > I've verified that the same problem occurs when running the xalan > build through gump on vmgump, so if you want to have a go at > figuring it out, that's all set to go :-) I'll try to free up some time, thanks. Stefan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
