[
https://issues.apache.org/jira/browse/EXEC-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17739875#comment-17739875
]
Nikolay Martynov commented on EXEC-53:
--------------------------------------
Yes, I think
[https://github.com/apache/commons-exec/blame/master/src/main/java/org/apache/commons/exec/DefaultExecutor.java#L257]
fixes the problem and the issue should be closed now.
> 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: Nikolay Martynov
> Assignee: Siegfried Goeschl
> Priority: Major
> Labels: patch
> Attachments: EXEC-53.unit-test.patch, 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 was sent by Atlassian Jira
(v8.20.10#820010)
