ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 8510] - shutdown hook does not fire in forked java task under JDK1.4
Date Tue, 16 Jul 2002 15:49:36 GMT
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=8510>.
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=8510

shutdown hook does not fire in forked java task under JDK1.4





------- Additional Comments From Hal.Hildebrand@hellblazer.com  2002-07-16 15:49 -------
With regards to:

> Does anyone has the slighest idea of 
> what's going on here that avoid the 
> shutdown hook to be triggered ? I can't 
> find what could be the problem !

The problem is that when the InterruptedException is caught and ignored in the 
waitFor() method, the executing process is assumed to have completed and is 
removed from the shutdown hook.  This is not the case when the thread is 
interrupted.  The issue is that catching the InterruptedException, and 
silently ignoring it, is acting just like the process exited normally.  The 
execute() method has no way of knowing if the thread was interrupted - and 
therefore the process is still executing - of if the process exited.  So when 
the InterruptedException is thrown in the thread, and the waitFor() exits, it 
just removes the shutdown hook and assumes the process is done.  Therefore the 
process will just happily continue to execute and no one will ever kill it.

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


Mime
View raw message