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, before ever
firing up a new java process. I.e. we never get beyond
return Runtime.getRuntime().exec(cmd, env);
on line 736 of Execute.java.
>>My hunch is that we'd have to implement a work around in Ant...
>
> I can probably get away with yet another magic property if I know
> how to cure the problem ;-)
It'd be nice to know :-)
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 :-)
cheers,
Leo
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
