commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Siegfried Goeschl (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (EXEC-44) ExecuteWatchdog should accept infinite timeouts (argument -1)
Date Mon, 31 May 2010 21:37:38 GMT

     [ https://issues.apache.org/jira/browse/EXEC-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Siegfried Goeschl resolved EXEC-44.
-----------------------------------

    Fix Version/s: 1.1
       Resolution: Fixed

'ExecuteWatchdog' has now an 'INFINITE_TIMEOUT' and an additional regression test 'DefaultExecutorTest#testExec44'

> ExecuteWatchdog should accept infinite timeouts (argument -1)
> -------------------------------------------------------------
>
>                 Key: EXEC-44
>                 URL: https://issues.apache.org/jira/browse/EXEC-44
>             Project: Commons Exec
>          Issue Type: Improvement
>    Affects Versions: 1.0.1
>            Reporter: Konrad Windszus
>            Assignee: Siegfried Goeschl
>             Fix For: 1.1
>
>
> Because the ExecuteWatchdog is the only way to destroy asynchronous processes, it should
be possible to set it to an infinite timeout, for processes which should not timeout, but
manually destroyed under some circumstances.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message