DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10345>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10345 Execute task, when interrupted, does not kill processes ------- Additional Comments From [EMAIL PROTECTED] 2002-07-16 15:18 ------- This is the way I run this all the time. We have replaced the Parallel task with the supplied attachement, and we run with variations of this pattern - i.e. several parallel threads, any one of which may have an error or timeout (if a condition) and then we wish the whole Parallel task to end - not just hang waiting for a thread which will never end. Our short regression -which is where we're using this - is run all the time by numerous developers. Without this patch to Execute, the processes hang around forever. With it, they die a normal death when the Parallel task exits. If you like, I'll include a complete, tested little build file with a Java program which just spins forever. But you'll still need the modified Parallel task to get the InterruptedException to be thrown during the waitFor(). -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
