Mailing-List: contact dev-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Ant Developers List" <dev@ant.apache.org>
Date: 1 Apr 2004 21:00:04 -0000
Message-ID: <20040401210004.27591.qmail@nagoya.betaversion.org>
From: bugzilla@apache.org
To: dev@ant.apache.org
Cc: 
Subject: DO NOT REPLY [Bug 23893]  -
    EXEC hangs until all processes launched from within .bat file finish.

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=23893>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=23893

EXEC hangs until all processes launched from within .bat file finish.


------- Additional Comments From ddevienne@lgc.com  2004-04-01 21:00 -------
OK, maybe I wasn't very explicit ;-)

The goal of spawn is to start and forget a process, that can (will) outlive the 
Java VM Ant is running inside of. If the started process is I/O intensive, it 
feels the system (native) buffers, and hangs when these buffers are full.

Your fix ensures that the out (err?) buffers are read from, thus providing room 
for the process to write some more output, and un-hang until the buffers are 
full again. But, who's going to read these buffers after Ant and its VM 
terminates? The spawned process goes on living, but if it ever fills the system 
buffers again, Ant is not there to pump the buffers anymore?

So is it in fact possible at all to spawn such a I/O intensive process at all???

Am I making more sense now? --DD

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org