Hi
Well fair enough, it is recognizable as the exit value will in that case be Integer.MAX_VALUE, so that should not be an issue. (So far for the non-hardcoded values)
Thanks, Martijn
Stefan Bodewig wrote:
On Wed, 17 Sep 2003, Martijn Kruithof <[EMAIL PROTECTED]> wrote:
regarding option 1 wouldn't this still need a patch to set killedProcess() to true
Hmm, only if it has been the watchdog that has killed the process IMHO. If the InterruptedException has been raised for any other reason, we shouldn't claim that a timeout has been hit. This is no strong opinion, though.
If it's been because of the watchdog, the current implementation should work fine.
Stefan
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
