Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Date: Thu, 3 Feb 2011 18:39:29 +0000 (UTC)
From: "Gary Gregory (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Message-ID: 
 <325519870.7956.1296758369328.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1564583291.7030.1296729149571.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] Commented: (EXEC-53) Allow control over asynchronous
 execution thread
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/EXEC-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990224#comment-12990224 ] 

Gary Gregory commented on EXEC-53:
----------------------------------

How about a unit test? :)

> Allow control over asynchronous execution thread
> ------------------------------------------------
>
>                 Key: EXEC-53
>                 URL: https://issues.apache.org/jira/browse/EXEC-53
>             Project: Commons Exec
>          Issue Type: Improvement
>    Affects Versions: 1.1
>            Reporter: Nickolay Martinov
>              Labels: patch
>         Attachments: commons-exec-daemon.patch
>
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> When process is started asynchronously using DefaultExecutor then thread is created that monitors process. This thread is user thread and blocks java program from exiting. There is no way to make this thread daemon. Allowing this to be a daemon thread one would be able to spawn process without &, monitor this process for some time to be sure that it is alive and then exit without calling System.exit() that isnt always possible/desirable.
> Also it would be nice to be able to create thread with specific priority or thread group or thread name or anything else.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira