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:10 ------- Use the attachement, Parallel.java, as the replacement for the standard Parallel task for Ant. Then do the following: <parallel> <sequential> <java fork="true" ... > #execute something like tomcat, #which will never exit, unless told to </sequential> <sequential> <waitfor maxwait="1" maxwaitunit="minute" checkevery="1" checkeveryunit="minute"> <isset property="short_regress_done" /> </waitfor> <fail unless="short_regress_done" message="Short_regress test timed out!" /> </sequential> </parallel> Note that it doesn't matter what's in the first sequential task, as long as it is a Java process (or any executable for that matter) which just goes away and never comes back - like Tomcat, or any application server. When the condition fails and the build exits, you'll see that the executable is still running. Clearly, the catching of the InterruptedException with no action whatsoever will cause the process to live forever, as the logic of the task shows that the Process is assumed to have been exited by returning from the waitFor() method. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
